apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses: Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)' failed.

Bug #510245 reported by inkisbetter
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: apport

Keep getting an error about a serious kernal issue on resume from sleep (which takes forever).

ProblemType: Crash
ApportLog:
 apport (pid 27195) Wed Jan 20 08:11:47 2010: called for pid 26834, signal 6
 apport (pid 27195) Wed Jan 20 08:11:47 2010: script: /usr/share/apport/apport-kde, interpreted by /usr/bin/python2.6 (command line "/usr/bin/python /usr/share/apport/apport-kde")
 apport (pid 27195) Wed Jan 20 08:12:08 2010: wrote report /var/crash/_usr_share_apport_apport-kde.0.crash
Architecture: i386
AssertionMessage: python: ../../src/xcb_io.c:242: process_responses: Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)' failed.
Date: Wed Jan 20 08:11:47 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/apport-kde
InterpreterPath: /usr/bin/python2.6
Package: apport-kde 1.9.3-0ubuntu4.2
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/apport/apport-kde
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 LANGUAGE=
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
Signal: 6
SourcePackage: apport
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
 ?? () from /usr/lib/libX11.so.6
Title: apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses: Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)' failed.
Uname: Linux 2.6.31-17-generic i686
UserGroups:

Revision history for this message
inkisbetter (timohen) wrote :
visibility: private → public
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.