Dear maintainer,
I had been stuck for 10days with a 50s pause just after user login, in lightdm
(used to launch kde5).
Looking to logs using journalctl i finally noticed that the 50s pause was
happening not very far after:
Oct 25 17:32:28 host-32-141 dbus-daemon[1762]: [session uid=1000 pid=1760]
Activating service name='org.freedesktop.Notifications' requested by ':1.3'
(uid=1000 pid=1778 comm="notify-send VBoxClient: the VirtualBox kernel serv")
No other entry after this one was related to VirtualBox: so it was difficult to
pinpoint the problem was coming from it.
The actual delay, in this example, was exactly 50s between the line above and:
Oct 25 17:33:19 host-32-141 dbus-daemon[699]: [system] Activating via systemd:
service name='org.freedesktop.UPower' unit='upower.service' requested by
':1.38' (uid=1000 pid=1846 comm="kded5 [kdeinit5]")
Its only after purging all packages related to virtualbox:
virtualbox-dkms virtualbox-guest-x11 virtualbox-guest-dkms virtualbox-qt
iso virtualbox
that the 50s pause vanished.
Reinstalling these packages did *not* induce this pause again: so this seems to
be related to how systemd & dbus were activating virtualbox.
I still report this as a bug as this was quite hard to find, and other users
might be affected. It seems that there was an update of virtualbox which the
start up of virtualbox was not set up to date, until the purge/reinstallation.
Best,
Ara
Note: installing linux-image-4.14.0-rc5-amd64 / experimental did not change any
behaviour, before the purge. So, recompiling the -dkms was not sufficient to
solve the problem.