[Touch-packages] [Bug 2033569] Re: suddenly choked on multiseat config in a way that survives reboots and even purging it

Found a solution. There were two separate issues: FIRST ISSUE Apparently systemd likes to start up lightdm early, so early that on a reasonably fast system the GPU driver won't be ready in time ... (I thought this was what systemd's dependency handling was for, but never mind.) This seems to b

[Touch-packages] [Bug 2033569] Re: suddenly choked on multiseat config in a way that survives reboots and even purging it

gpu-manager.service is probably a red herring, or a separate bug. I (sometimes?) get "Error: can't access /sys/bus/pci/devices/:6e:00.0/driver \ The device is not bound to any driver." when booting with gdm as well; yet gpu-manager.service doesn't fail, and gdm comes up normally. I -- You

[Touch-packages] [Bug 2033569] [NEW] suddenly choked on multiseat config in a way that survives reboots and even purging it

Public bug reported: I have a bog-standard loginctl multiseat setup, using lightdm because of #2033323. Except for the lack of session locking, it worked beautifully, across multiple reboots. Until it didn't. Box woke from suspend, and to be fair was acting strangely even then (Steam suddenly tri

[Touch-packages] [Bug 1849680] [NEW] audit spam in dmesg (libreoffice)

Public bug reported: My dmesg is getting flooded by apparmor audit messages, mostly from libreoffice (profiles libreoffice-soffice and libreoffice-oosplash): $ dmesg | tail -n 25 [13682.452555] audit: type=1400 audit(1571920851.001:3672): apparmor="ALLOWED" operation="open" profile="libreoffice-