Bug 165977 - Panel crashes when any right-stuck applet resizes itself
Summary: Panel crashes when any right-stuck applet resizes itself
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-menus   
(Show other bugs)
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2005-08-15 14:04 UTC by Bill Crawford
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version: gnome-menus-2.11.91-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-08-17 15:44:38 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
core file from crashed gnome-panel. (1.65 MB, application/octet-stream)
2005-08-16 00:03 UTC, Bill Crawford
no flags Details
some debug output from gdb + panel (2.89 KB, text/plain)
2005-08-16 12:48 UTC, Bill Crawford
no flags Details

External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Bugzilla 313232 None None None 2019-04-19 00:17 UTC

Description Bill Crawford 2005-08-15 14:04:58 UTC
Description of problem:
When certain applets, placed at the right of the panel (like the clock, or the
systray^Wnotification area) resize themselves (e.g. I open an app with a tray
icon) gnome-panel often crashes (I get a popup saying it has unexpectedly
stopped working, anyway).
Other particular culprits include GAIM, aMule etc etc.
Not sure if it's related, but leaving xmms running for a while seemed to trigger
it too, when I had the window-list menu on the panel too.
I've completely blown away ~/.gconf (gconftool-2 --recursive-unset /apps, ditto
/system, etc; then rm -rf .gconf after logging out of X). Still happens.

Version-Release number of selected component (if applicable):

Comment 1 Bill Crawford 2005-08-15 14:06:13 UTC
Just crashed again as I hit the submit button in firefox to open the bug.
It looks like sometimes just a change in a window title can trigger a crash too.

Comment 2 Bill Crawford 2005-08-15 14:15:56 UTC
Never mind, seems to have been caused by two copies of libwnck on the system.

Comment 3 Bill Crawford 2005-08-15 14:48:38 UTC
Yuck. No, it just didn't happen for a while. Just after gaim changed the tray
icon (becuase I was marked away) the panel crashed again. And it's just done it
again now (five minutes later) while I'm trying to type this.
OK, what can I do to help track down the cause of this? Beyond "when I have
anything changing state in the systray" I mean ...

Comment 4 Mark McLoughlin 2005-08-15 15:29:12 UTC
Thanks for the bug report. Without a stack trace from the crash it is 
very hard to determine what caused the crash. Please see
http://fedoraproject.org/wiki/StackTraces for more information about
getting a useful stack trace.

Comment 5 Bill Crawford 2005-08-15 16:23:09 UTC
I'll have a go, yes - just installing the -debuginfo packages now.
I did click the "inform developers" button but the traces didn't look too useful :-S

Comment 6 Bill Crawford 2005-08-15 19:31:41 UTC
Well, .. I installed all the debugingo packages, and I've attached gdb ... and
it hasn't done it since :)
It *did* crash while I was installing the debug packagess and running prelink,
so I'm gonna write this off as bad luck for now :)

Comment 7 Bill Crawford 2005-08-15 23:54:25 UTC
*sigh* done it again, I have a core dump this time. I'll try to attach it if
'zilla will accept the file.

Comment 8 Bill Crawford 2005-08-16 00:03:19 UTC
Created attachment 117779 [details]
core file from crashed gnome-panel.

I don't know if this will help *that* much ... but I can't make enough sense of
the data to make any deductions beyond "it looks like the menu change monitor"
gnome-panel-2.11.91-2, from rawhide; I've prelinked everything, if that matters
I can pass on a copy of the binary or undo prelinking and try again.

Comment 9 Mark McLoughlin 2005-08-16 06:23:19 UTC
Please don't attach core files, attach a stack trace. See:


Also, that core file was from gaim, not the panel.

Comment 10 Ryan James 2005-08-16 12:42:04 UTC
i *think* i've been seeing the same thing, but it's only on newer (ie anything
after 1469) kernels.  i looked at, but didn't save, the stack trace from
bugbuddy: #0 was in something that ended in 'vsyscall()' is all i remember. 
i'll get a full trace after yum is done.

Comment 11 Bill Crawford 2005-08-16 12:47:07 UTC
ok .. how do I remove an attachment? and some output from gdb follows

Comment 12 Bill Crawford 2005-08-16 12:48:52 UTC
Created attachment 117788 [details]
some debug output from gdb + panel

Comment 13 Bill Crawford 2005-08-16 13:02:04 UTC
Sorry, it seemed to me the trace alone didn't say much of any use -- the state
of the variables at the time would perhaps explain the segfault, hence the core
file :-S  GAIM dies every time the panel does (presumably related to the tray
icon, 'cause it survives the crash if I disable the icon).  I just assumed the
core file was from the panel 'cause I quit gdb with "signal 6" ... maybe I need
to disable bug-buddy or whatever.

Anyway, if there's any additional info I can prise out of the program state
if/when it crashes again, please tell me, I'm running it with gdb attached.

If it's helpful: last time it crashed, was when I updated a couple of packages;
the next time I clicked on a launcher (the GAIM one, as it happened) *boom*

Comment 14 Mark McLoughlin 2005-08-16 13:46:07 UTC
Looks like a gnome-menus bug which was fixed upstream recently:

* Tue Aug 16 2005 Mark McLoughlin <markmc@redhat.com> 2.11.91-1
- Update to 2.11.91
- Backport patch from HEAD to hopefully fix crasher (rh #165977)

Please re-open if you still see the problem with gnome-menus-2.11.91-1

Comment 15 Mark McLoughlin 2005-08-16 21:04:42 UTC
Upstream bug report:


Comment 16 Bill Crawford 2005-08-17 15:25:01 UTC
Reopening due to regression.

Whenever a menu is changed e.g. by installing / upgrading a package, two copies
of all KDE menu items now appear.

Comment 17 Mark McLoughlin 2005-08-17 15:44:38 UTC
Please don't re-open bugs with details of some other bug report. Open a new bug

Thanks for testing, though. I assume this means the crash has been fixed?

The new bug you're referring to is filed upstream at:


Comment 18 Bill Crawford 2005-08-17 16:10:30 UTC
Um, ok, ... the crash is gone, but the menus are still messed up; I thought it
best to report that in case it's related ...

I take it there's no need to open a new bug on brc if it's in gnome 'zilla and
will be fixed in the next upstream bump?

Comment 19 Mark McLoughlin 2005-08-18 08:22:22 UTC
Bill: please test gnome-menus-2.11.91-2 now - the "duplicate entries on
updating" issue should be fixed. If you still see that issue or any other new
issues, please do open another bug. Thanks.

Comment 20 Mark McLoughlin 2005-08-18 13:01:09 UTC
gnome-menus-2.11.91-2 had an infinite loop, fixed in gnome-menus-2.11.91-3

Note You need to log in before you can comment on or make changes to this bug.