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 535739 - Evolution Mail and Calendar: The system is voerloaded...
Evolution Mail and Calendar: The system is voerloaded...
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.22.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-05-30 12:23 UTC by javier.debian.bb.ar
Modified: 2009-10-09 10:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description javier.debian.bb.ar 2008-05-30 12:23:27 UTC
The system is voerloaded.
Sometimes, the gnome-keyring-d precess start and use all the available cpu resources, falling down all the others process.
The only way to solve this, is to close the evolution program.
And then, restart it.
Some time pass, and the problem bak again.





Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0
Comment 1 javier.debian.bb.ar 2008-05-30 13:17:26 UTC
1st:
The correct sentence is "The system is overloaded"
Sorry for my bad english.

2nd: The top report:

top - 09:58:56 up  2:12,  3 users,  load average: 4.85, 4.02, 3.24
Tasks: 129 total,   6 running, 123 sleeping,   0 stopped,   0 zombie
Cpu(s): 53.5%us, 45.8%sy,  0.0%ni,  0.0%id,  0.0%wa,  0.7%hi,  0.0%si,  0.0%st
Mem:    451188k total,   445816k used,     5372k free,     6892k buffers
Swap:  1566296k total,   149160k used,  1417136k free,    70220k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND            
 3482 user5     20   0  263m 206m 1752 R 14.6 46.8  15:08.63 gnome-keyring-d    
24122 user5     20   0  116m  15m  10m S 11.0  3.5   3:16.78 evolution          
11200 user5     20   0  158m  40m  21m S  6.6  9.3   0:37.22 firefox-bin        
 3380 user5     20   0  2340  804  660 R  6.0  0.2   6:17.58 dbus-daemon        
 3458 user5     20   0 32840  10m 8104 S  5.0  2.3   8:06.63 ksysguard          
 4043 user5     20   0  123m  21m 9.9m S  4.0  4.9   3:45.44 rhythmbox          
 3462 user5     20   0  2432  900  712 S  3.7  0.2   4:27.16 ksysguardd         
24131 user5     20   0 48856 6436 5668 S  3.3  1.4   1:03.09 evolution-excha    
 3465 user5     20   0  7524 2684 1560 S  3.0  0.6   2:55.75 gconfd-2           
14164 root      20   0 80544  16m  10m S  2.7  3.8   0:01.26 gnome-terminal     
 2857 root      20   0  2012  640  588 S  0.7  0.1   0:00.38 dhcdbd             
 3439 user5     20   0 11920 2412 1916 R  0.7  0.5   0:06.14 artsd              
 3474 user5     20   0 33468 5608 5024 S  0.7  1.2   0:00.76 knotify            
 3477 user5     20   0 10532 1156 1068 S  0.7  0.3   0:02.72 gdl_config         
    1 root      20   0  2032  556  528 S  0.0  0.1   0:01.28 init               
    2 root      15  -5     0    0    0 S  0.0  0.0   0:00.00 kthreadd     

Comment 2 javier.debian.bb.ar 2008-06-02 17:39:58 UTC
Temporally, I could stop the problem by unchecking the option "Automatically synchronize account locally" on the Receiving option tab of the Account editor.

Comment 3 Akhil Laddha 2009-08-26 10:49:08 UTC
This version is no longer maintained, which means that it will not receive any
further security or bug fix updates.
The current stable GNOME and Evolution version is 2.26.

Can you please check again whether this issue still happens in Evolution 2.24
or 2.26 and update this report by adding a comment and changing the "Version"
field? Thanks a lot.

Again thank you for reporting this bug and we are sorry it could not be fixed
for the version you originally used here.

Without feedback this report will be closed as INCOMPLETE in 6 weeks.
Comment 4 Akhil Laddha 2009-10-09 10:43:11 UTC
Thanks for taking the time to report this bug; however, closing due to lack of
response of the reporter, sorry. if you still see this issue with a current
release of evolution (2.26.3 or 2.28.x or later), please reopen. thanks in advance.