gnome-system-monitor crashed with SIGABRT in __GI___assert_fail()

Bug #926668 reported by omarly666
32
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-system-monitor (Ubuntu)
Expired
Medium
Unassigned

Bug Description

loggged out after setting up new dual top screen. seems ok. had trouble w multiple launchers before relog, probably because of different screensizes

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-system-monitor 3.3.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-12.21-generic 3.2.2
Uname: Linux 3.2.0-12-generic i686
ApportVersion: 1.91-0ubuntu1
Architecture: i386
CheckboxSubmission: 8617bffd198177508bf030f94c880aca
CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
Date: Sat Feb 4 14:56:38 2012
ExecutablePath: /usr/bin/gnome-system-monitor
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: gnome-system-monitor
Signal: 6
SourcePackage: gnome-system-monitor
StacktraceTop:
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () 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
 XRenderCreatePicture () from /usr/lib/i386-linux-gnu/libXrender.so.1
Title: gnome-system-monitor crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to precise on 2012-01-28 (7 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
omarly666 (omarly666) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __GI___assert_fail (assertion=0x56add39 "ret != inval_id", file=0x56adcaa "../../src/xcb_io.c", line=528, function=0x56addbe "_XAllocID") at assert.c:81
 _XAllocID (dpy=0x8b4a0a0) at ../../src/xcb_io.c:528
 XRenderCreatePicture (dpy=0x8b4a0a0, drawable=28329216, format=0x8b88d40, valuemask=0, attributes=0x0) at ../../src/Picture.c:90
 _cairo_xlib_surface_ensure_dst_picture (display=0xb0d02c08, surface=0x8f228c0) at /build/buildd/cairo-1.10.2/src/cairo-xlib-surface.c:1130
 _cairo_xlib_surface_fill_rectangles (abstract_surface=0x8f228c0, op=CAIRO_OPERATOR_CLEAR, color=0x56d520, rects=0xbfe3a720, num_rects=1) at /build/buildd/cairo-1.10.2/src/cairo-xlib-surface.c:2752

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-system-monitor (Ubuntu):
importance: Undecided → Medium
summary: - gnome-system-monitor crashed with SIGABRT in raise()
+ gnome-system-monitor crashed with SIGABRT in __GI___assert_fail()
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-system-monitor (Ubuntu):
status: New → Confirmed
Revision history for this message
Robert Roth (evfool) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

visibility: private → public
Revision history for this message
Robert Roth (evfool) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Changed in gnome-system-monitor (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-system-monitor (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-system-monitor (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.