You are not logged in.
My system is freshly installed 3 weeks ago and now I'm experiencing an issue. The system starts fine but it takes a long time to see the graphical interface of GDM, like say 20 seconds. After typing my password it takes another 20 seconds to display the Gnome-Shell interface.
This post talks about similar problems. But I don't have ConsoleKit installed. Here they talk about the same issue and about Avahi. But I don't really know if I have issues with that. This is a post on Google+ with the same issue.
Does someone have some advice on what I can do to check the cause?
[root@Arch viper]# systemctl status gdm.service
● gdm.service - GNOME Display Manager
Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled)
Active: active (running) since vr 2014-09-05 17:09:19 CEST; 19min ago
Main PID: 414 (gdm)
CGroup: /system.slice/gdm.service
├─414 /usr/bin/gdm
└─761 /usr/bin/Xorg.bin :0 -background none -noreset -verbose 3 -logfile /dev/null -auth /var/run/gdm/auth-for-gdm-wKMBF8/database -seat seat0 -nolisten tcp vt1
sep 05 17:12:11 Arch gdm-Xorg-:0[761]: > Using new definition
sep 05 17:12:11 Arch gdm-Xorg-:0[761]: > Warning: Compat map for group 3 redefined
sep 05 17:12:11 Arch gdm-Xorg-:0[761]: > Using new definition
sep 05 17:12:11 Arch gdm-Xorg-:0[761]: > Warning: Compat map for group 4 redefined
sep 05 17:12:11 Arch gdm-Xorg-:0[761]: > Using new definition
sep 05 17:12:11 Arch gdm-Xorg-:0[761]: Errors from xkbcomp are not fatal to the X server
sep 05 17:12:11 Arch gdm-Xorg-:0[761]: (II) NVIDIA(GPU-0): Display (HP w2408 (CRT-0)) does not support NVIDIA 3D Vision
sep 05 17:12:11 Arch gdm-Xorg-:0[761]: (II) NVIDIA(GPU-0): stereo.
sep 05 17:12:11 Arch gdm-Xorg-:0[761]: (II) NVIDIA(GPU-0): Display (SAMSUNG (DFP-0)) does not support NVIDIA 3D Vision
sep 05 17:12:11 Arch gdm-Xorg-:0[761]: (II) NVIDIA(GPU-0): stereo.[root@Arch viper]# systemd-analyze blame
13.345s man-db.service
7.076s dhcpcd@enp5s0.service
5.348s dkms.service
1.514s dev-disk-by\x2duuid-c14bef07\x2d4b91\x2d4dd4\x2db249\x2d0779323a48b3.swap
1.142s systemd-vconsole-setup.service
1.010s gdm.service
975ms accounts-daemon.service
842ms systemd-modules-load.service
786ms systemd-fsck-root.service
766ms shadow.service
691ms rpcbind.service
596ms logrotate.service
456ms systemd-rfkill@rfkill0.service
382ms polkit.service
344ms media-NAS.mount
333ms dev-hugepages.mount
285ms sys-kernel-debug.mount
284ms dev-mqueue.mount
244ms tmp.mount
193ms systemd-tmpfiles-setup-dev.service
181ms kmod-static-nodes.service
159ms systemd-tmpfiles-setup.service
146ms user@120.service
145ms systemd-user-sessions.service
141ms systemd-journal-flush.service
139ms systemd-logind.serviceLast edited by DarkLite1 (2014-09-05 15:42:08)
Offline
What does your gdm or journalctl log say? If I remember right the GDM one should be at ~/.cache/gdm/session.log and journalctl.. well, that is a command to run in term. Maybe narrow it down to a service like 'sudo journalctl -u gdm.service' or similar.
Offline
Thank you for the tips, but I don't have this folder ~/.cache/gdm.
Journalctl gives me these lines in red, but it's not really using a lot of time. What is very strange is that today I had a very fast boot, almost no problems. And yesterday and the days before it was always slow. Can't get my head around it ...
sep 06 10:54:56 Arch dbus[350]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
sep 06 10:54:56 Arch dbus[350]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory.
sep 06 10:54:56 Arch pulseaudio[1255]: GetManagedObjects() failed: org.freedesktop.systemd1.LoadFailed: Unit dbus-org.bluez.service failed to load: No such file or directory.
sep 06 10:54:56 Arch rtkit-daemon[1102]: Successfully made thread 1286 of process 1286 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
sep 06 10:54:56 Arch rtkit-daemon[1102]: Supervising 5 threads of 2 processes of 2 users.
sep 06 10:54:56 Arch pulseaudio[1286]: [pulseaudio] pid.c: Daemon already running.Offline
I am not sure about the gdm log... was awhile since I used Gnome. Am using Bspwm nowadays... Anyway.. The journalctl command was just an example to see one unit. In this case the gdm one. You could do a 'journalctl -b' to see the whole last boot. If you want a less verbose you could try ' sudo journalctl -b -l -o short-monotonic -p 4 --no-pager' or 'sudo journalctl -b -l -o short-monotonic -p 5 --no-pager' but that might miss something. I am guessing you have something that times out. It is possible you could find something with 'dmesg -deL' but that is usually for investigating hardware errors. I believe it is something with Xorg..
Offline
It's very bizarre, because this morning I booted again and that's the second time in a row that there's no slowdown on boot. So I guess, one way or another, it fixed itself. When it happens again, I'll sure try your journalctl suggestions. I'm not used to using systemd debugging, so thanks for the help there. Let's hope for this as things are back to normal now.
Offline
If it happens again, switch to a VT during logging in and run top and iotop. That might give you hint as to what's going on.
Offline