indicator-applet-complete crashed with SIGABRT in __assert_fail_base()

Bug #971900 reported by miguelator
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cairo (Ubuntu)
Invalid
Undecided
Unassigned
libx11 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

indicator-applet-complete crashed with SIGABRT in raise()

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: indicator-applet-complete 0.4.92-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-20.33-generic-pae 3.2.12
Uname: Linux 3.2.0-20-generic-pae i686
ApportVersion: 2.0-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Mon Apr 2 23:01:01 2012
ExecutablePath: /usr/lib/indicator-applet/indicator-applet-complete
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120318)
ProcCmdline: /usr/lib/indicator-applet/indicator-applet-complete
ProcEnviron:
 SHELL=/bin/bash
 LANG=es_ES.UTF-8
Signal: 6
SourcePackage: indicator-applet
Title: indicator-applet-complete crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
miguelator (miguel+angel) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceTop.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in indicator-applet (Ubuntu):
importance: Undecided → Medium
summary: - indicator-applet-complete crashed with SIGABRT in raise()
+ indicator-applet-complete crashed with SIGABRT in __assert_fail_base()
tags: removed: need-i386-retrace
visibility: private → public
affects: indicator-applet (Ubuntu) → libx11 (Ubuntu)
Revision history for this message
Bryce Harrington (bryce) wrote :

Hmm, I doubt this is actually a bug in libx11.

The bug is an assertion, so something is definitely wrong. This is the assertion that's failing:

XID _XAllocID(Display *dpy)
{
        XID ret = dpy->xcb->next_xid;
        assert (ret != inval_id); /* FAIL */
        ...

So we know there's bad data in the Display structure.

_XAllocID is being called by XCreatePixmap(), which looks like this:

Pixmap XCreatePixmap (
    register Display *dpy,
    ...)
{
    ....
    LockDisplay(dpy);
    ....
    pid = req->pid = XAllocID(dpy);
    UnlockDisplay(dpy);

LockDisplay doesn't appear to tinker with anything in the dpy->xcb part of the structure, so we can ignore that.

XCreatePixmap is called from cairo, so we're outside libx11 at that point.

Doesn't answer the question of where the inval_id came from to begin with though...

Revision history for this message
Bryce Harrington (bryce) wrote :

This is probably caused by something higher up in the stack. Could be cairo, probably more likely gdk_x11 or gtk.
I think the libx11 bug task is probably invalid here, it's just asserting on bad data in the display struct.

Revision history for this message
Sebastien Bacher (seb128) wrote :

there has been no activity/reports in years, closing

Changed in libx11 (Ubuntu):
status: New → Invalid
Changed in cairo (Ubuntu):
status: New → Invalid
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.