GNOME Bugzilla – Bug 344330
Panel Crash
Last modified: 2007-04-10 14:55:56 UTC
Steps to reproduce: 1. Install NVIDIA rpms for x86_64 2. Install libquicktime update 3. Have Yum remove libquicktime. Then remove NVIDIA rpms Stack trace: Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496370240 (LWP 2640)] 0x000000306930cc95 in waitpid () from /lib64/libpthread.so.0
+ Trace 68733
Thread 1 (Thread 46912496370240 (LWP 2640))
Other information: Error Panel does not close or cancel....keeps coming back. Restart also does the same thing. Panel only shows weather, and time applet....no menu or other desktops makes it very hard to use. Started to have YUM remove and re-install but it wanted to remove a total of 24 packages which seemed excessive.
Looks like the stack trace Davyd got in bug 327972 comment 13. Could you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Backtrace was generated from '/usr/bin/gnome-panel' Using host libthread_db library "/lib64/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 46912496370240 (LWP 2267)] 0x000000306930cc95 in waitpid () from /lib64/libpthread.so.0
+ Trace 68744
Thread 1 (Thread 46912496370240 (LWP 2267))
Thanks for following up. Unfortunately, that stack trace only has has marginally more debugging symbols, and unfortunately not at the most interesting frames. Which debuginfo packages did you install? I'd suggest making sure you have at least ORBit2-debuginfo, libbonobo-debuginfo, libbonoboui-debuginfo, glib2-debuginfo, gtk2-debuginfo, and gnome-panel-debuginfo.
I installed all the sugested debuginfo packages, and reran the BackTrace below: Backtrace was generated from '/usr/bin/gnome-panel' Using host libthread_db library "/lib64/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 46912496370240 (LWP 2299)] 0x000000306930cc95 in waitpid () from /lib64/libpthread.so.0
+ Trace 68747
Thread 1 (Thread 46912496370240 (LWP 2299))
Hi Again....I tried a forced install of gnome-panel-2.14.2-1.fc5.1.x86_64.rpm to see if it would clear up any problems.....but N-O-O-O-O-O !!! I'm still stuck with the same thing....BugBuddy comes up, and will not go away or cancel, and panel shows almost no applets....temp & switcher only.
I filed the same bug over at redhat.com yesterday: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=194809 But mine had nothing to do with nvidia or quicktime. Here's the tail end of my yum.log, probably one of these updates was the culprit: Jun 09 09:26:20 Updated: glib2.i386 2.10.3-1 Jun 09 09:26:33 Updated: gtk2.i386 2.8.18-1 Jun 09 09:26:36 Updated: hal.i386 0.5.7-3.fc5.2 Jun 09 09:27:05 Updated: gnome-vfs2.i386 2.14.2-1 Jun 09 09:27:13 Updated: gnome-desktop.i386 2.14.2-1 Jun 09 09:27:21 Updated: evolution-data-server.i386 1.6.2-1.fc5.1 Jun 09 09:28:40 Updated: gnome-panel.i386 2.14.2-1.fc5.1 Jun 09 09:29:35 Updated: evolution.i386 2.6.2-1.fc5.5 Jun 09 09:30:24 Updated: gnome-utils.i386 1:2.14.0-4.fc5.2 Jun 09 09:31:14 Updated: gnome-media.i386 2.14.2-1 Jun 09 09:31:26 Updated: gnome-themes.noarch 2.14.2-1 Jun 09 09:31:29 Updated: glib2-devel.i386 2.10.3-1 Jun 09 09:31:54 Updated: gnome-applets.i386 1:2.14.2-1.fc5.1 Jun 09 09:32:08 Updated: totem.i386 1.4.1-1 Jun 09 09:32:22 Updated: gthumb.i386 2.7.7-1 Jun 09 09:32:33 Updated: dia.i386 1:0.95-4.fc5 Jun 09 09:32:40 Updated: planner.i386 0.13-4.4 Jun 09 09:32:41 Updated: procps.i386 3.2.6-3.4 Jun 09 09:32:51 Updated: eog.i386 2.14.2-1.fc5.1 Jun 09 09:32:55 Updated: evolution-connector.i386 2.6.2-1.fc5.4 Jun 09 09:32:55 Updated: gnome-vfs2-smb.i386 2.14.2-1 Jun 09 09:32:56 Updated: evolution-sharp.i386 0.10.2-9.3 Jun 09 09:33:04 Updated: evolution-webcal.i386 2.4.1-3.4 Jun 09 09:33:20 Updated: gnome-terminal.i386 2.14.2-1 Jun 09 09:33:28 Updated: gtk2-devel.i386 2.8.18-1 Jun 09 09:33:30 Updated: gnome-vfs2-devel.i386 2.14.2-1 Jun 09 09:33:32 Updated: policycoreutils.i386 1.30.10-1.fc5 Jun 09 09:35:22 Updated: gnome-games.i386 1:2.14.2-1 Jun 09 09:35:25 Updated: info.i386 4.8-9.2.fc5.1 Jun 09 09:35:26 Updated: module-init-tools.i386 3.2.2-0.FC5.3 Jun 09 09:35:36 Updated: gnome-session.i386 2.14.2-1 Jun 09 09:35:51 Updated: sound-juicer.i386 2.14.4-1.fc5.1 Jun 09 09:35:53 Updated: rsync.i386 2.6.8-1.FC5 Jun 09 09:35:54 Updated: gnome-sudoku.noarch 0.4.0-5.fc5 Jun 09 09:35:58 Updated: dovecot.i386 1.0-0.beta8.1.fc5 Jun 09 09:36:04 Updated: gnome-themes-extras.noarch 0.9.0-3.fc5 Jun 09 19:13:10 Updated: libgnome.i386 2.14.1-1.fc5.1 Jun 09 19:13:17 Updated: libgnomeui.i386 2.14.1-1.fc5.1 Jun 09 19:13:19 Updated: libgnome-devel.i386 2.14.1-1.fc5.1 Jun 09 19:14:07 Updated: control-center.i386 1:2.14.2-1 Jun 09 19:14:11 Updated: libgnomeui-devel.i386 2.14.1-1.fc5.1
This last weekend 10-11th, yum brought in a small 50k gnome-panel-dev file that seems to have cleared up the major problem. The only remaining problem is with the "TimeApplet" which does not load on "Boot"....but I can live with that small problem as long as most of the panel functions. Mel Gordon
RedHat's Bugzilla crashed and took my bug report with it. I just refiled it as: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=195263
[This comment duplicated from https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=195263.] EUREKA. When I noticed that (according to the call stack) Bonobo was calling ORBit with a null object, I inspected my panel configuration using gconf-editor. Sure enough, I found an applet -- /apps/panel/applet_3 in gconf -- with no properties, but with some settings in /apps/panel/applet_3/prefs that made it look like it was once something pilot-related. I removed the appls/panel/applets/applet_3 subtree from my $HOME/.gconf directory, then renamed applet_4 to applet_3 just in case. (A change that I then reflected in apps/panel/%gconf.xml.) After launching a new session (to get a new gconfd instance), all was well. I presume that one of my many software updates must have left that applet config in a bad state. It might be worth putting some code into gnome-panel to defend against this condition.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 327972 ***