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

[transcepter]

Binary package hint: evolution

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

ProblemType: Crash
Architecture: i386
AssertionMessage: evolution: ../../src/xcb_io.c:378: _XAllocID: Assertion `ret != inval_id' failed.
Date: Fri Oct 23 14:27:58 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/evolution
Package: evolution 2.28.1-0ubuntu1
ProcCmdline: evolution --component=mail
ProcEnviron:
 LANGUAGE=ru_RU.UTF-8
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
Signal: 6
SourcePackage: evolution
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: evolution assert failure: evolution: ../../src/xcb_io.c:378: _XAllocID: Assertion `ret != inval_id' failed.
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:__kernel_vsyscall ()
*__GI_raise (sig=6)
*__GI_abort () at abort.c:92
*__GI___assert_fail (assertion=0x81eb65 "ret != inval_id",
_XAllocID (dpy=0x8526618) at ../../src/xcb_io.c:378

[Bryce Harrington (bryce)]

Hi transcepter,

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISO CD images are available from http://cdimage.ubuntu.com/releases/)

If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
Thanks in advance.

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

[Pako (elektrobank01)]

I don't think that I can reproduce this crash again, everything seems fine
now so you can close this bug immediately. Thanks!

[Bryce Harrington (bryce)]

Thanks for letting us know the issue is resolved.