Summary: twice, bug happened when service org.gtk.vfs.Daemon is activating *after* org.a11y.atspi.Registry is activated.
Details below.
Bug just happened again on unlocking session (versus switching users).
I compared the output of journalctl.
## Around unlock time: nothing to see
Around unlock time, journalctl only shows lightdm cleanup activity. Then, only when bug happens, lightdm starts again the whole sequence :
systemd[somepid]: Starting User Manager for UID 110...
systemd-logind[749]: New session c9 of user lightdm.
systemd[somepid]: Started Session c9 of user lightdm.
...
## Around lock time: same correlation between log order and bug occurrence
Again
Indeed, bug happens when log is in this order:
at-spi-bus-launcher[25560]: dbus-daemon[25565]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=110 pid=25557 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined")
at-spi-bus-launcher[25560]: dbus-daemon[25565]: Successfully activated service 'org.a11y.atspi.Registry'
at-spi-bus-launcher[25560]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
dbus-daemon[25559]: [session uid=110 pid=25559] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.4' (uid=110 pid=25557 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined")
and things go smoothly when log is in this order:
at-spi-bus-launcher[15685]: dbus-daemon[15690]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=110 pid=15682 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined")
dbus-daemon[15684]: [session uid=110 pid=15684] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.3' (uid=110 pid=15682 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined")
at-spi-bus-launcher[15685]: dbus-daemon[15690]: Successfully activated service 'org.a11y.atspi.Registry'
at-spi-bus-launcher[15685]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Summary: twice, bug happened when service org.gtk.vfs.Daemon is activating *after* org.a11y.atspi.Registry is activated.
Summary: twice, bug happened when service org.gtk.vfs.Daemon is activating *after* org.a11y. atspi.Registry is activated.
Details below.
Bug just happened again on unlocking session (versus switching users).
I compared the output of journalctl.
## Around unlock time: nothing to see
Around unlock time, journalctl only shows lightdm cleanup activity. Then, only when bug happens, lightdm starts again the whole sequence :
systemd[somepid]: Starting User Manager for UID 110... logind[ 749]: New session c9 of user lightdm.
systemd-
systemd[somepid]: Started Session c9 of user lightdm.
...
## Around lock time: same correlation between log order and bug occurrence
Again
Indeed, bug happens when log is in this order:
at-spi- bus-launcher[ 25560]: dbus-daemon[25565]: Activating service name='org. a11y.atspi. Registry' requested by ':1.0' (uid=110 pid=25557 comm="/ usr/sbin/ lightdm- gtk-greeter " label="unconfined") bus-launcher[ 25560]: dbus-daemon[25565]: Successfully activated service 'org.a11y. atspi.Registry' bus-launcher[ 25560]: SpiRegistry daemon is running with well-known name - org.a11y. atspi.Registry gtk.vfs. Daemon' unit='gvfs- daemon. service' requested by ':1.4' (uid=110 pid=25557 comm="/ usr/sbin/ lightdm- gtk-greeter " label="unconfined")
at-spi-
at-spi-
dbus-daemon[25559]: [session uid=110 pid=25559] Activating via systemd: service name='org.
and things go smoothly when log is in this order:
at-spi- bus-launcher[ 15685]: dbus-daemon[15690]: Activating service name='org. a11y.atspi. Registry' requested by ':1.0' (uid=110 pid=15682 comm="/ usr/sbin/ lightdm- gtk-greeter " label="unconfined") gtk.vfs. Daemon' unit='gvfs- daemon. service' requested by ':1.3' (uid=110 pid=15682 comm="/ usr/sbin/ lightdm- gtk-greeter " label="unconfined") bus-launcher[ 15685]: dbus-daemon[15690]: Successfully activated service 'org.a11y. atspi.Registry' bus-launcher[ 15685]: SpiRegistry daemon is running with well-known name - org.a11y. atspi.Registry
dbus-daemon[15684]: [session uid=110 pid=15684] Activating via systemd: service name='org.
at-spi-
at-spi-
Summary: twice, bug happened when service org.gtk.vfs.Daemon is activating *after* org.a11y. atspi.Registry is activated.