synaptic assert failure: synaptic: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed.

[Rachel Greenham]

Binary package hint: synaptic

synaptic seemed to hang after typing 'the' into the search box. (was planning to type more but that's as far as it got.) Used xkill to kill it. Crashed during subsequent startup, which I think is this error. (damaged previous bug report by attempting to restart I think)

ProblemType: Crash
Architecture: i386
AssertionMessage: synaptic: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed.
Date: Thu Feb 18 07:55:13 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/sbin/synaptic
Package: synaptic 0.63.1ubuntu1
ProcAttrCurrent: unconfined (enforce)
ProcCmdline: /usr/sbin/synaptic
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
Signal: 6
SourcePackage: synaptic
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libc.so.6
 abort () from /lib/tls/i686/cmov/libc.so.6
 __assert_fail () from /lib/tls/i686/cmov/libc.so.6
 _XAllocID () from /usr/lib/libX11.so.6
Title: synaptic assert failure: synaptic: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed.
Uname: Linux 2.6.32-13-generic i686
UserGroups:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #507062, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

[Rachel Greenham (rachel-strangenoises)]

It seems to reliably go unresponsive with a search term typed in starting 'the' though i wouldn't be surprised if it's just working hard. (perhaps a short delay to allow for more letters to appear that would narrow it?)

Yes, on second try it eventually sorted itself out anyway; probably notabug, sorry. :-)