xcompmgr crashed at startup

Bug #1063033 reported by Henrique Maia
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xcompmgr (Ubuntu)
New
Medium
Unassigned

Bug Description

xcompmgr crashed when logging in to user session.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: xcompmgr 1.1.6-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
Uname: Linux 3.5.0-17-generic i686
ApportVersion: 2.6.1-0ubuntu1
Architecture: i386
Date: Sat Oct 6 22:52:47 2012
ExecutablePath: /usr/bin/xcompmgr
InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Beta i386 (20121005)
ProcCmdline: xcompmgr -cfF -t-9 -l-11 -r9 -o.95 -D6
Signal: 6
SourcePackage: xcompmgr
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Henrique Maia (henriquemaia) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __assert_fail_base (fmt=0xb75b4c98 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0xb76ea179 "ret != inval_id", file=0xb76ea0ea "../../src/xcb_io.c", line=528, function=0xb76ea1fe "_XAllocID") at assert.c:94
 __GI___assert_fail (assertion=assertion@entry=0xb76ea179 "ret != inval_id", file=file@entry=0xb76ea0ea "../../src/xcb_io.c", line=line@entry=528, function=function@entry=0xb76ea1fe "_XAllocID") at assert.c:103
 _XAllocID (dpy=0x8bbf008) at ../../src/xcb_io.c:528
 XFixesCreateRegion (dpy=0x8bbf008, rectangles=0x0, nrectangles=0) at ../../src/Region.c:41
 configure_win (ce=0xbf86eebc, dpy=0x8bbf008) at ../xcompmgr.c:1550

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in xcompmgr (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
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.