GNOME Bugzilla – Bug 105228
panel crashes on gnome startup
Last modified: 2004-12-22 21:47:04 UTC
Package: gnome-core Severity: normal Version: 2.0.6 Synopsis: panel crashes on gnome startup Bugzilla-Product: gnome-core Bugzilla-Component: panel BugBuddy-GnomeVersion: 2.0 (2.0.3) Description: Description of Problem: panel crashes on gnome startup after crash, error dialog shows up, hitting close, panel crashes again, wash, rinse, repeat Steps to reproduce the problem: 1. startx (no .xinit file in $HOME) 2. 3. Actual Results: panel keeps crashing - console seems to indicate that the problem is with the system tray applet: .... file : obox.c : line 107 ... should not be reached Expected Results: How often does this happen? repeatedly - never happened before this report though just rebooted my system after upgrading to kernel 2.4.18-24.8.0 Additional Information: just rebooted my system after upgrading to kernel 2.4.18-24.8.0 Debugging Information: Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found)...(no debugging symbols found)...[New Thread 8192 (LWP 1340)] 0x420ae169 in wait4 () from /lib/i686/libc.so.6
+ Trace 33479
Thread 1 (Thread 8192 (LWP 1340))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-02-04 14:11 ------- The original reporter (scottu@apptechsys.com) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, panel-maint@bugzilla.gnome.org.
Submitter here. To get the panel to start up, I had to find the applet object in the ~/.gconf/ hierarchy that had the SystemTray applet, then search for the name of that object in all the .gconf files. I found it in .gconf/panel/profiles/default/general/%gconf.xml, and excised the xml tag containing the string ( <li>...</li>). Two comments unrelated to this bug: 1. do the identifier strings for applets/objects/etc really need to be so long? With that naming scheme, you could probably assign a unique id to every atom in the milky way galaxy 2. the lack of line breaks in the gconf xml files makes hand editing them difficult in the editor I use (vim) - long lines makes for slow operations and screen updates. I know these files are generated and auto-read, but how about keeping with the unix tradition and make these config files editable, when necessary? That is one goal with xml, or so I've been informed As to the reason why my system tray applet doesnt work, I don't know, but it's been flakey for me for a long time. Might be related to the flakiness of the red hat network up2date applet (which didn't start properly either).
You've listed multiple problems. Most of these should be in separate bug reports. The panel crash you are experiencing is the now infamous vertical panel crasher bug found in bug 94625--Havoc has at least one comment in that bug report saying where to get fixed packages from. As far as the gconf-editor enhancement requests, that should be filed in a separate bug. As for the system tray applet and the up2date applet being flaky, that sounds like bug 94422 to me, but if you can provide more information, you can feel free to file a separate bug report about this. *** This bug has been marked as a duplicate of 94625 ***