Created attachment 510296 [details]
/var/log/messages beginning at GDM
Description of problem: Graphical login crashes before choosing userID and getting password.
Version-Release number of selected component (if applicable):
How reproducible: every time (5 times so far)
Steps to Reproduce:
1. boot to default multi-user graphical login
Actual results: Background splash screen (night sky, aurora, moon, tree with two birds [one "mechanical"]) appears twice and persists. "Login" appears in style of XFCE (GNOME was default) but then "Login" disappears. Mouse does move the pointer, but there is nothing to click; keyboard gets no response. Complaints from gdm-simple-greeter appear in /var/log/messages, with tracebacks.
Expected results: Usual login with no crash.
Created attachment 510299 [details]
[ 40.120] (--) PCI:*(0:1:0:0) 1002:9540:174b:e970 rev 0, Mem @ 0xd0000000/268435456, 0xfe8e0000/65536, I/O @ 0x0000b000/256, BIOS @ 0x????????/131072
01:00.0 VGA compatible controller : ATI Technologies Inc RV710 [Radeon HD 4550] [1002:9540]
it's a bug in the accessibility stack that gdm is hitting because it gets crashy on fatal-criticals in development versions.
I don't like that behaviour, so I've switched it off:
which i'll build into rawhide shortly.
Reassigning to gail for the actual
Gtk-CRITICAL: gtk_widget_get_mapped: assertion `GTK_IS_WIDGET (widget)' failed
*** This bug has been marked as a duplicate of bug 716365 ***
unduping, since bug 716365 is assigned to GDM and I put the bug in gtk3
Using today's new gdm-3.1.2-3.fc16.x86_64 I can now login and get Gnome desktop; thank you, Ray.
/var/log/messages still shows the complaints (with traceback):
Jun 29 06:19:07 f16r64 gdm-simple-greeter: Gtk-CRITICAL: gtk_widget_get_mapped: assertion `GTK_IS_WIDGET (widget)' failed#012aborting...
Created attachment 510525 [details]
gdm-3.1.2-3.fc16 did not fix this for me, if this attachment shows the sqme error. Description comment matches what I am seeing.
The last working gdm for me is: gdm-3.0.0-2.fc16.x86_64
Define 'fix'. The 'fix' in -3.fc16 is simply not to abort when this error happens. So the error still happens and is still logged, but that does not prevent gdm running. If gdm is not working for you, it's probably because of something else, now.
The original issue has been fixed here.