Ubuntu
gnome-system-monitor package

gnome-system-monitor assert failure: gnome-system-monitor: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed.

Bug #548930 reported by Terry Saunders on 2010-03-26

This bug report is a duplicate of: Bug #507062: synaptic assert failure: synaptic: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed.. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gnome-system-monitor (Ubuntu)	Incomplete	Medium	Unassigned

Bug Description

Binary package hint: gnome-system-monitor

Just running system monitor and it crashed.

ProblemType: Crash
Architecture: i386
AssertionMessage: gnome-system-monitor: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed.
Date: Fri Mar 26 10:31:55 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/gnome-system-monitor
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
NonfreeKernelModules: nvidia
Package: gnome-system-monitor 2.28.0-1ubuntu2
ProcCmdline: gnome-system-monitor
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic-pae 2.6.32.10+drm33.1
Signal: 6
SourcePackage: gnome-system-monitor
StacktraceTop:
__kernel_vsyscall ()
raise () from /lib/tls/i686/cmov/libc.so.6
abort () from /lib/tls/i686/cmov/libc.so.6
__assert_fail () from /lib/tls/i686/cmov/libc.so.6
_XAllocID () from /usr/lib/libX11.so.6
Title: gnome-system-monitor assert failure: gnome-system-monitor: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed.
Uname: Linux 2.6.32-17-generic-pae i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (polkit-gnome-authentication-agent-1:4419): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Tags:

Revision history for this message

Terry Saunders (tsaunders) wrote on 2010-03-26:

Dependencies.txt Edit (4.5 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (536 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (31.1 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (788 bytes, text/plain; charset="utf-8")
Registers.txt Edit (480 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (10.7 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (11.3 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2010-03-26:

StacktraceTop:
__kernel_vsyscall ()
*__GI_raise (sig=6)
*__GI_abort () at abort.c:92
*__GI___assert_fail (
_XAllocID (dpy=0x80af4d0) at ../../src/xcb_io.c:385

Revision history for this message

Apport retracing service (apport) wrote on 2010-03-26: Stacktrace.txt

Stacktrace.txt Edit (58.0 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2010-03-26: ThreadStacktrace.txt

ThreadStacktrace.txt Edit (58.6 KiB, text/plain)

Changed in gnome-system-monitor (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-i386-retrace

Pedro Villavicencio (pedro) on 2010-03-29

visibility:

private → public

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2010-03-29:

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.
This will help us to find and resolve the problem.

Changed in gnome-system-monitor (Ubuntu):
status:	New → Incomplete

Revision history for this message

Terry Saunders (tsaunders) wrote on 2010-03-30:

I am not sure how to replicate the issue.

I was just running system monitor and it crashed.

Sorry that is all I can give you, it just happened.

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2010-03-30:

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.