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

Bug #514914 reported by Majestyx
120
This bug affects 27 people
Affects Status Importance Assigned to Milestone
gnome-panel (Ubuntu)
Incomplete
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-panel

i only restart my laptop

michael@tuxtop:~$ apt-cache policy gnome-panel
gnome-panel:
  Installiert: 1:2.29.6-0ubuntu1
  Kandidat: 1:2.29.6-0ubuntu1
  Versions-Tabelle:
 *** 1:2.29.6-0ubuntu1 0
        500 http://archive.ubuntu.com lucid/main Packages
        100 /var/lib/dpkg/status
michael@tuxtop:~$

ProblemType: Crash
Architecture: i386
AssertionMessage: gnome-panel: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed.
CrashCounter: 1
Date: Sat Jan 30 22:01:55 2010
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-panel
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: gnome-panel 1:2.29.6-0ubuntu1
ProcCmdline: gnome-panel
ProcEnviron:
 LANG=de_DE.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-12.16-generic
Signal: 6
SourcePackage: gnome-panel
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-panel assert failure: gnome-panel: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret != inval_id' failed.
Uname: Linux 2.6.32-12-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (gnome-settings-daemon:1697): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1697): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:1738): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

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

StacktraceTop:
 __kernel_vsyscall ()
 *__GI_raise (sig=6)
 *__GI_abort () at abort.c:92
 *__GI___assert_fail (assertion=0x7477e5 "ret != inval_id",
 _XAllocID (dpy=0x98368d0) at ../../src/xcb_io.c:385

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-panel (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
Pedro Villavicencio (pedro) wrote :

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-panel (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
status: New → Incomplete
Revision history for this message
Majestyx (majestyx) wrote :

>1. Is this reproducible?

sorry, no. this bug came only one time

>2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.

after updates at 2010-01-30 i switch off my laptop. later at day i start the laptop and apport icon was shown and i report the bug

Revision history for this message
mukesh agrawal (launchpad-net-mukesh) wrote :

Happened after a reboot. Might also be related to a screen resolution change.
(Before reboot, laptop was running in dual-head, spanning mode. I disconnected
the external display, power down, and then powered the system back up an hour
later.)

Revision history for this message
Nathan J (nathanator) wrote :

Did it for me after a simple reboot. No monitors or other display alterations.

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.