gnome-panel locks up or can't start

[Caspian]

When X crashes and I do Ctrl-Alt-Backspace, gnome-panel sometimes comes up with a error "gnome-panel is already running. Will now exit". So, I'm left without any panels.

I kill X, run "kill `pgrep gnome-panel`", then run "sudo /etc/init.d/gdm restart" and log into Gnome again. gnome-panel starts up, but it hangs -- making it a useless tan strip at the bottom of my screen.

I repeat this process until sometimes it finally works -- but sometimes I need to restart my computer to get out of this cycle.

[Sebastien Bacher (seb128)]

Thanks for your bug. You describe 2 different issues on that page, don't do that that's not managable The first one is a duplicate of bug #33962. Could you get a backtrace for the second one using gdb?

[Sebastien Bacher (seb128)]

backtrace from bug #35378

"(gdb) run
Starting program: /usr/bin/gnome-panel
[Thread debugging using libthread_db enabled]
[New Thread -1223850304 (LWP 26649)]

(gnome-panel:26649): GnomeUI-WARNING **: While connecting to session manager:
Could not open network socket.

** (gnome-panel:26649): WARNING **: No toplevel on which to load object 'show_desktop_button'

** (gnome-panel:26649): WARNING **: /build/buildd/gnome-panel-2.14.0/./gnome-panel/panel-applet-frame.c:1261: failed to load applet OAFIID:GNOME_WindowListApplet:
Failed to resolve, or extend '!prefs_key=/apps/panel/applets/applet_2/prefs;background=none:;orient=up;size=x-small;locked_down=false

Program received signal SIGINT, Interrupt.
[Switching to Thread -1223850304 (LWP 26649)]
0xffffe410 in __kernel_vsyscall ()
(gdb) bt
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb75e78cd in poll () from /lib/tls/i686/cmov/libc.so.6
#2 0xb77636e8 in g_main_context_iterate (context=0x80fc498, block=1, dispatch=1, self=0x80c7920) at gmain.c:2849
#3 0xb7763d1e in IA__g_main_context_iteration (context=0x80fc498, may_block=1) at gmain.c:2606
#4 0xb7c6756a in link_main_iteration () from /usr/lib/libORBit-2.so.0
#5 0xb7c4c515 in giop_recv_buffer_get () from /usr/lib/libORBit-2.so.0
#6 0xb7c4fcc5 in ORBit_small_invoke_stub () from /usr/lib/libORBit-2.so.0
#7 0xb7c4fe96 in ORBit_small_invoke_stub_n () from /usr/lib/libORBit-2.so.0
#8 0xb7c616be in ORBit_c_stub_invoke () from /usr/lib/libORBit-2.so.0
#9 0xb7c8a2e6 in Bonobo_ActivationContext_activateMatchingFull () from /usr/lib/libbonobo-activation.so.4
#10 0xb7c8b833 in bonobo_activation_activate () from /usr/lib/libbonobo-activation.so.4
#11 0xb7c8ba53 in bonobo_activation_activate_from_id () from /usr/lib/libbonobo-activation.so.4
#12 0xb6e5bcd2 in bonobo_moniker_oaf_resolve () from /usr/lib/bonobo/monikers/libmoniker_std_2.so
#13 0xb7ce5b4c in bonobo_moniker_use_extender () from /usr/lib/libbonobo-2.so.0
#14 0xb77ca79f in IA__g_closure_invoke (closure=0x81fc4a8, return_value=0xfffffffc, n_param_values=4294967292, param_values=0xfffffffc, invocation_hint=0xfffffffc)
    at gclosure.c:490
#15 0xb7cf63da in bonobo_closure_invoke_va_list () from /usr/lib/libbonobo-2.so.0
#16 0xb7cf66d7 in bonobo_closure_invoke () from /usr/lib/libbonobo-2.so.0
#17 0xb7ce5f22 in bonobo_resolve_flag_get_type () from /usr/lib/libbonobo-2.so.0
#18 0xb7ce556e in bonobo_moniker_get_case_sensitive () from /usr/lib/libbonobo-2.so.0
#19 0xb7cf6a78 in _ORBIT_skel_small_Bonobo_Moniker_resolve () from /usr/lib/libbonobo-2.so.0
#20 0xb7c61665 in ORBit_c_stub_invoke () from /usr/lib/libORBit-2.so.0
#21 0xb7cf8ccf in Bonobo_Moniker_resolve () from /usr/lib/libbonobo-2.so.0
#22 0xb6e5b92b in bonobo_moniker_item_resolve () from /usr/lib/bonobo/monikers/libmoniker_std_2.so
#23 0xb7ce5b4c in bonobo_moniker_use_extender () from /usr/lib/libbonobo-2.so.0
#24 0xb77ca79f in IA__g_closure_invoke (closure=0x81fb370, return_value=0xfffffffc, n_param_values=4294967292, param_values=0xfffffffc, invocation_hint=0xfffffffc)
    at gclosure.c:490
#25 0xb7cf63da in bonobo_closure_invoke_va_list () from /usr/lib/libbonobo-2.so.0
#26 0xb7cf66d7 in bonobo_cl...

[Daniel Holbach (dholbach)]

Do you still have the problem in Edgy or Dapper?

[Sebastien Bacher (seb128)]

No reply, closing the bug now. Feel free to reopen with the asked details if you still get that bug

[Caspian (masterhacker)]

This problem has been resolved in the Dapper stable release

Sorry for the delayed reply.

[Sebastien Bacher (seb128)]

no problem, marking as fixed then, thank you for the update