PicframeScreenlet.py assert failure: python: ../../src/xcb_io.c:385: _XAllocID: Проверочное утверждение «ret != inval_id» не выполнено.

Bug #721655 reported by Anton
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
screenlets (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: screenlets

PicframeScreenlet.py assert failure: python: ../../src/xcb_io.c:385: _XAllocID: Проверочное утверждение «ret != inval_id» не выполнено.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: screenlets 0.1.2-7ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-3.30-generic 2.6.38-rc4
Uname: Linux 2.6.38-3-generic i686
Architecture: i386
AssertionMessage: python: ../../src/xcb_io.c:385: _XAllocID: Проверочное утверждение «ret != inval_id» не выполнено.
Date: Sat Feb 19 09:19:09 2011
ExecutablePath: /usr/share/screenlets/Picframe/PicframeScreenlet.py
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: python -u /usr/share/screenlets/Picframe/PicframeScreenlet.py
ProcEnviron:
 LANGUAGE=ru_RU:ru:en_GB:en
 LANG=ru_RU.UTF-8
 LC_MESSAGES=ru_RU.utf8
 SHELL=/bin/bash
Signal: 6
SourcePackage: screenlets
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/libc.so.6
 abort () from /lib/libc.so.6
 __assert_fail () from /lib/libc.so.6
 _XAllocID () from /usr/lib/libX11.so.6
Title: PicframeScreenlet.py assert failure: python: ../../src/xcb_io.c:385: _XAllocID: Проверочное утверждение «ret != inval_id» не выполнено.
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Anton (welderx) wrote :
Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 507062, so it 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.

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.