GNOME Bugzilla – Bug 94969
gnome-panel crashes on startup if default desktop position is changed
Last modified: 2004-12-22 21:47:04 UTC
Package: gnome-panel Severity: normal Version: 2.0.6 Synopsis: gnome-panel crashes on startup if default desktop position is changed Bugzilla-Product: gnome-panel Bugzilla-Component: System Tray Applet BugBuddy-GnomeVersion: 2.0 (2.0.3) Description: Description of Problem: If you set gnome-panel property to place panel along RHS of desktop, the gnome-panel applet will crash upon startup. I'm assuming this is a problem for any setting that's not the default bottom of the desktop Steps to reproduce the problem: 1. Right click on the gnome-panel and select Properties 2. Select side position 3. logoff your gnome session and then run startx again or log backin Actual Results: Dialog box flashes: gnome-panel (process NNNNN) has crashed due to a fatal error. Issuing terminal (if you launch from a gnome terminal) reads: system-tray-applet-ERROR **: file obox.c: line 107 (get_class): should not be reached aborting... Expected Results: Normal gnome-panel functionality, but moved to a different screen placement How often does this happen? Consistently. If I clobber the ~/.gconf/apps/panel/profiles/default directory with a new "clean" default version, I can set the panel to the default bottom position and everything's fine. If I set the position in the properties dialog box, everything's fine until I login the next time. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found)...(no debugging symbols found)...[New Thread 8192 (LWP 19159)] 0x420ae169 in wait4 () from /lib/i686/libc.so.6
+ Trace 28320
Thread 1 (Thread 8192 (LWP 19159))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-10-05 20:17 ------- The original reporter (jgorman@SETassociates.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, hp@redhat.com.
*** This bug has been marked as a duplicate of 94625 ***