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 127056 - clock applets uses 100% cpu at gnome start.
clock applets uses 100% cpu at gnome start.
Status: RESOLVED DUPLICATE of bug 122327
Product: gnome-panel
Classification: Other
Component: notification area
2.4.x
Other Linux
: Normal major
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-11-15 17:10 UTC by Fred Blaise
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.3/2.4


Description Fred Blaise 2003-11-15 17:10:46 UTC 
I have gkrellm to start when I login to Gnome. My CPU utilization shows a
100%, until i bring my mouse over the clock applet, or click on it. Then it
drops back down to 0-1%.
This is not gkrellm going crazy, because I can hear my fan going nuts as
well, and dimishing when my mouse is on the clock applet.
Comment 1 Fred Blaise 2003-11-18 02:47:26 UTC 
The clock applet is definitly the cause of the CPU usage. If I remove
it, the CPU usage is normal at startup.
Also, the gnome splash was hung 100% of the time, and needed to be
clicked to get rid of. This problem was resolved when the clock applet
was removed. It seems to have gone away after reinserting the clock
applet, but the abnormal CPU usage is still there.
Comment 2 Vincent Untz 2003-11-20 09:05:01 UTC 
Can you do a 'top' on a terminal. I'm pretty sure it's not the clock
but the notification area which is the problem (and it stops doing
that once you click on the panel). If so, this is a duplicate of bug
#122327.
Comment 3 Fred Blaise 2003-11-20 13:43:02 UTC 
I have done a top and the notification area seems to be the problem,
as you pointed.
I have 2 notification areas in my panel, and clicking the second one
also makes the CPU go down.
I think this bug can now be considered a duplicate.
Good call. :)

I couldn't seem to complete the attachment, so it is also here
(Screenshot of 'top' at X startup).
http://fred.blaisern.com/top_shot.png

I changed the component from clock-applet to notification-area-applet.
I am still very new to the 'report bugs process', so let me know if I
shouldn't have done that.

Thanks.

--fb
Comment 4 Vincent Untz 2003-11-20 13:51:47 UTC 
I'm marking this bug as duplicate of the other bug.

*** This bug has been marked as a duplicate of 122327 ***