xfce4-menu-plugin crashed with signal 5 in _XError()

Bug #334925 reported by Mario Limonciello on 2009-02-26
14
Affects Status Importance Assigned to Milestone
xfdesktop4 (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: xfdesktop4

Right upon login, it crashed. No panel available now.

This is w/ Mythbuntu a5 i386 candidate from 02-26-2009

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/xfce4/panel-plugins/xfce4-menu-plugin
Package: xfdesktop4 4.5.99.1-0ubuntu3
ProcCmdline: /usr/lib/xfce4/panel-plugins/xfce4-menu-plugin socket_id 20971569 name xfce4-menu id 1 display_name Xfce\ Menu size 24 screen_position 1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: xfdesktop4
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
 XSync () from /usr/lib/libX11.so.6
Title: xfce4-menu-plugin crashed with signal 5 in _XError()
Uname: Linux 2.6.28-8-generic i686
UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare

Mario Limonciello (superm1) wrote :

StacktraceTop:gdk_x_error (display=0x8f56e00, error=0xbfd6cdc8)
_XError (dpy=0x8f56e00, rep=0x8f968f0)
process_responses (dpy=0x8f56e00, wait_for_first_event=0,
_XReply (dpy=0x8f56e00, rep=0xbfd6cef0, extra=0, discard=1)
XSync (dpy=0x8f56e00, discard=0) at ../../src/Sync.c:48

Changed in xfdesktop4:
importance: Undecided → Medium
tags: added: iso-testing
Charlie Kravetz (charlie-tca) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. Since you reported this against a development version of Xubuntu Jaunty with a beta version of xfdesktop4, we are closing this report. If this can be reproduced using the final version of Xubuntu 9.10, please comment and change the status to 'new' in the yellow line.

Changed in xfdesktop4 (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers