GNOME Bugzilla – Bug 146140
X Window System error
Last modified: 2009-08-15 18:40:50 UTC
Distribution: Debian testing/unstable Package: control-center Severity: critical Version: GNOME2.6.1 2.6.x Gnome-Distributor: Debian Synopsis: X Window System error Bugzilla-Product: control-center Bugzilla-Component: settings-daemon Bugzilla-Version: 2.6.x Description: Description of Problem: gnome-settings-daemon terminates because of an X Window System error. Steps to reproduce the problem: 1. launch gnome-settings-daemon Actual Results: Doesn't apply settings and outputs this in console: 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 112 error_code 1 request_code 0 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.) Expected Results: Start gracefully and apply settings. How often does this happen? Always. Additional Information: When launched without any argument in gdb: Program received signal SIGSEGV, Segmentation fault.
+ Trace 47724
Thread 1088496384 (LWP 1149)
When lauched with --sync: [error output in console] Program exited with code 01. ------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-08 20:21 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "control-center". Setting to default milestone for this product, '---' Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
May be a duplicate of bug 143292.
Can you still reproduce this or has it been fixed? It could be broken X-server packages in debian testing from the look of the backtrace...
Fixed. Thank you.
ok, so bug closed, thanks.