Bug 150373 - gnome-panel is crashing on an attempt to bring drop-down menus
Summary: gnome-panel is crashing on an attempt to bring drop-down menus
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-panel
Version: rawhide
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Mark McLoughlin
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-03-05 02:36 UTC by Michal Jaegermann
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-03-07 09:03:47 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
a backtrace from a crashing gnome-panel (11.26 KB, text/plain)
2005-03-05 02:37 UTC, Michal Jaegermann 		no flags Details
View All

Description Michal Jaegermann 2005-03-05 02:36:21 UTC 
Description of problem:

After updates from today an attempt to logout, or to touch any
of three headers from a "Custom Menu", is immediately and consistenly
crashing gnome-panel.  A backtrace is attached.

I do not know at this moment if i386 installation is affected or not.

Version-Release number of selected component (if applicable):
gnome-panel-2.9.91-3

How reproducible:
100%
Comment 1 Michal Jaegermann 2005-03-05 02:37:48 UTC 
Created attachment 111685 [details]
a backtrace from a crashing gnome-panel
Comment 2 Dan Witte 2005-03-05 07:52:06 UTC 
Ditto. x86_64, same gnome-panel build.
Comment 3 Michal Jaegermann 2005-03-06 06:35:14 UTC 
It seems that updates from today fixed the issue so this was
not gnome-panel per se although it was this program which was
crashing.  Even if it works the above means that gnome-panel
has bugs but a direct culprit was something else. gnome-menus
library?  No idea really.  Dan, how this works for you?
Comment 4 Dan Witte 2005-03-06 08:26:04 UTC 
wfm with today's updates, thanks Michal.
Comment 5 Mark McLoughlin 2005-03-07 09:03:47 UTC 
Thanks, Jeremy Katz and Matthias Clasen tracked it down
Note You need to log in before you can comment on or make changes to this bug.