Red Hat Bugzilla – Bug 476929
WLAN on boot breaks GDM/greeter
Last modified: 2009-04-17 17:32:19 EDT
Description of problem:
Enabling the new system-connections feature (with the keyfile plugin) on a wireless connection causes GDM to fail on boot (X loads, but the cursor spins endlessly, greeter never comes up). Logs indicate gnome-settings-daemon etc being unable to connect to display :0
As a test, I tried the identical configuration, but with a wired connection, and everything worked, so I think what's happening is that the longer time it takes to bring up wireless vs wired results in the connection being in partially-connected state when GDM starts.
If I boot into runlevel 3, wait for NM to finish brining up the connection, then telinit to runlevel 5, it works, which seems to confirm the above suspicion.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Change /etc/NetworkManager/nm-system-settings.conf to read "plugins=keyfile"
2. Apply appropriate PolicyKit voodoo
3. In nm-connection-editor, check "available to all users" and "connect automatically" on a wireless connection.
GDM's X session loads, but the greeter never comes up.
GDM greeter, successful login, world peace.
I'm not sure whether this bug should be filed against GDM in addition to/instead of NetworkManager.... or is it gnome-session, Xorg, something else?
Sample log entries:
AUDIT: Wed Dec 17 16:49:55 2008: 2133 Xorg: client 8 rejected from local host ( uid=42 gid=42 pid=2288 )
Window manager warning: Failed to read saved session file /var/lib/gdm/.config/metacity/sessions/107defc4414717b4f51229561347$
** (process:2299): DEBUG: Greeter session pid=2299 display=:0.0 xauthority=/var/run/gdm/auth-for-gdm-E8x3L6/database
No protocol specified
gdm-simple-greeter: Gtk-WARNING: cannot open display: :0.0
This is probably hostname related; GDM doesn't handle hostname changes very well. Could you try assigning a hostname in /etc/sysconfig/network like so?
and then see if this problem continues?
This bug has been triaged
Fedora Bugzappers volunteer triage team
Duplicate of #441453?
*** This bug has been marked as a duplicate of bug 441453 ***