apport-gtk assert failure: python3: ../../src/xcb_io.c:273: poll_for_event: La declaracin `!xcb_xlib_threads_sequence_lost' no se cumple.

Bug #1042532 reported by Angel Guzman Maeso
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
New
Medium
Unassigned

Bug Description

Reporting a bug about compiz this crash happens.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: apport-gtk 2.5.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1
Uname: Linux 3.5.0-10-generic i686
ApportLog:
 ERROR: apport (pid 11806) Tue Aug 28 06:06:29 2012: called for pid 4261, signal 6, core limit 0
 ERROR: apport (pid 11806) Tue Aug 28 06:06:29 2012: script: /usr/share/apport/apport-gtk, interpreted by /usr/bin/python3.2mu (command line "/usr/bin/python3 /usr/share/apport/apport-gtk")
 ERROR: apport (pid 11806) Tue Aug 28 06:06:29 2012: debug: session gdbus call: (true,)

 ERROR: apport (pid 11806) Tue Aug 28 06:06:52 2012: wrote report /var/crash/_usr_share_apport_apport-gtk.1000.crash
ApportVersion: 2.5.1-0ubuntu2
Architecture: i386
AssertionMessage: python3: ../../src/xcb_io.c:273: poll_for_event: La declaracin `!xcb_xlib_threads_sequence_lost' no se cumple.
Date: Tue Aug 28 06:06:29 2012
ExecutablePath: /usr/share/apport/apport-gtk
InstallationMedia:

InterpreterPath: /usr/bin/python3.2mu
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
ProcEnviron:
 PATH=(custom, no user)
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: apport
StacktraceTop:
 __assert_fail_base (fmt=0xb5fab76d <Address 0xb5fab76d out of bounds>, assertion=0xb6880e90 "!xcb_xlib_threads_sequence_lost", file=0xb68810ea "../../src/xcb_io.c", line=273, function=0xb68811d8 "poll_for_event") at assert.c:94
 __GI___assert_fail (assertion=0xb6880e90 "!xcb_xlib_threads_sequence_lost", file=0xb68810ea "../../src/xcb_io.c", line=273, function=0xb68811d8 "poll_for_event") at assert.c:103
 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
 _XEventsQueued () from /usr/lib/i386-linux-gnu/libX11.so.6
Title: apport-gtk assert failure: python3: ../../src/xcb_io.c:273: poll_for_event: La declaracin `!xcb_xlib_threads_sequence_lost' no se cumple.
UpgradeStatus: Upgraded to quantal on 2012-06-05 (83 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape vboxusers video

Revision history for this message
Angel Guzman Maeso (shakaran) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __assert_fail_base (fmt=0xb5fab76d <Address 0xb5fab76d out of bounds>, assertion=0xb6880e90 "!xcb_xlib_threads_sequence_lost", file=0xb68810ea "../../src/xcb_io.c", line=273, function=0xb68811d8 "poll_for_event") at assert.c:94
 __GI___assert_fail (assertion=assertion@entry=0xb6880e90 "!xcb_xlib_threads_sequence_lost", file=file@entry=0xb68810ea "../../src/xcb_io.c", line=line@entry=273, function=function@entry=0xb68811d8 "poll_for_event") at assert.c:103
 poll_for_event (dpy=dpy@entry=0x96ca400) at ../../src/xcb_io.c:270
 poll_for_response (dpy=dpy@entry=0x96ca400) at ../../src/xcb_io.c:288
 _XEventsQueued (dpy=dpy@entry=0x96ca400, mode=mode@entry=2) at ../../src/xcb_io.c:362

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.gz
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.gz
Changed in apport (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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

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.