systemsettings assert failure: systemsettings: ../../src/xcb_io.c:445: _XReply: Afirma??o `!dpy->xcb->reply_data' falhou.

[Nerivaldo J. da Costa]

Binary package hint: kdebase-workspace

System settings crash

ProblemType: Crash
Architecture: amd64
AssertionMessage: systemsettings: ../../src/xcb_io.c:445: _XReply: Afirmação `!dpy->xcb->reply_data' falhou.
Date: Thu Oct 1 23:12:12 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/systemsettings
Package: systemsettings 4:4.3.1-0ubuntu14
ProcCmdline: /usr/bin/systemsettings -caption Configurações\ do\ sistema -icon preferences-system
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
Signal: 6
SourcePackage: kdebase-workspace
StacktraceTop:
 raise () from /lib/libc.so.6
 abort () from /lib/libc.so.6
 __assert_fail () from /lib/libc.so.6
 _XReply () from /usr/lib/libX11.so.6
 XQueryExtension () from /usr/lib/libX11.so.6
Title: systemsettings assert failure: systemsettings: ../../src/xcb_io.c:445: _XReply: Afirmação `!dpy->xcb->reply_data' falhou.
Uname: Linux 2.6.31-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:*__GI_raise (sig=<value optimized out>)
*__GI_abort () at abort.c:92
*__GI___assert_fail (
_XReply (dpy=0xf1f340, rep=0x7fff4150f160, extra=0,
XQueryExtension (dpy=0xf1f340,

[Jonathan Thomas (echidnaman)]

Appears to be a libX11/libxcb issue.

[Bryce Harrington (bryce)]

Hi neribh,

Thanks for including the attached files. Could you also include your /var/log/Xorg.0.log (or Xorg.0.log.old) from after reproducing the issue?

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Timo Aaltonen (tjaalton)]

Assuming this is in libxcb not libx11.

[Timo Aaltonen (tjaalton)]

Install libgl1-mesa-glx-dbg and get a new backtrace.

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.