GTK programs started acting really badly after a recent rawhide update + system restart. As in I couldn't login anymore. That combined with the evdev breakage (ctrl-alt-f1 and backspace did nothing) made for a really fun (not) recovery, only way of getting to a text console was either rapidly pressing ctrl-alt-f1 after logging into gdm or booting into runlevel 3. When starting the programs up The program 'gnome-session' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 21 error_code 3 request_code 2 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) ends up in .xsession-errors (or stderr if you run them manually). Most of the time. Occasionally the program starts up just fine. xterm/twm and KDE are fine. In fact, if you start up KDE the GTK apps start up just fine there (xterm+twm don't have that effect). Running the programs under gdb or ltrace also seemed to make them nearly always. Will poke a bit more later... -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
