GNOME Bugzilla – Bug 669135
gdm is really slow due to --debug option
Last modified: 2012-01-31 23:02:56 UTC
Created attachment 206549 [details] messages.log from last restart Reported on my distro buglist. Gdm is really slow on startup and in the logs there is a lot of debug information. As suggested from the devs in Arch linux I should report it here. Here's the link for the bug in Arch linux: https://bugs.archlinux.org/task/28202 $ pacman -Qi gdm Name : gdm Version : 3.2.1.1-1 URL : http://www.gnome.org Licenses : GPL Groups : gnome-extra Provides : None Depends On : libcanberra libxklavier gnome-session gnome-settings-daemon metacity upower accountsservice consolekit xorg-xrdb nss Optional Deps : gnome-shell: new login interface Required By : awesome-gnome Conflicts With : None Replaces : None Installed Size : 6659.00 KiB Packager : Jan Alexander Steffens (heftig) <jan.steffens@gmail.com> Architecture : x86_64 Build Date : Wed 19 Oct 2011 05:59:55 PM BST Install Date : Mon 26 Dec 2011 11:42:01 AM GMT Install Reason : Explicitly installed Install Script : Yes Description : Gnome Display Manager (a reimplementation of xdm) Let me know if you require further information.
What does the highly subjective "really slow" mean (time, hardware)?
My system is an 8-core amd (AMD FZ-8120) running with 8GB of memory 1866Mhz DDR3. The root is on SSD (and the /home) on btrfs (and ext4) file systems. The gdm used to load almost intantly, just the time for my screen to change resolution from terminal's framebuffer to native resulution. Now I see seconds of black screen (usually 15-20 secs). You can see details on the attached logs.
note it's not the --debug option that makes your system really slow, it's the --debug option that helps us figure out what's going wrong with a system (for instance, why it might be slow). A lot of messages doesn't mean a lot of time spent. In this case it doesn't seem to have anything to do with gdm though: Jan 31 19:24:32 localhost dbus[609]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper) ... Jan 31 19:24:37 localhost dbus[609]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Jan 31 19:24:57 localhost dbus[609]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out Jan 31 19:24:57 localhost dbus[609]: [system] Failed to activate service 'org.freedesktop.ConsoleKit': timed out The system is trying to start ConsoleKit and Avahi. Neither one wants to start, so it gives up after 20 seconds. So I'd investigate why those aren't starting and you should hopefully get your time back.