Red Hat Bugzilla – Bug 103916
Evolution main window becomes non-responsive after clicking the close ("X") button
Last modified: 2007-04-18 12:57:25 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703
Description of problem:
Trying to close evolution causes it to become non-responsive. A pop-up prompts
user to force quit because the window is not responding.
Client system is severn beta up2date against RHN.
IMAP server is imap-2001a-18.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open evolution against an imap server.
2. Click Send/Receive at least once.
2. Click the 'x' button at top-right of screen to close app.
Actual Results: Pop-up that reports:
The window "INBOX (1) - Ximian Evolution" is not responding.
Forcing this application to quit will cause you to lose any unsaved changes.
Must click "force quit".
`ps -ef | grep evolution` then shows:
paul 32392 1 0 09:00 ? 00:00:00
paul 32394 1 0 09:00 ? 00:00:00
These two procesesses must be killed before evolution will start again.
Expected Results: App should close normally.
If I close out of evolution before clicking send/receive, then the app closes
Created attachment 94285 [details]
shell script to kill evolution processes
Since I have this problem too (IMAP, evo won't shutdown properly), I revived an
old evolution favorite: killev. Its just a little shell script, and I'm sure it
could be done more eloquently, but it works for me (tm).
If you click cancel, does it eventually quit? I think there's a timing issue
here where it gets carried away starting to clean up without pinging to say it's
Clicking cancel and leaving for as long as 8-9 minutes had no effect.
Can you attach to the process with gdb and see where it's spinning?
evolution-debuginfo package is at
Installed evolution-1.4.4-6 from RHN; bug still present.
... still there with 1.4.4-7.
*** This bug has been marked as a duplicate of 102554 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.