After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 146140 - X Window System error
X Window System error
Status: VERIFIED INCOMPLETE
Product: gnome-control-center
Classification: Core
Component: [obsolete] settings-daemon
2.6.x
Other other
: Normal critical
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-05-28 16:38 UTC by David Munger
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6



Description David Munger 2004-07-09 00:21:30 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.

Thread 1088496384 (LWP 1149)

  • #0 XRenderQueryFormats
    from /usr/lib/libXrender.so.1
  • #1 XRenderFindVisualFormat
    from /usr/lib/libXrender.so.1
  • #2 _XftDisplayInfoGet
    from /usr/lib/libXft.so.2
  • #3 XftDefaultHasRender
    from /usr/lib/libXft.so.2
  • #4 ??
  • #5 ??
  • #6 ??
  • #7 _XftDisplayManageMemory
    from /usr/lib/libXft.so.2


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.

Comment 1 Elijah Newren 2004-11-08 20:07:32 UTC
May be a duplicate of bug 143292.
Comment 2 Kjartan Maraas 2004-12-30 14:40:50 UTC
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...
Comment 3 David Munger 2004-12-31 01:40:43 UTC
Fixed. Thank you.
Comment 4 Sebastien Bacher 2004-12-31 11:28:35 UTC
ok, so bug closed, thanks.