GNOME Bugzilla – Bug 611816
When launching pidgin, gnome-panel starts using 100% of CPU
Last modified: 2010-08-26 16:12:53 UTC
I can't figure out whether the problem is with gnome-panel or pidgin, but when I try to launch pidgin, everything seizes up. If I use ctrl-alt-F4 to move to another screen, I can "killall pidgin" and "killall gnome-panel" to get a fresh panel and use gnome again.
Is it really gnome-panel that uses 100% of the CPU? Could you attach to it with gdb and see what it's doing?
top definitely shows gnome-panel using all that CPU. I need some help "attaching with gdb," however, so I'm reading up.
(In reply to comment #2) > I need some help "attaching with gdb," however, so I'm reading up. http://live.gnome.org/GettingTraces/Details#gdb-already-running But instead of waiting for the program to crash, press ctrl+c in gdb when the panel uses 100%. You'll have the same result.
Thanks.
FWIW, this mysteriously stopped, though since then I regularly find I have to issue killall gnome-panel to reload my user menu when I'm done booting. Otherwise, I just have a gap in my panel.
can I close this bug?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!