I run Ubuntu Mate 22.04 and I have a USB mass storage device (aka USB-Stick) that is formatted with btrfs. I know it's partition UUID and label and I want it specifically to be mounted with specific mount options. In particular I want to enable file system compression every time I plug it into my computer without having to unmount it and then manually remount it with the terminal.

When I plug it in, I would usually have to do

sudo umount /dev/sdb/
sudo mkdir /media/username/label
sudo mount -t btrfs -o rw,ssd,nosuid,nodev,noatime,space_cache=v2,subvolid=5,subvol=/,uhelper=udisks2,compress=zstd:15,discard=async /dev/disk/by-uuid/<uuid> /media/username/label
sudo chown username:usergroup /media/username/label

which I would like to automate somehow.

How do I do that?

Edit

I tried adding this line to my /etc/fstab as suggested in the comments.

UUID=<uuid> /mnt/<label> btrfs rw,ssd,nosuid,nodev,noatime,space_cache=v2,subvolid=5,subvol=/,uhelper=udisks2,compress=zstd:15,discard=async,nofail        0       2

However this causes the device to not auto-mount anymore when I plug it in. When I mount it, I have to be root. Then it doesn't show up in the devices anymore in my file manager (caja). It also is not user writable by default.

I would like the same behavior as plugging it in normally, just with the options

• ssd, because the device in question is somewhat special and announces itself as rotational when it is not),
• compress=zstd:15, because the device is very slow anyway and also somewhat small and
• noatime to preserve the flash drive's lifespan

I want it to mount automatically with those settings, but also is user writable and show up in the file manager.

I have installed a debian based distribution on my drive. When I installed it, the / mountpoint was btrfs on a logical partition (/dev/sda7) with a mount point for /boot/efi on a fat32 logical partition (/dev/sda6).

I since wanted to use the savedefault feature of grub, which doesn't work on btrfs. So I booted up a live image with gparted and shrunk /boot/efi (/dev/sda6) added an ext4 partition /dev/sda8.

After that I adjusted /etc/fstab to use the new mount point and then followed the steps to repair grub.

1. mount the root file system mkdir /tmp/rootfs && mount /dev/sda7 /tmp/rootfs
2. mount the boot drive on the mounted file system mount /dev/sda8 /tmp/rootfs/@/boot
3. mount the efi partition mount /dev/sda6 /tmp/rootfs/@/boot/efi
4. mount sys mount --bind /sys /tmp/rootfs/@/sys
5. mount dev mount --bind /dev /tmp/rootfs/@/dev
6. mount proc mount --bind /proc /tmp/rootfs/@/proc
7. for good measure mount home mount --bind /tmp/rootfs/@home /tmp/rootfs/@/home
8. chroot into the rootfs chroot /tmp/rootfs
9. repair grub, apparently

To repair grub I used this command:

grub-install /dev/sda

And it says it's successful. However when I then try to boot the system I get this error:

GRUB loading...
Welcome to GRUB!

error: file `/@/boot/grub/i386-pc/normal.mod´ not found.
grub rescue>

Of course it can't find it there because it's not in /@/boot/ anymore. I think this is an error with the stage 1 bootloader in the MBR. How do I fix that? I use an msdos partition table.

I have also managed to boot the system from grub loaded from a USB drive with this command

set root=(hd1,msdos8)
linux /vmlinuz root=LABEL=LinuxRoot rootflags=subvol=@ quiet splash rw
initrd /initrd
boot

I have tried to reinstall grub from there as well, with no success. I have also tried this command, which also didn't work (says successful, but same error appears on reboot).

grub-install --bootloader-id=grub --target=x86_64-efi --efi-directory=/boot/efi --no-nvram /dev/sda

I am running Ubuntu Mate 20.04 and I am trying to set up my audio devices on my laptop. I learned about module-echo-cancel and am now using it.

I have added the following to the pulse audio configuration near the end:

.ifexists module-echo-cancel.so
# https://wiki.archlinux.org/title/PulseAudio#Microphone_echo/noise_cancellation
load-module module-echo-cancel use_master_format=1 use_volume_sharing=1 aec_method=webrtc aec_args="analog_gain_control=0 digital_gain_control=1 experimental_agc=0 noise_suppression=1 voice_detection=1 extended_filter=1" source_name=echoCancel_source sink_name=echoCancel_sink
set-default-source echoCancel_source
set-default-sink echoCancel_sink
.endif

I have since noticed that I can not set the port for this source in the GUI as I can with the default source. I have 2 sources. "Built-in Audio Analog Stereo" and Monitor of Built-in Audio Analog Stereo when I don't have the module loaded.

Without module-echo-cancel, when I plug in my headset into the mixed input and output 3.5mm jack, the audio sink connector switches from Internal to Headset. This is most likely because the module module-switch-on-port-available is loaded. However when I plug the same headset into the 3.5mm jack the audio source does not automatically switch over. How can I achieve that?

With the echo cancel module it takes the selected audio port and applies it's filter to that. However I have to do 4 clicks to change it. First switching back to the unfiltered input, then switching the port and then switching back to the filtered input. Whenever I unplug my headset it switches back to the internal microphone, which has a very poor quality.

How can I switch automatically to the new source port? How can I make echo cancel automatically use the new source port if that is a different thing?

I have read through the pulseaudio documentation on freedesktop and the arch wiki, but I have found nothing that would help me. I thought module-switch-on-port-available would do it, but it was already loaded. It switches only the output ports automatically, not the input.

Pulse detects the headset microphone as it populates the drop down list in the gui, but it does not switch automatically.

I am running ubuntu 20.04 LTS (kernel 5.4.0-81-generic) from PXE and I wish to add a local cache. Because I don't want to have a partition on all my devices for caching, I wish to use a ramdisk for that purpose.

I have managed to enable the fsc option during boot with the help of this answer.

However when I run the cachefilesd service, it failes with -95: Operation not supported. This is probably because tmpfs doesn't support user_xattr, which is required.

I have read here that you can compile/patch the kernel to enable user_xattr, though this is a security risk. Besides being a maintenance nightmare, I do not wish to go that far and fiddle around with automating that with every kernel update.

I have read here (german) and this and it's response.

It indicates that you can make a tmpfs, then make a loopback device, format that to ext4 and then run your fs-cache on there.

However, since I'm using PXE and the NFS mount point is /, how do I do that during boot, preferably before cachedfilesd.service is started?

My bootloader (vesamenu.c32)

# [...]
label                   ubuntunfs
        menu label      ^Ubuntu NFS
        text help
Run ubuntu from Network File System.
        endtext
        kernel          ubuntu/boot/vmlinuz
        initrd          ubuntu/boot/initrd.img
        append          root=/dev/nfs nfsroot=192.168.1.5:/srv/tftp/ubuntu,rw,fsc,relatime ip=dhcp rw
# [...]

My fstab

/proc    /proc    proc    defaults   0 0
/sys     /sys     sysfs   defaults   0 0
/dev/nfs /        nfs     defaults,relatime,fsc   1 1

# ramdisk for fs-cache for nfs
tmpfs    /media/ramdisk    tmpfs    defaults,size=5%      0       0

none            /tmp            tmpfs   defaults        0       0
none            /var/run        tmpfs   defaults        0       0
none            /var/lock       tmpfs   defaults        0       0
none            /var/tmp        tmpfs   defaults        0       0

my /etc/cachefilesd.conf

dir /media/ramdisk
tag mycache
brun 90%
bcull 70%
bstop 30%
frun 90%
fcull 70%
fstop 30%

culltable 14

I have the following file

Hello
World
my
name
is
FalcoGer

And I wish to concatenate the strings of each line.

I wrote the following script to do just that.

#! /usr/bin/bash
myFile=/home/FalcoGer/testfile.txt

result=""
cat $myFile | while read line
do
  result+="$line "
done

echo Result: $result

However I only get Result: with an empty string. When I print it from within the loop it seems to work just fine. What's wrong with this script and how do I fix it?

I want to run a game server on my raspberry pi 4 (4GB) using steamcmd. I have already set up a chroot and box86 to run a teamspeak 3 server.

I am following these instructions and I am stuck on step 8, that is running steamcmd.sh.

I have altered the file to run box86, however whenever I run the shell script, it seems to update itself before executing, reverting my edits.

#!/usr/bin/env bash

STEAMROOT="$(cd "${0%/*}" && echo $PWD)"
STEAMCMD=`basename "$0" .sh`

UNAME=`uname`
if [ "$UNAME" == "Linux" ]; then
  STEAMEXE="${STEAMROOT}/linux32/${STEAMCMD}"
  PLATFORM="linux32"
  export LD_LIBRARY_PATH="$STEAMROOT/$PLATFORM:$LD_LIBRARY_PATH"
else # if [ "$UNAME" == "Darwin" ]; then
  STEAMEXE="${STEAMROOT}/${STEAMCMD}"
  if [ ! -x ${STEAMEXE} ]; then
    STEAMEXE="${STEAMROOT}/Steam.AppBundle/Steam/Contents/MacOS/${STEAMCMD}"
  fi
  export DYLD_LIBRARY_PATH="$STEAMROOT:$DYLD_LIBRARY_PATH"
  export DYLD_FRAMEWORK_PATH="$STEAMROOT:$DYLD_FRAMEWORK_PATH"
fi

ulimit -n 2048

MAGIC_RESTART_EXITCODE=42

if [ "$DEBUGGER" == "gdb" ] || [ "$DEBUGGER" == "cgdb" ]; then
  ARGSFILE=$(mktemp $USER.steam.gdb.XXXX)

  # Set the LD_PRELOAD varname in the debugger, and unset the global version.
  if [ "$LD_PRELOAD" ]; then
    echo set env LD_PRELOAD=$LD_PRELOAD >> "$ARGSFILE"
    echo show env LD_PRELOAD >> "$ARGSFILE"
    unset LD_PRELOAD
  fi

  $DEBUGGER -x "$ARGSFILE" --args /usr/local/bin/box86 "$STEAMEXE" "$@"
  rm "$ARGSFILE"
else
  $DEBUGGER /usr/local/bin/box86 "$STEAMEXE" "$@"
fi

STATUS=$?

if [ $STATUS -eq $MAGIC_RESTART_EXITCODE ]; then
    exec "$0" "$@"
fi
exit $STATUS

When I run this modified file I get this:

Box86 with Dynarec v0.2.1 7c0b11e built on May  6 2021 17:03:01
WARNING: setlocale('en_US.UTF-8') failed, using locale: 'C'. International characters may not work.
Redirecting stderr to '/root/Steam/logs/stderr.txt'
Looks like steam didn't shutdown cleanly, scheduling immediate update check
[  0%] Checking for available updates...
[----] Verifying installation...
[  0%] Downloading update...
[  0%] Checking for available updates...
[----] Download complete.
[----] Extracting package...
[----] Extracting package...
[----] Extracting package...
[----] Extracting package...
[----] Installing update...
[----] Installing update...
[----] Installing update...
[----] Installing update...
[----] Installing update...
[----] Installing update...
[----] Installing update...
[----] Installing update...
[----] Cleaning up...
[----] Update complete, launching Steamcmd...
/opt/steamcmd/steamcmd.sh: line 37: /opt/steamcmd/linux32/steamcmd: cannot execute binary file: Exec format error

If I use a different file name, such as steamcmd_custom.sh I get this:

Box86 with Dynarec v0.2.1 7c0b11e built on May  6 2021 17:03:01
Error: file is not found (check BOX86_PATH)
./steamcmd_custom.sh: line 38: 71730 Segmentation fault      (core dumped) $DEBUGGER /usr/local/bin/box86 "$STEAMEXE" "$@"

And running

box86 steamcmd

from /opt/steamcmd/linux32 yields me

Box86 with Dynarec v0.2.1 7c0b11e built on May  6 2021 17:03:01
WARNING: setlocale('en_US.UTF-8') failed, using locale: 'C'. International characters may not work.
Redirecting stderr to '/root/Steam/logs/stderr.txt'
[  0%] Checking for available updates...
[----] Verifying installation...
[----] !!! Fatal Error: Failed to load steamconsole.so

I have set up my raspberry pi running ubuntu 20.04 server so it can run teamspeak with box86.

To do that I set up a chroot in ls /srv/chroot/focal-armhf/ with debootstrap. In that directory I compiled box86. I then downloaded and installed ts3server for x86 on linux. I have set up a custom config for schroot.

/etc/schroot/chroot.d/focal-armhf.conf:

[focal-armhf]
description=Ubuntu focal armhf chroot
type=directory
directory=/srv/chroot/focal-armhf
profile=ts3server
personality=linux
# preserve-environment=true
root-users=ubuntu
users=ubuntu

When I run the following commands in bash on the host, everything works fine.

# beginn session, name it ts3server
sudo /usr/bin/schroot -n ts3server -b -c chroot:focal-armhf

# run start script. it's the same as the default start script, however I added /usr/local/bin/box86 in front of the starting of the actual server binary.
sudo /usr/bin/schroot --run-session --chroot ts3server -d /opt/ts3server/teamspeak3-server_linux_x86/ './ts3custom.sh' start

# at this point the server is running and i can connect to it.
# ...

# when I want to shut down:
# stopping server
/usr/bin/schroot --run-session --chroot ts3server -d /opt/ts3server/teamspeak3-server_linux_x86/ './ts3custom.sh' stop

# ending schroot session
/usr/bin/schroot -e --chroot ts3server

I wanted to do this automatically with systemd now. So I created this unit configuration

[Unit]
Description=Teamspeak3 Server in chroot
After=network.target
After=syslog.target

[Service]
ExecStartPre=/usr/bin/schroot -n ts3server -b -c chroot:focal-armhf
ExecStart=/usr/bin/schroot --run-session --chroot ts3server -d /opt/ts3server/teamspeak3-server_linux_x86/ './ts3custom.sh' start
ExecStop=/usr/bin/schroot --run-session --chroot ts3server -d /opt/ts3server/teamspeak3-server_linux_x86/ './ts3custom.sh' stop
ExecStopPost=/usr/bin/schroot -e --chroot ts3server
Restart=no
Type=simple

[Install]
WantedBy=multi-user.target

When I run it however it shuts down immediately after. The teamspeak server log runs is

2021-05-06 17:58:49.429511|INFO    |ServerLibPriv |   |TeamSpeak 3 Server 3.13.3 (2020-12-16 14:17:05)
2021-05-06 17:58:49.456286|INFO    |ServerLibPriv |   |SystemInformation: Linux 5.4.0-1034-raspi #37-Ubuntu SMP PREEMPT Mon Apr 12 23:14:49 UTC 2021 i686 Binary: 32bit
2021-05-06 17:58:49.456975|WARNING |ServerLibPriv |   |The system locale is set to "C" this can cause unexpected behavior. We advice you to repair your locale!
2021-05-06 17:58:49.508403|INFO    |DatabaseQuery |   |dbPlugin name:    SQLite3 plugin, Version 3, (c)TeamSpeak Systems GmbH
2021-05-06 17:58:49.509804|INFO    |DatabaseQuery |   |dbPlugin version: 3.11.1
2021-05-06 17:58:49.553828|INFO    |DatabaseQuery |   |checking database integrity (may take a while)

If I set restart always, it will keep generating that same log over and over again.
It seems like the server is started, then forks to the background, then ExecStop is called by systemd.

I have tried setting Type=forking and Type=exec and Type=simple, all with the same results.

Basically everything works fine, until I try to use systemd to manage it all.

How can I make it work?

In particular I want:

• Automatically start it with the system
• Manage it with service ts3server start|stop|restart

For completeness sake my custom script to manage teamspeak server:

#!/bin/sh
# Copyright (c) 2019 TeamSpeak Systems GmbH
# All rights reserved

BINARYNAME="./ts3server"
COMMANDLINE_PARAMETERS="" #add any command line parameters you want to pass here
PID_FILE=ts3server.pid

do_start() {
        if [ -e $PID_FILE ]; then
                PID=$(cat "$PID_FILE")
                if (ps -p "$PID" >/dev/null 2>&1); then
                        echo "The server is already running, try restart or stop"
                        return 1
                else
                        echo "$PID_FILE found, but no server running. Possibly your previously started server crashed"
                        echo "Please view the logfile for details."
                        rm $PID_FILE
                fi
        fi
       if [ $(id -u) -eq 0 ]; then
               echo "WARNING ! For security reasons we advise: DO NOT RUN THE SERVER AS ROOT"
               c=1
               while [ "$c" -le 10 ]; do
                       echo -n "!"
                       sleep 1
                       c=$(($c + 1))
               done
               echo "!"
       fi
        echo "Starting the TeamSpeak 3 server"
        if [ ! -e "$BINARYNAME" ]; then
                echo "Could not find binary, aborting"
                return 5
        fi
        if [ ! -x "$BINARYNAME" ]; then
                echo "${BINARYNAME} is not executable, trying to set it"
                chmod u+x "${BINARYNAME}"
        fi
        if [ ! -x "$BINARYNAME" ]; then
                echo "${BINARNAME} is not exectuable, cannot start TeamSpeak 3 server"
                return 3
        fi
        /usr/local/bin/box86 "./${BINARYNAME}" "${@}" "daemon=1" "pid_file=$PID_FILE"
        if [ $? -eq 0 ]; then
                echo "TeamSpeak 3 server started, for details please view the log file"
        else
                echo "TeamSpeak 3 server could not start"
                return 4
        fi
}

do_stop() {
        if [ ! -e $PID_FILE ]; then
                echo "No server running ($PID_FILE is missing)"
                return 0
        fi
        PID=$(cat "$PID_FILE")
        if (! ps -p "$PID" >/dev/null 2>&1); then
                echo "No server running"
                return 0
        fi

        echo -n "Stopping the TeamSpeak 3 server "
        kill -TERM "$PID" || exit $?
        rm -f $PID_FILE
        c=300
        while [ "$c" -gt 0 ]; do
                if (kill -0 "$PID" 2>/dev/null); then
                        echo -n "."
                        sleep 1
                else
                        break
                fi
                c=$(($c - 1))
        done
        echo
        if [ $c -eq 0 ]; then
                echo "Server is not shutting down cleanly - killing"
                kill -KILL "$PID"
                return $?
        else
                echo "done"
        fi
        return 0
}

do_status() {
        if [ ! -e $PID_FILE ]; then
                echo "No server running ($PID_FILE is missing)"
                return 1
        fi
        PID=$(cat "$PID_FILE")
        if (! ps -p "$PID" >/dev/null 2>&1); then
                echo "Server seems to have died"
                return 1
        fi
        echo "Server is running"
        return 0
}

# change directory to the scripts location
cd $(dirname $([ -x "$(command -v realpath)" ] && realpath "$0" || readlink -f "$0"))

case "$1" in
start)
        shift
        do_start "$@" "$COMMANDLINE_PARAMETERS"
        exit $?
        ;;
stop)
        do_stop
        exit $?
        ;;
restart)
        shift
        do_stop && (do_start "$@" "$COMMANDLINE_PARAMETERS")
        exit $?
        ;;
status)
        do_status
        exit $?
        ;;
*)
        echo "Usage: ${0} {start|stop|restart|status}"
        exit 2
        ;;
esac

I am trying to set up a chroot and I ran

sudo qemu-debootstrap --arch=amd64 stretch /srv/chroot/focal-amd64

during the second stage i realized that I wanted focal, not stretch. Copy & paste error.
So I hit ctrl + c and wanted to try again.

sudo rm -rf /srv/chroot/focal-amd64/*

however i get spammed with

rm: cannot remove '/srv/chroot/focal-amd64/proc/[...]': Operation not permitted

I tried setting write permissions to directories with

find -type d | xargs chmod +rwx

with the same errors. No matter what I try to do it seems like I can't delete the folder anymore to try again.

Before, when I let the chroot creation finish, I was able to delete the directory without any problems afterwards, it's only after I interrupted this one that this happens.

I have read that ubuntu mate has support for wayland for some time now and wanted to give it a try, because supposedly it's all around better for security and performance and a lot cleaner code.

uname -a gives me: Linux <hostname> 5.4.0-62-generic #70-Ubuntu SMP Tue Jan 12 12:45:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux and I'm running on a Toshiba R702Q Vivobook.

I have searched for instructions on how to install wayland on ubuntu mate and came up short. I have found a snap package "MATE-on-wayland", but I don't really like snap. I tried it anyway and I get a selection on the login screen. When I pick the wayland option the display flickers briefly before staying blank (with the backlights on). The websites talking about this snap package seem very computer generated and give no more info other than "use sudo snap install blah to install the package" and the package description.

I have had a look at my installed packages and plenty of libwayland- packages are installed by default (as dependencies of some dependency of ubuntu-mate-desktop or something).

$ apt list --installed | grep --ignore-case wayland

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

kwayland-data/focal,focal,now 4:5.68.0-0ubuntu1 all [installed,automatic]
kwayland-integration/focal,now 4:5.18.4.1-0ubuntu1 amd64 [installed,automatic]
libkf5waylandclient5/focal,now 4:5.68.0-0ubuntu1 amd64 [installed,automatic]
libqt5waylandclient5-dev/focal,now 5.12.8-0ubuntu1 amd64 [installed]
libqt5waylandclient5/focal,now 5.12.8-0ubuntu1 amd64 [installed,automatic]
libqt5waylandcompositor5-dev/focal,now 5.12.8-0ubuntu1 amd64 [installed]
libqt5waylandcompositor5/focal,now 5.12.8-0ubuntu1 amd64 [installed,automatic]
libva-wayland2/focal,now 2.7.0-2 amd64 [installed,automatic]
libwayland-bin/focal,now 1.18.0-1 amd64 [installed,automatic]
libwayland-client0/focal,now 1.18.0-1 amd64 [installed,automatic]
libwayland-client0/focal,now 1.18.0-1 i386 [installed,automatic]
libwayland-cursor0/focal,now 1.18.0-1 amd64 [installed,automatic]
libwayland-cursor0/focal,now 1.18.0-1 i386 [installed,automatic]
libwayland-dev/focal,now 1.18.0-1 amd64 [installed,automatic]
libwayland-egl1/focal,now 1.18.0-1 amd64 [installed,automatic]
libwayland-egl1/focal,now 1.18.0-1 i386 [installed,automatic]
libwayland-server0/focal,now 1.18.0-1 amd64 [installed,automatic]
qtwayland5-dev-tools/focal,now 5.12.8-0ubuntu1 amd64 [installed,automatic]
qtwayland5-doc/focal,focal,now 5.12.8-0ubuntu1 all [installed,automatic]
qtwayland5/focal,now 5.12.8-0ubuntu1 amd64 [installed]
wayland-protocols/focal,focal,now 1.20-1 all [installed,automatic]             

Yet I can not pick it during login. I have seen a similar question that was resolved (in the comments) by reinstalling the libwayland-* packages. I did so with

sudo apt install --reinstall libwayland-bin libwayland-client0 libwayland-cursor0 libwayland-dev libwayland-egl1 libwayland-server0

which gave me no appreciable effect, even after a reboot.

My current display manager is lightdm. Because of that I looked up how to enable wayland with lightdm and came up with this set of instructions.

1. Verify that you have a Gnome session in /usr/share/wayland-sessions.
2. Using root privilege open a text editor of your preference and edit the /etc/lightdm/lightdm.conf file and uncomment the following line: sessions-directory=/usr/share/lightdm/sessions:/usr/share/xsessions:/usr/share/wayland-sessions

I do not have any files or directories in /usr/share/wayland-sessions, though the folder exists.
Furthermore I do not have a file /etc/lightdm/lightdm.conf, though 2 other .conf files exist (one to turn on numlock and another to forbid certain users (nologin, nobody, etc) and shells /bin/false, /bin/nologin, etc) and an empty directory for config files.

So I'm at a loss. Supposedly ubuntu mate ships and supports wayland, yet I can not use it. And I can't find any resource on how to make it work.

I also would like to run some wayland compositor natively, not on top of x. What's the point in adding more overhead when I want to save power :P

PS: I'm aware that wayland is not a software, but rather a protocol. But I don't know what compositor mate is supposed to ship with, because apparently every major distribution is making their own one, or so I've read.
Also I don't really know what all the terms mean. window manager, display manager, compositor or what is client to which server (and how to connect a client to a remote server for that matter).
So when I search compositor or wayland with apt search I get to see stuff like mutter, weston and xweston. And when I apt info mutter I get

Example window manager using GNOME's window manager library Mutter is a Wayland display server and X11 window manager and compositor library. It contains functionality related to, among other things, window management, window compositing, focus tracking, workspace management, keybindings and monitor configuration.

Which might as well be chineese.

Edit:

I tried to install the weston package, which gave me the option to select it from the login screen. However launching it from terminal (weston), virtual terminal (TTY1) weston-launch or the login screen (via dropdown select) gives me a very, very barebones and unusable gray "desktop" kind of area with nothing but a button to launch a terminal and a clock, which is nothing like the mate desktop.

Edit2:

Trying to run mate-wayland from terminal (instead of from the login screen) after installing the snap package gave me an error about xwayland not being installed. After installing it it kinda worked. But the pannels threw me a lot of errors about missing references and a lot of things didn't show up on them (including the menu). Running firefox (from a quick link that survived the messed up panels) gave me a window that'd flash at a high update rate (> 10/s) with text and images shifting all over with every update until a page was done loading. Interestingly enough that firefox didn't remember my cookies (I wasn't logged into stackexchange for example) or the session, though it popped up with some old version of my opened tab list.

So I want to use Anjuta and add a Theme. I use the GtkSourceView plugin as my editor. For some reason it doesn't allow me to define colors like with any any other editor but instead requires me to use a gtk theme.

I use Ubuntu Mate 20.04. I'm not sure why but gtksourceview-3.0 and gtksourceview-4 are both installed on my system.

To add a theme I tried a few things. I read someplace that you can make themes with a project called "oomox". I tried that, but it created a massive array of files and directories that didn't seem at all like what GtkSourceView uses, which is a single file. So I scrapped that.

I coped obsidian.xml (the closest to what I want my thing to look like) from /usr/share/gtksourceview-4/styles and edited it. I placed my new file into ~/.themes. That didn't work (it doesn't show up in the list when selecting a theme for Anjuta). I tried ~/.local/share/gtksourceview-4/styles and ~/.local/share/gtksourceview-3.0/styles and also ~/.local/share/gedit and ~/.local/share/gedit/styles (gedit is not installed though).

I am confused how I can add a simple style to this editor and why there isn't any information on that topic. I can imagine people wanting to customize their IDE all the time. Maybe I'm missing something obvious? I searched "adding theme to gtksourceview" and "adding theme to Anjuta". And all I found was how to add a theme to gedit (hence my attempts above) and how to switch the default themes.

Also I don't want to add my theme to the system install directory (/usr or /etc). Surely there is a way to add it for users (/home/<user>) only.

It would be really nice if there were some program I could use to edit my style and give me a preview of some code. (Like most other IDEs). If there is no such thing, then I'd be really nice to at least have a list of all the valid tags.

Edit: Just to test it, I put the new file in with the rest of them in /usr/share/gtksourceview-4/styles/ and 3.0 and 2. Neither soft links nor the file itself seemed to have an effect. I'm very confused. I doublechecked the file itself. All I did was add/delete some color tags and change colors about.

For clarity's sake here is the file.

custom.xml

<?xml version="1.0" encoding="UTF-8"?>

<style-scheme id="custom" _name="custom" version="1.0">

  <author>MyName</author>
  <_description>Dark color scheme.</_description>

  <color name="green"                       value="#00FF00"/>
  <color name="darkgreen"                   value="#008000"/>
  <color name="red"                         value="#FF0000"/>
  <color name="orange"                      value="#FF8000"/>
  <color name="yellow"                      value="#FF0000"/>
  <color name="blue"                        value="#0000FF"/>
  <color name="lightblue"                   value="#00FFFF"/>
  <color name="purple"                      value="#8080FF"/>
  <color name="gray"                        value="#808080"/>
  <color name="darkgray"                    value="#404040"/>
  <color name="bggray"                      value="#202020"/>
  <color name="purple"                      value="#8080FF"/>
  <color name="white"                       value="#ffffff"/>

  <!-- Global Settings -->
  <style name="text"                        foreground="green"          background="bggray"/>
  <style name="selection"                   foreground="green"          background="gray"/>
  <style name="cursor"                      foreground="white"           background="bggray"/>
  <style name="secondary-cursor"            foreground="darkgray"       background="bggray"/>
  <style name="current-line"                background="gray"/>
  <style name="line-numbers"                foreground="yellow" background="#black"/>
  <style name="draw-spaces"                 foreground="gray"/>
  <style name="background-pattern"          background="bggray"/>

  <!-- Bracket Matching -->
  <style name="bracket-match"               foreground="yellow"/>
  <style name="bracket-mismatch"            foreground="yellow" background="red"/>

  <!-- Right Margin -->
  <style name="right-margin"                foreground="gray" background="bggray"/>

  <!-- Search Matching -->
  <style name="search-match"                background="orange"/>

  <!-- Comments -->
  <style name="def:comment"                 foreground="darkgreen"/>
  <style name="def:shebang"                 foreground="darkgreen" bold="true"/>
  <style name="def:doc-comment-element"     italic="true"/>

  <!-- Constants -->
  <style name="def:constant"                foreground="yellow"/>
  <style name="def:string"                  foreground="yellow"/>
  <style name="def:special-char"            foreground="orange"/>
  <style name="def:special-constant"        foreground="orange"/>
  <style name="def:floating-point"          foreground="purple"/>

  <!-- Identifiers -->
  <style name="def:identifier"              foreground="lightblue"/>

  <!-- Statements -->
  <style name="def:statement"               foreground="green" bold="true"/>

  <!-- Types -->
  <style name="def:type"                    foreground="blue" bold="true"/>

  <!-- Others -->
  <style name="def:preprocessor"            foreground="red"/>
  <style name="def:error"                   foreground="red" background="orange" bold="true"/>
  <style name="def:warning"                 foreground="yellow" background="orange" bold="true"/>
  <style name="def:note"                    foreground="lightblue" background="bggray" bold="true"/>
  <style name="def:underlined"              italic="true" underline="single"/>

  <!-- Heading styles, uncomment to enable -->
  <!--
  <style name="def:heading0"                scale="5.0"/>
  <style name="def:heading1"                scale="2.5"/>
  <style name="def:heading2"                scale="2.0"/>
  <style name="def:heading3"                scale="1.7"/>
  <style name="def:heading4"                scale="1.5"/>
  <style name="def:heading5"                scale="1.3"/>
  <style name="def:heading6"                scale="1.2"/>
  -->

  <!-- Language specific -->
  <style name="diff:added-line"             foreground="darkgreen"/>
  <style name="diff:removed-line"           foreground="red"/>
  <style name="diff:changed-line"           foreground="yellow"/>
  <style name="diff:diff-file"              foreground="green" bold="true"/>
  <style name="diff:location"               foreground="green"/>
  <style name="diff:special-case"           foreground="white" bold="true"/>

  <style name="latex:command"               foreground="green" bold="true"/>
  <style name="latex:include"               use-style="def:preprocessor"/>

</style-scheme>

Edit 2: I found these resources: https://developer.gnome.org/gtksourceview/stable/style-reference.html
But they don't detail which style names are valid. Or where to put the style file.

So I set up a virtual machine with Ubuntu Mate 20.04 and because I wanted to try it out, I set it up to use ZFS. I use a disk size of 10GB and the installer decided to set up my bpool to have a capacity of 480M. However df -h shows

bpool/BOOT/ubuntu_cub7km                          118M   92M   26M  78% /boot

I have 0 experience with ZFS and don't know what this is all about. I didn't even get one kernel update in without an error that initramfs couldn't write to the disk.

Setting up initramfs-tools (0.136ubuntu6.2) ...
update-initramfs: deferring update (trigger activated)
Setting up linux-firmware (1.187.1) ...
update-initramfs: Generating /boot/initrd.img-5.4.0-40-generic
I: The initramfs will attempt to resume from /dev/sda5
I: (UUID=ff3fca52-c9f0-4369-9aaf-598aa999db8b)
I: Set the RESUME variable to override this.
Error 24 : Write error : cannot write compressed block 
E: mkinitramfs failure cpio 141 lz4 -9 -l 24
update-initramfs: failed for /boot/initrd.img-5.4.0-40-generic with 1.
dpkg: error processing package linux-firmware (--configure):
 installed linux-firmware package post-installation script subprocess returned error exit status 1

How can I expand that partition? Normally I'd just run gparted and move the sizes about a little, but zfs is supposed to be all advanced and stuff. I tried enabling autoexpand for bpool, but the issue persisted. I don't know where the remaining ~400MB space for that pool went either.

As a workaround I moved the initfs image file to my home directory and ran apt upgrade again, which did generate the new initramfs file without issue. But that seems dangerous and unnecessary.

Edit

I have reinstalled the virtual machine to use a traditional ext4 file system. Thus I can not try out any answers.

I have upgrade to ubuntu mate 20.04 yesterday and now my typing acts as though I have the compose key permanently pressed. If I want to type, say a back quote (`) or this acute (^) I must press the key twice, which is quite annoying.
I don't need those characters to type stuff like é, but rather scripts, regex, markdown or vim and the like use them. So I often need to type those characters but really rarely do I need to type accented letters.

Before I was able to just press the key and it would pop up straight away. How do I get that functionality back?

I have tried enabling the compose key (in the hopes that it will disable that annoying system), but it didn't help. I have also tried to switch from 105 key generic (intl.) to 104 key generic (not international), but that didn't help either.
I really don't even know how to word this for searching.

My keyboard layout is set to "german", I set my compose key to capslock and it does seem to do stuff. Like compose + c + c = č
But what I want doesn't work with or without the compose key set. Also what is that "3rd Level" stuff?

I tried to update my graphics drivers from AMD for my laptop. I am running ubuntu mate (Linux <hostname> 4.15.0-96-generic #97-Ubuntu SMP Wed Apr 1 03:25:46 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux) It runs on an amd apu with radeon r7 graphics. Afterwards redshift, a program to change the color temperature of the display during night hours, stopped working correctly. I have uninstalled the drivers and reinstalled the repository ones.

The problem is: seemingly all pure white surfaces don't get the color corrections applied, while all others do. Some weird scrolling behavior in the web browser can also be seen. I confirmed this with a color picker. Most annoyingly window shadows do get this applied and when they move over a white area, it becomes orange in a thick outline. Unfortunately I can't make a screenshot of the phenomenon as the redshift happens afterwards.

I think the issue is not with redshift but rather with the driver acting up. I have no idea where to start. I already reinstalled mesa drivers and redshift from repositories.

Here's my apt log.

# Installing driver prerequisites (as per instructions for amd drivers)

Start-Date: 2020-04-10  21:09:28
Commandline: apt install vulkan-sdk
Requested-By: paul (1000)
Install: lunarg-vulkan-layers:amd64 (1.2.135.0~rc2-1ubuntu18.04.1.1, automatic), spirv-headers:amd64 (1.5.1+37-1ubuntu18.04.1.1, automatic), shaderc:amd64 (2019.1+28-1ubuntu18.04.1.1, automatic), spirv-cross-dev:amd64 (2020.02.26+22-1ubuntu18.04.1.1, automatic), libvulkan-dev:amd64 (1.2.135.0~rc2-1ubuntu18.04.1.1, automatic), lunarg-vktrace:amd64 (1.2.135.0~rc2-1ubuntu18.04.1.1, automatic), vulkan-headers:amd64 (1.2.135.0~rc2-1ubuntu18.04.1.1, automatic), libminizip1:amd64 (1.1-8build1, automatic), libqt5webenginewidgets5:amd64 (5.9.5+dfsg-0ubuntu2, automatic), glslang-dev:amd64 (8.13.3559+168-1ubuntu18.04.1.1, automatic), libre2-4:amd64 (20180201+dfsg-2, automatic), libqt5webengine-data:amd64 (5.9.5+dfsg-0ubuntu2, automatic), spirv-cross:amd64 (2020.02.26+22-1ubuntu18.04.1.1, automatic), vulkan-tools:amd64 (1.2.135.0~rc2-1ubuntu18.04.1.1, automatic), spirv-tools:amd64 (2020.2-1ubuntu18.04.1.1, automatic), lunarg-vkconfig:amd64 (1.2.135.0~rc2-1ubuntu18.04.1.1, automatic), lunarg-via:amd64 (1.2.135.0~rc2-1ubuntu18.04.1.1, automatic), libqt5webenginecore5:amd64 (5.9.5+dfsg-0ubuntu2, automatic), vulkan-sdk:amd64 (1.2.135.0~rc1-1lunarg18.04.1.1), vulkan-validationlayers:amd64 (1.2.135.0~rc2-1ubuntu18.04.1.1, automatic), glslang-tools:amd64 (8.13.3559+168-1ubuntu18.04.1.1, automatic), vulkan-validationlayers-dev:amd64 (1.2.135.0~rc2-1ubuntu18.04.1.1, automatic)
Upgrade: libvulkan1:amd64 (1.1.70+dfsg1-1ubuntu0.18.04.1, 1.2.135.0~rc2-1ubuntu18.04.1.1), libvulkan1:i386 (1.1.70+dfsg1-1ubuntu0.18.04.1, 1.2.135.0~rc2-1ubuntu18.04.1.1)
End-Date: 2020-04-10  21:09:43

# install amd drivers via install script

Start-Date: 2020-04-10  21:10:56
Commandline: apt install amdgpu amdgpu-lib32
Requested-By: paul (1000)
Install: libgbm1-amdgpu:amd64 (1:18.0.0-673703, automatic), libgbm1-amdgpu:i386 (1:18.0.0-673703, automatic), libglapi-amdgpu-mesa:amd64 (1:18.0.0-673703, automatic), libglapi-amdgpu-mesa:i386 (1:18.0.0-673703, automatic), amdgpu-core:amd64 (18.20-673703, automatic), amdgpu-lib32:amd64 (18.20-673703), libllvm6.0-amdgpu:amd64 (1:6.0-673703, automatic), libllvm6.0-amdgpu:i386 (1:6.0-673703, automatic), libdrm-amdgpu-amdgpu1:amd64 (1:2.4.91-673703, automatic), libdrm-amdgpu-amdgpu1:i386 (1:2.4.91-673703, automatic), amdgpu:amd64 (18.20-673703), libgles1-amdgpu-mesa:amd64 (1:18.0.0-673703, automatic), libgles1-amdgpu-mesa:i386 (1:18.0.0-673703, automatic), mesa-amdgpu-omx-drivers:amd64 (1:18.0.0-673703, automatic), libwayland-amdgpu-client0:amd64 (1.14.0-673703, automatic), libwayland-amdgpu-client0:i386 (1.14.0-673703, automatic), gst-omx-amdgpu:amd64 (1.0.0.1-673703, automatic), libwayland-amdgpu-egl1-mesa:amd64 (1:18.0.0-673703, automatic), libwayland-amdgpu-egl1-mesa:i386 (1:18.0.0-673703, automatic), glamor-amdgpu:amd64 (1.19.0-673703, automatic), libomxil-bellagio0:amd64 (0.9.3-4, automatic), libwayland-amdgpu-server0:amd64 (1.14.0-673703, automatic), libwayland-amdgpu-server0:i386 (1.14.0-673703, automatic), libgles2-amdgpu-mesa:amd64 (1:18.0.0-673703, automatic), libgles2-amdgpu-mesa:i386 (1:18.0.0-673703, automatic), libosmesa6-amdgpu:amd64 (1:18.0.0-673703, automatic), libosmesa6-amdgpu:i386 (1:18.0.0-673703, automatic), libegl1-amdgpu-mesa-drivers:amd64 (1:18.0.0-673703, automatic), libegl1-amdgpu-mesa-drivers:i386 (1:18.0.0-673703, automatic), mesa-amdgpu-vdpau-drivers:amd64 (1:18.0.0-673703, automatic), mesa-amdgpu-vdpau-drivers:i386 (1:18.0.0-673703, automatic), libegl1-amdgpu-mesa:amd64 (1:18.0.0-673703, automatic), libegl1-amdgpu-mesa:i386 (1:18.0.0-673703, automatic), amdgpu-dkms:amd64 (18.20-673703, automatic), mesa-amdgpu-va-drivers:amd64 (1:18.0.0-673703, automatic), mesa-amdgpu-va-drivers:i386 (1:18.0.0-673703, automatic), xserver-xorg-amdgpu-video-amdgpu:amd64 (1:1.4.0-673703, automatic), libomxil-bellagio-bin:amd64 (0.9.3-4, automatic), libxatracker2-amdgpu:amd64 (1:18.0.0-673703, automatic), libxatracker2-amdgpu:i386 (1:18.0.0-673703, automatic), libgl1-amdgpu-mesa-dri:amd64 (1:18.0.0-673703, automatic), libgl1-amdgpu-mesa-dri:i386 (1:18.0.0-673703, automatic), ids-amdgpu:amd64 (1.0.0-673703, automatic), libdrm2-amdgpu:amd64 (1:2.4.91-673703, automatic), libdrm2-amdgpu:i386 (1:2.4.91-673703, automatic), libgl1-amdgpu-mesa-glx:amd64 (1:18.0.0-673703, automatic), libgl1-amdgpu-mesa-glx:i386 (1:18.0.0-673703, automatic)
End-Date: 2020-04-10  21:13:29

# rerun install script with opencl option

Start-Date: 2020-04-10  21:13:59
Commandline: apt install amdgpu amdgpu-lib32 clinfo-amdgpu-pro opencl-orca-amdgpu-pro-icd clinfo-amdgpu-pro opencl-amdgpu-pro-icd
Requested-By: paul (1000)
Install: amdgpu-pro-core:amd64 (18.20-673703, automatic), opencl-amdgpu-pro-icd:amd64 (18.20-673703), opencl-orca-amdgpu-pro-icd:amd64 (18.20-673703), libopencl1-amdgpu-pro:amd64 (18.20-673703, automatic), clinfo-amdgpu-pro:amd64 (18.20-673703)
End-Date: 2020-04-10  21:14:07

# rerun install script with vulkan and opencl support

Start-Date: 2020-04-10  21:15:07
Commandline: apt install amdgpu amdgpu-lib32 amdgpu-pro vulkan-amdgpu-pro amdgpu-pro-lib32 vulkan-amdgpu-pro:i386 clinfo-amdgpu-pro opencl-orca-amdgpu-pro-icd clinfo-amdgpu-pro opencl-amdgpu-pro-icd
Requested-By: paul (1000)
Install: libgbm1-amdgpu-pro:i386 (18.20-673703, automatic), libgbm1-amdgpu-pro:amd64 (18.20-673703, automatic), vulkan-amdgpu-pro:i386 (18.20-673703), vulkan-amdgpu-pro:amd64 (18.20-673703), libgles2-amdgpu-pro:i386 (18.20-673703, automatic), libgles2-amdgpu-pro:amd64 (18.20-673703, automatic), libgl1-amdgpu-pro-dri:i386 (18.20-673703, automatic), libgl1-amdgpu-pro-dri:amd64 (18.20-673703, automatic), libgl1-amdgpu-pro-ext:amd64 (18.20-673703, automatic), wsa-amdgpu:i386 (18.20-673703, automatic), wsa-amdgpu:amd64 (18.20-673703, automatic), libgl1-amdgpu-pro-glx:i386 (18.20-673703, automatic), libgl1-amdgpu-pro-glx:amd64 (18.20-673703, automatic), libegl1-amdgpu-pro:i386 (18.20-673703, automatic), libegl1-amdgpu-pro:amd64 (18.20-673703, automatic), amdgpu-pro-lib32:amd64 (18.20-673703), amdgpu-pro:amd64 (18.20-673703), libgl1-amdgpu-pro-appprofiles:amd64 (18.20-673703, automatic), libgbm1-amdgpu-pro-base:amd64 (18.20-673703, automatic)
End-Date: 2020-04-10  21:15:16

rebooted here, problems appeared

# run uninstall script

Start-Date: 2020-04-10  21:21:58
Commandline: apt purge amdgpu-core
Requested-By: paul (1000)
Purge: amdgpu-pro-core:amd64 (18.20-673703), libgbm1-amdgpu-pro:i386 (18.20-673703), libgbm1-amdgpu-pro:amd64 (18.20-673703), libgbm1-amdgpu:amd64 (1:18.0.0-673703), libgbm1-amdgpu:i386 (1:18.0.0-673703), libglapi-amdgpu-mesa:amd64 (1:18.0.0-673703), libglapi-amdgpu-mesa:i386 (1:18.0.0-673703), amdgpu-core:amd64 (18.20-673703), vulkan-amdgpu-pro:i386 (18.20-673703), vulkan-amdgpu-pro:amd64 (18.20-673703), amdgpu-lib32:amd64 (18.20-673703), libllvm6.0-amdgpu:amd64 (1:6.0-673703), libllvm6.0-amdgpu:i386 (1:6.0-673703), libdrm-amdgpu-amdgpu1:amd64 (1:2.4.91-673703), libdrm-amdgpu-amdgpu1:i386 (1:2.4.91-673703), amdgpu:amd64 (18.20-673703), libgles1-amdgpu-mesa:amd64 (1:18.0.0-673703), libgles1-amdgpu-mesa:i386 (1:18.0.0-673703), mesa-amdgpu-omx-drivers:amd64 (1:18.0.0-673703), libwayland-amdgpu-client0:amd64 (1.14.0-673703), libwayland-amdgpu-client0:i386 (1.14.0-673703), gst-omx-amdgpu:amd64 (1.0.0.1-673703), libgles2-amdgpu-pro:i386 (18.20-673703), libgles2-amdgpu-pro:amd64 (18.20-673703), libgl1-amdgpu-pro-dri:i386 (18.20-673703), libgl1-amdgpu-pro-dri:amd64 (18.20-673703), libgl1-amdgpu-pro-ext:amd64 (18.20-673703), wsa-amdgpu:i386 (18.20-673703), wsa-amdgpu:amd64 (18.20-673703), libgl1-amdgpu-pro-glx:i386 (18.20-673703), libgl1-amdgpu-pro-glx:amd64 (18.20-673703), libwayland-amdgpu-egl1-mesa:amd64 (1:18.0.0-673703), libwayland-amdgpu-egl1-mesa:i386 (1:18.0.0-673703), libegl1-amdgpu-pro:i386 (18.20-673703), libegl1-amdgpu-pro:amd64 (18.20-673703), amdgpu-pro-lib32:amd64 (18.20-673703), glamor-amdgpu:amd64 (1.19.0-673703), opencl-amdgpu-pro-icd:amd64 (18.20-673703), libwayland-amdgpu-server0:amd64 (1.14.0-673703), libwayland-amdgpu-server0:i386 (1.14.0-673703), opencl-orca-amdgpu-pro-icd:amd64 (18.20-673703), libgles2-amdgpu-mesa:amd64 (1:18.0.0-673703), libgles2-amdgpu-mesa:i386 (1:18.0.0-673703), libosmesa6-amdgpu:amd64 (1:18.0.0-673703), libosmesa6-amdgpu:i386 (1:18.0.0-673703), libopencl1-amdgpu-pro:amd64 (18.20-673703), libegl1-amdgpu-mesa-drivers:amd64 (1:18.0.0-673703), libegl1-amdgpu-mesa-drivers:i386 (1:18.0.0-673703), mesa-amdgpu-vdpau-drivers:amd64 (1:18.0.0-673703), mesa-amdgpu-vdpau-drivers:i386 (1:18.0.0-673703), libegl1-amdgpu-mesa:amd64 (1:18.0.0-673703), libegl1-amdgpu-mesa:i386 (1:18.0.0-673703), amdgpu-dkms:amd64 (18.20-673703), mesa-amdgpu-va-drivers:amd64 (1:18.0.0-673703), mesa-amdgpu-va-drivers:i386 (1:18.0.0-673703), amdgpu-pro:amd64 (18.20-673703), xserver-xorg-amdgpu-video-amdgpu:amd64 (1:1.4.0-673703), libgl1-amdgpu-pro-appprofiles:amd64 (18.20-673703), libgbm1-amdgpu-pro-base:amd64 (18.20-673703), libxatracker2-amdgpu:amd64 (1:18.0.0-673703), libxatracker2-amdgpu:i386 (1:18.0.0-673703), libgl1-amdgpu-mesa-dri:amd64 (1:18.0.0-673703), libgl1-amdgpu-mesa-dri:i386 (1:18.0.0-673703), ids-amdgpu:amd64 (1.0.0-673703), libdrm2-amdgpu:amd64 (1:2.4.91-673703), libdrm2-amdgpu:i386 (1:2.4.91-673703), clinfo-amdgpu-pro:amd64 (18.20-673703), libgl1-amdgpu-mesa-glx:amd64 (1:18.0.0-673703), libgl1-amdgpu-mesa-glx:i386 (1:18.0.0-673703)
End-Date: 2020-04-10  21:22:24

Start-Date: 2020-04-10  21:28:25
Commandline: apt autoremove
Requested-By: paul (1000)
Remove: libomxil-bellagio0:amd64 (0.9.3-4), libomxil-bellagio-bin:amd64 (0.9.3-4)
End-Date: 2020-04-10  21:28:28

Steam started acting up, saying opengl not supported by display or something, started installing opengl

Start-Date: 2020-04-10  21:28:57
Commandline: apt install freeglut3-dev
Requested-By: paul (1000)
Install: freeglut3:amd64 (2.8.1-3, automatic), freeglut3-dev:amd64 (2.8.1-3)
End-Date: 2020-04-10  21:28:58

Start-Date: 2020-04-10  21:29:39
Commandline: apt install binutils-gold g++ mesa-common-dev build-essential libglew1.5-dev libglm-dev
Requested-By: paul (1000)
Install: libglew-dev:amd64 (2.0.0-5), libglm-dev:amd64 (0.9.9~a2-2)
End-Date: 2020-04-10  21:29:41

Start-Date: 2020-04-10  21:30:05
Commandline: apt install --reinstall mesa-utils
Requested-By: paul (1000)
Reinstall: mesa-utils:amd64 (8.4.0-1)
End-Date: 2020-04-10  21:30:07

Start-Date: 2020-04-10  21:37:05
Commandline: apt remove vulkan-sdk
Requested-By: paul (1000)
Remove: vulkan-sdk:amd64 (1.2.135.0~rc1-1lunarg18.04.1.1)
End-Date: 2020-04-10  21:37:07

Start-Date: 2020-04-10  21:37:21
Commandline: apt autoremove
Requested-By: paul (1000)
Remove: lunarg-vulkan-layers:amd64 (1.2.135.0~rc2-1ubuntu18.04.1.1), spirv-headers:amd64 (1.5.1+37-1ubuntu18.04.1.1), shaderc:amd64 (2019.1+28-1ubuntu18.04.1.1), spirv-cross-dev:amd64 (2020.02.26+22-1ubuntu18.04.1.1), libvulkan-dev:amd64 (1.2.135.0~rc2-1ubuntu18.04.1.1), lunarg-vktrace:amd64 (1.2.135.0~rc2-1ubuntu18.04.1.1), vulkan-headers:amd64 (1.2.135.0~rc2-1ubuntu18.04.1.1), libminizip1:amd64 (1.1-8build1), libqt5webenginewidgets5:amd64 (5.9.5+dfsg-0ubuntu2), glslang-dev:amd64 (8.13.3559+168-1ubuntu18.04.1.1), libre2-4:amd64 (20180201+dfsg-2), libqt5webengine-data:amd64 (5.9.5+dfsg-0ubuntu2), spirv-cross:amd64 (2020.02.26+22-1ubuntu18.04.1.1), vulkan-tools:amd64 (1.2.135.0~rc2-1ubuntu18.04.1.1), spirv-tools:amd64 (2020.2-1ubuntu18.04.1.1), lunarg-vkconfig:amd64 (1.2.135.0~rc2-1ubuntu18.04.1.1), lunarg-via:amd64 (1.2.135.0~rc2-1ubuntu18.04.1.1), libqt5webenginecore5:amd64 (5.9.5+dfsg-0ubuntu2), vulkan-validationlayers:amd64 (1.2.135.0~rc2-1ubuntu18.04.1.1), glslang-tools:amd64 (8.13.3559+168-1ubuntu18.04.1.1), vulkan-validationlayers-dev:amd64 (1.2.135.0~rc2-1ubuntu18.04.1.1)
End-Date: 2020-04-10  21:37:24

Start-Date: 2020-04-10  21:38:29
Commandline: apt install --reinstall mesa-utils
Requested-By: paul (1000)
Reinstall: mesa-utils:amd64 (8.4.0-1)
End-Date: 2020-04-10  21:38:31

Start-Date: 2020-04-10  21:55:48
Commandline: apt install --reinstall libgl1-mesa-dri
Reinstall: libgl1-mesa-dri:amd64 (19.2.8-0ubuntu0~18.04.3), libgl1-mesa-dri:i386 (19.2.8-0ubuntu0~18.04.3)
End-Date: 2020-04-10  21:55:51

Start-Date: 2020-04-10  22:17:33
Commandline: apt remove mesa-vulkan-drivers
Remove: mesa-vulkan-drivers:amd64 (19.3.3~kisak2~b)
End-Date: 2020-04-10  22:17:33

Start-Date: 2020-04-10  22:17:56
Commandline: apt install mesa-vulkan-drivers
Install: mesa-vulkan-drivers:amd64 (19.2.8-0ubuntu0~18.04.3)
Remove: mesa-vulkan-drivers:i386 (19.3.3~kisak2~b)
End-Date: 2020-04-10  22:17:57

Start-Date: 2020-04-10  22:18:57
Commandline: apt remove libxatracker2
Remove: libxatracker2:amd64 (19.3.3~kisak2~b), xserver-xorg-video-vmware:amd64 (1:13.2.1-1build1), xserver-xorg-video-all:amd64 (1:7.7+19ubuntu7.1)
End-Date: 2020-04-10  22:18:58

Start-Date: 2020-04-10  22:19:09
Commandline: apt autoremove
Remove: libvulkan1:i386 (1.2.135.0~rc2-1ubuntu18.04.1.1), libxcb-randr0:i386 (1.13-2~ubuntu18.04)
End-Date: 2020-04-10  22:19:10

Start-Date: 2020-04-10  22:19:37
Commandline: apt install xserver-xorg-video-all
Install: libxatracker2:amd64 (19.2.8-0ubuntu0~18.04.3, automatic), xserver-xorg-video-vmware:amd64 (1:13.2.1-1build1, automatic), xserver-xorg-video-all:amd64 (1:7.7+19ubuntu7.1)
End-Date: 2020-04-10  22:19:38

At this point local packages were installed and I couldn't get apt to install the repository versions. So I ran

dpkg -r --force-depends libdrm-common libegl-mesa0 libegl1-mesa libgbm1 libgl1-mesa-glx libglapi-mesa libglx-mesa0 libllvm9 libvulkan1 libwayland-egl1-mesa
apt --fix-broken install

Start-Date: 2020-04-10  22:34:00
Commandline: apt --fix-broken install
Install: libvulkan1:amd64 (1.1.70+dfsg1-1ubuntu0.18.04.1, automatic), libllvm9:amd64 (1:9-2~ubuntu18.04.2, automatic), libllvm9:i386 (1:9-2~ubuntu18.04.2, automatic), libegl-mesa0:amd64 (19.2.8-0ubuntu0~18.04.3, automatic), libglapi-mesa:amd64 (19.2.8-0ubuntu0~18.04.3, automatic), libglapi-mesa:i386 (19.2.8-0ubuntu0~18.04.3, automatic), libgbm1:amd64 (19.2.8-0ubuntu0~18.04.3, automatic), libgl1-mesa-glx:amd64 (19.2.8-0ubuntu0~18.04.3, automatic), libgl1-mesa-glx:i386 (19.2.8-0ubuntu0~18.04.3, automatic), libglx-mesa0:amd64 (19.2.8-0ubuntu0~18.04.3, automatic), libglx-mesa0:i386 (19.2.8-0ubuntu0~18.04.3, automatic), libdrm-common:amd64 (2.4.99-1ubuntu1~18.04.2, automatic)
End-Date: 2020-04-10  22:34:07

Start-Date: 2020-04-10  22:35:35
Commandline: apt install libegl1-mesa
Install: libegl1-mesa:amd64 (19.2.8-0ubuntu0~18.04.3)
End-Date: 2020-04-10  22:35:36

Start-Date: 2020-04-10  22:38:32
Commandline: apt install --reinstall libdrm-amdgpu1
Reinstall: libdrm-amdgpu1:amd64 (2.4.99-1ubuntu1~18.04.2), libdrm-amdgpu1:i386 (2.4.99-1ubuntu1~18.04.2)
End-Date: 2020-04-10  22:38:33

Update

Seemingly went away on it's own. Please close.

The problem

My Custom DNS-Server is randomly not queried anymore.

The Setup

I am using Ubuntu 18.04 and I have my own DNS server in my network. I set up my dhcp server to set up that DNS server for the network. Before I had set up my DNS server explicitly, but now I am visiting two wifi access points and the second one doesn't have that DNS server.
Now I have deleted the nameservers section from my netplan yaml file, because I can't seem to set it on a per AP basis.
After a reconnect everything works fine for a while, but then suddenly the DNS server doesn't answer anymore for anything in my lan, but public stuff like google works fine.
When I reconnect then, it works again for a while, and then seemingly randomly stops.

Running dig with the dns server explicitly works fine. I am confused, dig says the response comes from the systemd-resolved resolver on 127.0.0.53. However the output of systemd-resolved --status reports the correct dns server settings for my interface.

Global
          DNSSEC NTA: 10.in-addr.arpa
                      16.172.in-addr.arpa
                      168.192.in-addr.arpa
                      17.172.in-addr.arpa
                      18.172.in-addr.arpa
                      19.172.in-addr.arpa
                      20.172.in-addr.arpa
                      21.172.in-addr.arpa
                      22.172.in-addr.arpa
                      23.172.in-addr.arpa
                      24.172.in-addr.arpa
                      25.172.in-addr.arpa
                      26.172.in-addr.arpa
                      27.172.in-addr.arpa
                      28.172.in-addr.arpa
                      29.172.in-addr.arpa
                      30.172.in-addr.arpa
                      31.172.in-addr.arpa
                      corp
                      d.f.ip6.arpa
                      home
                      internal
                      intranet
                      lan
                      local
                      private
                      test

Link 4 (tun0)
<OpenVPN not in use>

Link 3 (wlp1s0)
      Current Scopes: DNS
       LLMNR setting: yes
MulticastDNS setting: no
      DNSSEC setting: no
    DNSSEC supported: no
         DNS Servers: 192.168.1.5
                      <ipv6>
          DNS Domain: ~.
                      lan

Link 2 (enp2s0)
<not in use>

Setting the DNS IP for the interface in netplan via

nameservers:
  addressess: [my.local.dns.server]
  search: [lan]

works fine, but again I can't do that anymore because i visit multiple access points and a configuration per access point seems impossible at the moment.
Setting the DNS server in network manager on it's own connection works fine, also.

I find this rather frustrating and want to know what DNS server I am using and why my own one isn't used anymore at random, and also why it comes back at random. I disabled DHCP on my fritzbox, it acts as a DNS server, but shouldn't be used (my own dns server uses it after 1.1.1.1 and 8.8.8.8).

My configuration:

/etc/resolv.conf:

# [comment block about this being systemd-dnsresolv stub]
nameserver 127.0.0.53
options edns0
search lan

/etc/nsswitch.conf

passwd:         compat systemd
group:          compat systemd
shadow:         compat
gshadow:        files

hosts:          files mdns4_minimal [NOTFOUND=return] dns myhostname
networks:       files

protocols:      db files
services:       db files
ethers:         db files
rpc:            db files

netgroup:       nis

/etc/hosts

127.0.0.1 localhost
127.0.1.1 <myhostname>.lan <myhostname>

::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

Edit

I had a look with wireshark when I ran dig. DNS queries were sent out to an ipv6 address, not my local dns server. The IPv6 Address was that of my router. Why is that?

Edit2

My current netplan config:

network:
  version: 2
  renderer: NetworkManager
  ethernets:
    enp2s0:
      dhcp4: yes
      dhcp6: yes
  wifis:
    wlp1s0:
      dhcp4: yes
      dhcp6: yes
      dhcp-identifier: mac
      access-points:
        "SSID1":
          password: ****
        "SSID2":
          password: ****

I have successfully installed Ubuntu 18.04 onto an SD card. I did this by creating an msdos partition table (pi doesn't support guid), then putting U-Boot onto the SD Card on partition 1 (fat32, pi doesn't support anything else). Then I pasted the pi-bootloader onto partition 1 /. And then I copied the files from the net installer (mini-iso) onto that partition as well. The whole process is laid out here.

Everything works perfectly well from the SD Card. UBoot starts, then it loads the grub2 that came with the net installer mini iso. that in turn i have changed the config so it loads the linux kernel from partition 3 (p2 is swap, in my case).

So I pulled an image of that, put it on an usb drive (usb to m2 sata adapter), which should just behave like any other flash drive. So, I turn it on. U boot starts, I don't see anything different from normal. Then it loads grub. But instead of displaying a nice menu with the option to boot ubuntu or install it (because the net installer stuff is still on there), it dumps me straight into the grub console.

typing ls I get (memdisk), and nothing else. It doesn't seem to find the usb drive it actually loaded from itself. on that memdisk is a single file at (memdisk)/boot/grub/grub.cfg, but I have no way of knowing what's actually in there. Edit: (memdisk) is there on the sd card also, same content, it just lists the partitions on the sd card also, while it does not on the flash drive.

There are no grub modules, no nothing. I think it ever so briefly flashes an error at me, but then the grub console opens and I have no time to read those messages.

I'm at a loss as to what to do. Perhaps if I made my own grub image with usb modules like it is described here (using grub-mkimage to create a grub image with modules in the memdisk)? Although I have no idea which modules I need, or if that's even the right approach.

Any help would be greatly appreciated.

Edit: I have found this:

Basically you need grub modules (which I don't have) for grub to recognize the usb drive.

the short answer is:

insmod usbms insmod ehci insmod uhci insmod ohci

Only one of the *hci line is needed (usually ehci), but older machines may need either uhci or ohci Inserting all 3 works fine.

Those lines should be added to either grub.cfg or custom.cfg (I recommend the latter) in the /boot/grub/ folder on the non-USB drive.

I got my modules from here, however usbms is not among them and neither is [e,u,o]hci. I have found this about writing grub modules, but it confuses me. And I can't find the source code. Using something odd like the armhf 64bit processor doesn't make things easy to find compatible software.

Edit2: I have downloaded the grub source code from http://git.savannah.gnu.org/git/grub.git/ and compiled it on my raspberry pi. However the usbms.c and ehci.c source code files are there, it did not compile them into grub modules.

I have found this information on how to build grub modules here but it just doesn't work for me. I tried changing Makefile.core.am and removed the if statement around usbms.module, then running autogen and configure. No dice. I tried manually building in grub-core with make usbms.module, but it says gcc: fatal error: no input files.

I don't need grub. I just want to boot my Ubuntu arm64. If I can somehow skip from u boot directly to there it's fine.

My current ideas:

• Compile usbms.mod, ehci.mod, uhci.mod and ohci.mod, make a new grub image with those modules linked in, and it should just work with the current grub config.
• Make a new grub image with the modules, the config and the linux kernel and initramfs built in as a memdisk. boot the kernel from there with the command line indicating that the rootfs is on partition 3
• Somehow tell uboot to boot my linux kernel from partition3 with the command line that partition 3 is root.
• use the black magic boot loader that comes with the raspberry pi firmware thing. I have not the slightest idea how that stuff works, but if someone can make it boot my ubuntu x64 then I'd be all too happy to ignore the fact that I don't know how it works.

I have no idea how to do any of them.

I'm using a Raspberry Pi 3 with Ubuntu 18.04. At my company we have a DNS server and a couple of domains with ".local". I know technically this isn't correct and it should be ".lan" instead, because .local is reserved for multicast dns. But that's the way it is and it can't easily be changed. So on my windows machine I can ping and browse to those domain names without trouble. On my Ubuntu however I can not.

I can not use IPs because some domains are on the same machine and the IIS webserver sorts things out what goes where.

I have searched and it comes up quite often:

• https://smallbusiness.chron.com/resolving-local-ubuntu-38861.html
• Why do none of my local servers resolve?
• ubuntu server not resolving LAN hostnames

However changing /etc/nsswitch.conf doesn't do the trick for me. I tried

• hosts: files mdns4_minimal [NOTFOUND=return] dns myhostname # default
• hosts: files dns
• hosts: files mdns4_minimal [NOTFOUND=continue] dns myhostname
• hosts: files mdns4 [NOTFOUND=return] dns myhostname
• hosts: files mdns4 [NOTFOUND=continue] dns myhostname
• hosts: files dns mdsn4_minimal myhostname
• hosts: dns
• a few others

None of which worked. I tried rebooting after a change too. I tried to tell avahi that the domain-name=alocal in /etc/avahi/avahi-daemon.conf, didn't work after service restart, didn't work after reboot. After this not working, I tried disabling the avahi-daemon service entirely.

sudo systemctl disable avahi-daemon

After a reboot I tried a couple of permutations in /etc/nsswitch.conf again, with no effect.

with my current settings in hosts (files dns) I get this response:

dig login.name.local # not the actual name

; <<>> Dig 9.11.3-1ubuntu1.1-Ubuntu <<>> login.name.local
;; global options: +cmd
;; Got answer:
;; WARNING .local is reserved for Multicast DNS
;; You are currently testing what happens when an mDNS query is leaked to DNS
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33538
;; flags: qr rd ra; QUERY: 1, ANSWER:0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;login.name.local. 0     IN     A

;; Query time: 2msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Thu Aug 23 10:51:50 CEST 2018
;; MSG SIZE  rcvd: 56

However when I instruct dig to query the server directly I get the correct answer:

dig @dnsIP login.name.local
; <<>> Dig 9.11.3-1ubuntu1.1-Ubuntu <<>> login.name.local
; (1 server found)
;; global options: +cmd
;; Got answer:
;; WARNING .local is reserved for Multicast DNS
;; You are currently testing what happens when an mDNS query is leaked to DNS
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57866
;; flags: qr aa rd ra; QUERY: 1, ANSWER:1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;login.name.local. 0     IN     A

;; ANSWER SECTION:
login.name.local. 3600 IN    A        serverIP

;; Query time: 2msec
;; SERVER: dnsIP#53(dnsIP)
;; WHEN: Thu Aug 23 10:51:50 CEST 2018
;; MSG SIZE  rcvd: 56

This version of Ubuntu uses netplan with the network manager. The correct DNS IP is definitely in the list. (in fact it's the primary DNS.) Also the dnsIp is the same as serverIP, but that shouldn't be an issue.

Ping or connecting via browser and such don't work of course. None use the dns query.

I'm at a loss at what to do. Certainly we can't switch to a different domain name. I put the servername into /etc/hosts but that's just a temporary solution.