GNOME Bugzilla – Bug 121719
gnome-panel crashes when Gnome is starting up.
Last modified: 2004-12-22 21:47:04 UTC
Description of Problem: After recently updating some dot files in my home directory, Gnome displays the dialog box: v Error (-) Application "gnome-panel" (process 1236) has crashed due to a fatal error. (Aborted) Please visit GNOME Application Crash page for more information. [ X Close ] [ Submit a bug report ] Steps to reproduce the problem: 1. Execute "startx" from a login shell in Red Hat Linux 8.0. 2. 3. Actual Results: (See above.) Expected Results: Running gnome-panel with the rest of Gnome. How often does this happen? Every time I start X. Additional Information:
What version of GNOME? Which dotfiles did you change? Can you use the "Submit a bug report" button to submit a backtrace, or see http://bugzilla.gnome.org/getting-stack-traces.cgi for other methods? Many thanks.
Andrew Sobala asked: > What version of GNOME? I am using gnome-panel 2.0.6, part of the Red Hat Linux 8.0 installation. > Which dotfiles did you change? Primarily my .bash_profile and .bashrc files. I may have also changed the .Xdefaults file. > Can you use the "Submit a bug report" button to submit a > backtrace, or see > > http://bugzilla.gnome.org/getting-stack-traces.cgi > > for other methods? The getting-stack-traces.cgi URL does not exist. I originally submitted this bug report using the [Submit a bug report] button but I will try again.
OK, it's http://bugzilla.gnome.org/getting-traces.cgi (I should cut and paste like normal ;). It might be useful to attach the files you changed if they don't contain sensitive information. Many thanks.
Reassigned, sorry for the spam.
This is the backtrace reported when the [Submit a bug report] button is pressed: Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found)...(no debugging symbols found)...[New Thread 8192 (LWP 1201)] 0x420ae169 in wait4 () from /lib/i686/libc.so.6 #0 0x420ae169 in wait4 () from /lib/i686/libc.so.6 #1 0x4212a2d0 in __DTOR_END__ () from /lib/i686/libc.so.6 #2 0x4084dc63 in waitpid () from /lib/i686/libpthread.so.0 #3 0x40197ff5 in libgnomeui_module_info_get () from /usr/lib/libgnomeui-2.so.0 #4 0x4084f47e in __pthread_sighandler () from /lib/i686/libpthread.so.0 #5 <signal handler called> #6 0x42028cc1 in kill () from /lib/i686/libc.so.6 #7 0x4084c07d in raise () from /lib/i686/libpthread.so.0 #8 0x4202a019 in abort () from /lib/i686/libc.so.6 #9 0x4089f476 in g_logv () from /usr/lib/libglib-2.0.so.0 #10 0x4089f4b4 in g_log () from /usr/lib/libglib-2.0.so.0 #11 0x40e6cb40 in get_class () from /usr/lib/system-tray-applet/libsystem-tray-applet.so #12 0x40e6cbb3 in gtk_obox_size_request () from /usr/lib/system-tray-applet/libsystem-tray-applet.so #13 0x40823870 in g_cclosure_marshal_VOID__BOXED () from /usr/lib/libgobject-2.0.so.0 #14 0x4080e467 in g_type_class_meta_marshal () from /usr/lib/libgobject-2.0.so.0 #15 0x4080e0c0 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #16 0x4082213f in signal_emit_unlocked_R () from /usr/lib/libgobject-2.0.so.0 #17 0x40821888 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #18 0x403df0cc in gtk_signal_emit_by_name () from /usr/lib/libgtk-x11-2.0.so.0 #19 0x403e0283 in do_size_request () from /usr/lib/libgtk-x11-2.0.so.0 #20 0x403e061f in _gtk_size_group_compute_requisition () from /usr/lib/libgtk-x11-2.0.so.0 #21 0x40480abf in gtk_widget_size_request () from /usr/lib/libgtk-x11-2.0.so.0 #22 0x4030b0c4 in gtk_alignment_size_request () from /usr/lib/libgtk-x11-2.0.so.0 #23 0x40823870 in g_cclosure_marshal_VOID__BOXED () from /usr/lib/libgobject-2.0.so.0 #24 0x4080e467 in g_type_class_meta_marshal () from /usr/lib/libgobject-2.0.so.0 #25 0x4080e0c0 in g_closure_invoke () from /usr/
Right. This is a duplicate of bug 94625, which is fixed. It's to do with vertical panels. There's 3 ways to get round this: 1. Upgrade to RH9 ;-) 2. Apparently there is a fix in up2date. 3. "Fire up gconf-editor and go to /apps/panel/profiles/default/panels and find the directory for the panel in question. You'll want to change 'screen_edge' to panel-edge-bottom or panel-edge-top" Thanks, and please report any other bugs you may find. *** This bug has been marked as a duplicate of 94625 ***
The suggested change to "screen-edge" allows me to work around this crash. Thank you for the rapid response!