Description of problem: $ /usr/libexec/gnome-settings-daemon --debug --no-daemon [skip] Gdk-ERROR **: The program 'gnome-settings-daemon' received an X Window System error. This probably reflects a bug in the program. The error was 'BadRequest (invalid request code or no such operation)'. (Details: serial 111 error_code 1 request_code 153 minor_code 25) (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.) aborting... Trace/breakpoint trap Version-Release number of selected component (if applicable): 2.25.3-2.fc11 and 2.25.3-4.fc11( in koji) How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: gnome-desktop-2.25.5-1.fc11.i386
I am getting the same with gnome-settings-daemon-2.25.3-4.fc11.x86_64. The only difference is that in "details" that prints: (Details: serial 110 error_code 1 request_code 149 minor_code 25) On a terminal this is also preceded by lines: Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". The later is a general affliction which was already reported as bug 478607 and I do not know if these errors are only coincidental or not.
Seenhere as well: The program 'gnome-settings-daemon' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 904 error_code 8 request_code 20 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.) found in the .xsession-errors file. It doesn't happen in a predictable manner, most times it works fine.
Can one of you perhaps do what the error message asks you to do, and attach the resulting stacktrace here ?
(In reply to comment #3) > Can one of you perhaps do what the error message asks you to do, and attach the > resulting stacktrace here ? Where is g-s-d started, so I can append the necessary cmdline options?
Re comment #3: > Can one of you perhaps do what the error message asks I actually tried that with gnome-settings-daemon-debuginfo loaded and did not get very far. Even if help says "--no-daemon Don't become a daemon" running that with options "--no-daemon --debug --sync" under gdb was not of much use. g-s-d says that it goes into background and terminates and that is about it. "No process running".
I did not get a reasonable backtrace but I am collecting in logs messages like this: gnome-settings-[2849] trap int3 ip:33fbe41bb6 sp:7fff9d442f50 error:0 There is always consistently "ip:33fbe41bb6" with values of sp varying quite a bit (load randomization effects?).
It happens in Fedora 10 x86_64 as well. The funny thing is that is dies during login, but can be restarted easily (by typing gnome-settings-daemon in the terminal).
Sorry, I meant by going to appearance prefs.
> but can be restarted easily (by typing gnome-settings-daemon in the terminal). Not for me. The original report is really copy-pasted from a terminal and I am getting basically the same thing too. It dies also when run under gdb but in some spawned process or a thread, even if '--no-daemon' option was given I was unable to catch that. gdb claims that it has no knowlegde of gdk_x_error() and grepping through /usr/include does not reveal its presence either so I have no idea which library may possibly be providing it.
After an update to libX11-1.1.99.2-3.fc11 messages Xlib: extension "Generic Event Extension" missing on display ":0.0". vanished from ~/.xsession-errors and local terminal windows and gnome-settings-daemon actually starts and runs. At least on my system. This is not an update of g-s-d as the last one here was on 2009-01-21.
Update gnome-settings-daemon-2.25.90-2.fc11 < http://koji.fedoraproject.org/koji/buildinfo?buildID=81647 > $ gdb /usr/libexec/gnome-settings-daemon GNU gdb (GDB) Fedora (6.8.50.20081214-1.fc11) Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i386-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... (gdb) r --no-daemon Gdk-ERROR **: The program 'gnome-settings-daemon' received an X Window System error. This probably reflects a bug in the program. The error was 'BadRequest (invalid request code or no such operation)'. (Details: serial 111 error_code 1 request_code 153 minor_code 25) (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.) aborting... Program received signal SIGTRAP, Trace/breakpoint trap. IA__g_logv (log_domain=0xa16414 "Gdk", log_level=G_LOG_LEVEL_ERROR, format=0xa33273 "%s", args1=0xbfffefcc "�p\t\b\001") at gmessages.c:503 503 g_private_set (g_log_depth, GUINT_TO_POINTER (depth)); Starting program: /usr/libexec/gnome-settings-daemon --no-daemon [Thread debugging using libthread_db enabled] Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". (gdb) bt #0 IA__g_logv (log_domain=0xa16414 "Gdk", log_level=G_LOG_LEVEL_ERROR, format=0xa33273 "%s", args1=0xbfffefcc "�p\t\b\001") at gmessages.c:503 #1 0x00853c26 in IA__g_log (log_domain=0xa16414 "Gdk", log_level=G_LOG_LEVEL_ERROR, format=0xa33273 "%s") at gmessages.c:517 #2 0x009fe264 in gdk_x_error (display=0x8063a00, error=0xbffff078) at gdkmain-x11.c:641 #3 0x00f0b979 in _XError (dpy=0x8063a00, rep=0x808cb78) at XlibInt.c:2931 #4 0x00f13926 in _XReply (dpy=0x8063a00, rep=0xbffff1c0, extra=0, discard=0) at xcb_io.c:506 #5 0x0080e6c5 in doGetScreenResources (dpy=0x8063a00, window=315, poll=0) at XrrScreen.c:86 #6 0x00b26f42 in fill_out_screen_info (error=<value optimized out>, info=<value optimized out>, xroot=<value optimized out>, xdisplay=<value optimized out>) at gnome-rr.c:366 #7 screen_info_new (screen=<value optimized out>, error=0xbffff3c0) at gnome-rr.c:465 #8 0x00b27deb in gnome_rr_screen_new (gdk_screen=0x80720c8, callback=0xb0bea0 <on_randr_event>, data=0x8076440, error=0xbffff3c0) at gnome-rr.c:559 #9 0x00b0b45d in gsd_xrandr_manager_start (manager=0x8076440, error=0xbffff3c0) at gsd-xrandr-manager.c:1371 #10 0x00b0926f in impl_activate (plugin=0x8087918) at gsd-xrandr-plugin.c:78 #11 0x0804d19f in _activate_plugin (info=<value optimized out>) at gnome-settings-plugin-info.c:497 #12 gnome_settings_plugin_info_activate (info=0x8071958) at gnome-settings-plugin-info.c:520 #13 0x0804babe in maybe_activate_plugin (info=0x8071958, user_data=0x0) at gnome-settings-manager.c:94 #14 0x00869467 in IA__g_slist_foreach (list=0x8082130, func=0x804baa0 <maybe_activate_plugin>, user_data=0x0) at gslist.c:743 #15 0x0804bdce in _load_all (manager=<value optimized out>) at gnome-settings-manager.c:263 #16 gnome_settings_manager_start (manager=0x8063260, error=0xbffff4c0) at gnome-settings-manager.c:349 #17 0x0804b855 in main (argc=134727560, argv=0x1) at main.c:478 (gdb) After disabling xrandr plugin, gnome-settings-daemon works well.
*** Bug 490286 has been marked as a duplicate of this bug. ***
gnome-rr.c lives in gnome-desktop, reassigning. I believe this bug has already been fixed though.
It still occurs in F-10 sometimes, but much less often. I'm not sure if it's the same bug, though.
Just for the record, I could reproduce this consistently on F-10 the first time logging into my account after a reboot.
I can confirm this bug on FC-10. Besides the reverting to the default theme setting, I also get one single workspace instead of the usual 4.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
(Details: serial 111 error_code 1 request_code 153 minor_code 25) RANDR minor code 25 is RRGetScreenResourcesCurrent. You're sending a 1.3 request to a 1.2 server. Of course, I have no idea how you'd be doing that, since the code in libgnome-desktop does appear to DTRT.
For the record, while I was hitting the issue on Fedora 10 (bug 479196), with Fedora 11 on EEE PC 1000, the problem does not seem to be present anymore. Could the original poster confirm if the problem has been fixed on latest Fedora 11 in their environment as well?
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.