From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020809 Description of problem: On 2 different systems using default Gnome desktop, when changes are made to panel (ie. setting it to a right side vertical panel instead of a horizontal bottom panel) it segs on sub-sequent launches of X11. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Verify default Gnome desktop for "Joe User" 2.Right click properties on panel. 3.Set panel to go to the right side of the desktop. 4.Exit X 5.Login as Joe 6.Experience problem. 7.Document facts 8.Submit bug Actual Results: Gnome detected crash with panel and wanted to file a bug report. Expected Results: Panel should have ran and life with linux would be harmonious. Additional info: output from manual running gnome-panel after stopping gnome-session from spawning gnome-panel. -------------------------- $gnome-panel system-tray-applet-ERROR **: file obox.c: line 107 (get_class): should not be reached aborting... ---------------------------------
Set this to High because the gnome-desktop will be totally useless to first time linux users, and also because panel does crash.
Can you upgrade to gnome-panel 2.0.6-9 or newest available in rawhide, and be sure this bug still exists?
Sorry, I did not get a chance to upgrade to the latest rawhide. Though I have upgraded to RedHat release 8.0. The exact error is still there. I did complete the bug submit through "bug buddy", so look for duplicate.
Yes, sorry, this definitely exists in final. It's fixed in system-tray-applet in GNOME CVS.
*** This bug has been marked as a duplicate of 75138 ***
As a workaround, I: 1) Removed .gconfd/lock/ directory (which caused gnome-panel to generate it's own -funky- panel at the top of the screen). 2)Copied the /root/.gconf/apps/panel/profiles/default/panels/bottom_panel/%gconf.xml to overwrite the corresponding file in my non-super-user's path. After restarting X, gnome-panel no longer crashed, and in fact was replaced with the custom launchers I had defined intact. That's all I had time for... hope this input helps to track it down!
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.