You are not logged in.
My computer boots quite fast since I've migrated to systemd, but I'm experiencing a long delay (about 30 seconds) between the GDM autologin (when my background appears) and having a usable GNOME Shell (when the top bar appears).
Since this kind of issue rarely has a unique fix, I would like to ask you for some suggestions to improve the GNOME launch time : what files should I look for errors, what apps should I try to remove or setup differently... This kind of advice could end up in the wiki to help people experiencing the problem. How fast does your GNOME boot ?
Offline
Does using a different login manager (slim, lxdm, xdm, etc) or startx make any difference?
Offline
I didn't try any different login manager yet, but I discovered journalctl, which is a very useful tool to figure out what's going on behind the scenes.
So I tried it (sudo journalctl -b) and got an interesting result : a 20-second gap.
déc. 04 20:55:09 Eggman rtkit-daemon[517]: Successfully made thread 587 of process 587 (/usr/bin/pulseaudio) owned by '1000' high priority at n
déc. 04 20:55:09 Eggman rtkit-daemon[517]: Supervising 2 threads of 2 processes of 1 users.
déc. 04 20:55:09 Eggman pulseaudio[587]: [pulseaudio] pid.c: Daemon already running.
déc. 04 20:55:24 Eggman dbus-daemon[276]: dbus[276]: [system] Failed to activate service 'org.freedesktop.PackageKit': timed out
déc. 04 20:55:24 Eggman dbus[276]: [system] Failed to activate service 'org.freedesktop.PackageKit': timed out
Looks like the 'org.freedesktop.PackageKit' service needs to be disabled, but why does it take so much time to activate ? I'm using gnome-packagekit and I enjoy getting pretty notifications when updates are available. Am I missing something, or is there another area I could investigate in ?
Offline