indicator-printers-service crashed in _cairo_xlib_surface_create_similar() -> XCreatePixmap() with an assertion failure ``_XAllocID: assertion "ret != inval_id''

Bug #1040919 reported by marcobra (Marco Braida)
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
indicator-printers (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Description: Ubuntu quantal (development branch)
Release: 12.10

indicator-printers:
  Installato: 0.1.6-0ubuntu1
  Candidato: 0.1.6-0ubuntu1
  Tabella versione:
 *** 0.1.6-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ quantal/main i386 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: indicator-printers 0.1.6-0ubuntu1 [modified: usr/lib/indicator-printers/indicator-printers-service]
ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2
Uname: Linux 3.5.0-11-generic i686
ApportVersion: 2.5.1-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Fri Aug 24 00:35:13 2012
ExecutablePath: /usr/lib/indicator-printers/indicator-printers-service
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate i386 (20100419.1)
ProcCmdline: /usr/lib/indicator-printers/indicator-printers-service
Signal: 6
SourcePackage: indicator-printers
StacktraceTop:
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 __assert_fail () from /lib/i386-linux-gnu/libc.so.6
 _XAllocID () from /usr/lib/i386-linux-gnu/libX11.so.6
Title: indicator-printers-service crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to quantal on 2012-08-15 (8 days ago)
UserGroups: adm admin audio cdrom debian-tor dialout dip fax floppy fuse icecast lpadmin netdev plugdev powerdev sambashare tape vboxusers video

Revision history for this message
marcobra (Marco Braida) (marcobra) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __assert_fail_base (fmt=0xb752c698 <Address 0xb752c698 out of bounds>, assertion=0x4b2c1179 "ret != inval_id", file=0x4b2c10ea "../../src/xcb_io.c", line=528, function=0x4b2c11fe "_XAllocID") at assert.c:94
 __GI___assert_fail (assertion=assertion@entry=0x4b2c1179 "ret != inval_id", file=file@entry=0x4b2c10ea "../../src/xcb_io.c", line=line@entry=528, function=function@entry=0x4b2c11fe "_XAllocID") at assert.c:103
 _XAllocID (dpy=0xa020de8) at ../../src/xcb_io.c:528
 XCreatePixmap (dpy=0xa020de8, d=52428805, width=width@entry=80, height=height@entry=80, depth=32) at ../../src/CrPixmap.c:56
 _cairo_xlib_surface_create_similar (abstract_src=0xa16f6d8, content=CAIRO_CONTENT_COLOR_ALPHA, width=80, height=80) at /build/buildd/cairo-1.12.2/src/cairo-xlib-surface.c:306

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 indicator-printers (Ubuntu):
importance: Undecided → Medium
summary: - indicator-printers-service crashed with SIGABRT in raise()
+ indicator-printers-service crashed with SIGABRT in __assert_fail_base()
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: indicator-printers-service crashed with SIGABRT in __assert_fail_base()

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in indicator-printers (Ubuntu):
status: New → Confirmed
Charles Kerr (charlesk)
information type: Private → Public
Charles Kerr (charlesk)
summary: - indicator-printers-service crashed with SIGABRT in __assert_fail_base()
+ indicator-printers-service crashed in
+ _cairo_xlib_surface_create_similar() -> XCreatePixmap() with an
+ assertion failure ``ret != inval_id''
summary: indicator-printers-service crashed in
_cairo_xlib_surface_create_similar() -> XCreatePixmap() with an
- assertion failure ``ret != inval_id''
+ assertion failure ``_XAllocID: assertion "ret != inval_id''
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.