A server running ThinLinc 4.11.0 on Ubuntu 16.04 had Ubuntu upgraded to 18.04. After this all sessions are thrown out after clicking OK on the "Welcome to ThinLinc dialog with the following in the server system log:
Feb 6 16:56:06 crux dbus-daemon: [session uid=1000 pid=5710] AppArmor D-Bus mediation is enabled
Feb 6 16:56:06 crux dbus-daemon: [session uid=1000 pid=5710] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=1000 pid=5713 comm="dbus-update-activation-environment --systemd DISPL" label="unconfined")
Feb 6 16:56:06 crux dbus-daemon: [session uid=1000 pid=5710] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Feb 6 16:56:09 crux dbus-daemon: [session uid=1000 pid=5710] Activating service name='org.freedesktop.systemd1' requested by ':1.1' (uid=1000 pid=5818 comm="dbus-update-activation-environment --systemd --all" label="unconfined")
Feb 6 16:56:09 crux dbus-daemon: [session uid=1000 pid=5710] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Rerunning tl-config had no effect.
I could not find anything in the documentation regarding upgrades. Is there something I missed?
We'll need to see the session log (xinit.log) from one of these sessions to debug things further. You might want to send it to our support address instead if you don't want to share it publicly.
Created attachment 919 [details]
xinit.log from failed session
Only exposing my own session, so it's GDPR safe
The issue is here:
> Executing XDG session command: init --user
> init: unrecognized option '--user'
This is something we've seen before (bug 7168) but haven't pinpointed the cause of. Somehow something goes wrong with the upgrade of upstart. It's odd that it happens between 16.04 and 18.04 though. We would have expected it when upgrading from 14.04 (i.e. when switching to systemd).
Can you check if the file /etc/upstart-xsessions exists? And if it does, which package owns it? You can check this by running "dpkg-query -S /etc/upstart-xsessions".
zino@crux:~$ ls -l /etc/upstart-xsessions
-rw-r--r-- 1 root root 270 Feb 29 2016 /etc/upstart-xsessions
zino@crux:~$ dpkg-query -S /etc/upstart-xsessions
The notes for this machine states that it was originally installed with 14.04 in Jan 2016 and upgraded to 16.04 later that year.
Alright, that explains the bad behaviour partially then at least. I would have expected ThinLinc to try to use upstart in that case.
Does /usr/sbin/upstart exist? And is it found if you do "which upstart" as a normal user?
If it doesn't exist, then what does "dpkg-query -s upstart" say?
zino@crux:~$ ls -l /usr/sbin/upstart
ls: cannot access '/usr/sbin/upstart': No such file or directory
zino@crux:~$ dpkg-query -s upstart
Status: deinstall ok config-files
Maintainer: James Hunt <firstname.lastname@example.org>
Replaces: init-system-helpers (<< 1.24ubuntu1), startup-tasks, system-services, sysvinit, upstart-bin (<< 1.13.2-0ubuntu10~), upstart-job
Provides: startup-tasks, system-services, upstart-compat-sysv, upstart-job
Depends: libc6 (>= 2.15), libcgmanager0 (>= 0.28), libdbus-1-3 (>= 1.9.14), libjson-c2 (>= 0.10), libnih-dbus1 (>= 1.0.0), libnih1 (>= 1.0.0), libudev1 (>= 183), sysvinit-utils, initscripts, mountall, ifupdown (>= 0.6.10ubuntu5), debianutils (>= 4)
Suggests: python3, graphviz, bash-completion, upstart-monitor
Breaks: friendly-recovery (<< 0.2.13), initramfs-tools (<< 0.103ubuntu8), libc6 (<< 2.12.1-0ubuntu12), upstart-bin (<< 1.13.2-0ubuntu10~)
Conflicts: lxcguest, startup-tasks, system-services, sysvinit, upstart-job
/etc/bash_completion.d/upstart 080f7eee4a3f3e5f76197eaa581fb4da obsolete
Description: event-based init daemon - essential binaries
upstart is a replacement for the /sbin/init daemon which handles
starting of tasks and services during boot, stopping them during
shutdown and supervising them while the system is running.
This package provides all essential upstart components, sufficient
for running user sessions managed by upstart.
Orig-Maintainer: Steve Langasek <email@example.com>
Ah, all right. The problem is that upstart is uninstalled but its config files remain.
We can see if we can handle this case in the future. Until then you can work around this by doing `dpkg --purge upstart` which should remove the stray config files.
Worked perfectly. Thanks for the help!