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

Bug #546846 reported by napster
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
screenlets (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: screenlets

1

ProblemType: Crash
Architecture: i386
AssertionMessage: python: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed.
CrashCounter: 1
Date: Thu Mar 25 14:18:02 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/share/screenlets/Sysmonitor/SysmonitorScreenlet.py
InterpreterPath: /usr/bin/python2.6
Package: screenlets 0.1.2-7ubuntu1
PackageArchitecture: all
ProcCmdline: python -u /usr/share/screenlets/Sysmonitor/SysmonitorScreenlet.py
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
Signal: 6
SourcePackage: screenlets
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: SysmonitorScreenlet.py assert failure: python: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed.
Uname: Linux 2.6.32-17-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
napster (ivo-pcboy) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

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

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in screenlets (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
security vulnerability: yes → no
visibility: private → public
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.