After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 611816 - When launching pidgin, gnome-panel starts using 100% of CPU
When launching pidgin, gnome-panel starts using 100% of CPU
Product: gnome-panel
Classification: Other
Component: panel
Other Linux
: Normal major
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Reported: 2010-03-04 16:21 UTC by amanda
Modified: 2010-08-26 16:12 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description amanda 2010-03-04 16:21:36 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.
Comment 1 Vincent Untz 2010-03-09 03:43:33 UTC
Is it really gnome-panel that uses 100% of the CPU? Could you attach to it with gdb and see what it's doing?
Comment 2 amanda 2010-03-09 14:19:51 UTC
top definitely shows gnome-panel using all that CPU. 

I need some help "attaching with gdb," however, so I'm reading up.
Comment 3 Vincent Untz 2010-03-09 14:25:49 UTC
(In reply to comment #2)
> I need some help "attaching with gdb," however, so I'm reading up.

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.
Comment 4 amanda 2010-03-09 14:44:24 UTC
Comment 5 amanda 2010-04-23 21:58:45 UTC
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.
Comment 6 Fabio Durán Verdugo 2010-06-05 04:53:04 UTC
can I close this bug?
Comment 7 Fabio Durán Verdugo 2010-08-26 16:12:53 UTC
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.