gnome-panel crashed with signal 5 in _XError()

Bug #328671 reported by TJ
42
This bug affects 7 people
Affects Status Importance Assigned to Milestone
GNOME Panel
New
Critical
gnome-panel (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gnome-panel

Spontaneous crash without any apparent user prompting.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/gnome-panel
NonfreeKernelModules: nvidia
Package: gnome-panel 1:2.25.90-0ubuntu1
ProcCmdline: gnome-panel
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: gnome-panel
StacktraceTop:
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 _XError () from /usr/lib/libX11.so.6
 ?? () from /usr/lib/libX11.so.6
 _XReply () from /usr/lib/libX11.so.6
 XInternAtom () from /usr/lib/libX11.so.6
Title: gnome-panel crashed with signal 5 in _XError()
Uname: Linux 2.6.28-7-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare users video

Tags: apport-crash
Revision history for this message
TJ (tj) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:gdk_x_error (display=<value optimized out>,
_XError (dpy=0x1272ea0, rep=0x1e291e0)
process_responses (dpy=0x1272ea0,
_XReply (dpy=0x1272ea0, rep=0x7fff4810c680,
XInternAtom (dpy=0x1272ea0,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in gnome-panel:
importance: Undecided → Medium
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

Thank you for your bug report. Since your stacktrace looked complete, I reported your bug to the developers of the software. You can track it and make comments at: http://bugzilla.gnome.org/show_bug.cgi?id=574739

Has this ever happend again? If yes, can you try to figure out what steps it need to trigger the crash? Thanks in advance.

Changed in gnome-panel:
status: Unknown → New
Changed in gnome-panel:
status: New → Triaged
status: Triaged → Incomplete
Revision history for this message
TJ (tj) wrote :

It seems to have 'gone-away' - probably a result of one of the countless updates over the intervening period. I'll keep an eye on it and update status here once we get into April so the report can be voided if the issue no longer occurs.

Revision history for this message
TJ (tj) wrote :

Spoke too soon! Just had it happen again. The apport report is bug #343473 which I've marked as a duplicate.

Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

Thanks. Setting this to "triaged" and waiting for upstream do process the trace.

Changed in gnome-panel:
status: Incomplete → Triaged
Changed in gnome-panel:
importance: Unknown → Critical
Changed in gnome-panel (Ubuntu):
status: Triaged → Invalid
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.