GNOME Bugzilla – Bug 657886
Evolution hangs while the password dialog is not displayed.
Last modified: 2011-10-21 07:35:35 UTC
Somehow the Evolution window greyed out (just grey, nothing is readable) and is unresponsive. Attaching to the process using `gdb --pid …` it looks like it is waiting for a password to be entered for two IMAP accounts (Thread 2 and 3, account names changed), but I cannot find that dialog anywhere on my desktop. (gdb) t a a bt full
+ Trace 228303
How can I resurrect that Evolution session? Evolution sometimes shows up in `top` but it does not use any CPU resources.
Thanks for a bug report. I donot see anything special about evolution in the backtrace, it's just like you wrote above, two threads are waiting for a password prompt and nothing else evolution-related is happening in there. The main thread is stuck on a tooltip querying, doing some X call. Is there any runtime warning on the console when you are running evolution? And will anything change if you move mouse away from the evolution's window, thus it'll not need to query a tooltip when it's run? I confess I've not much idea what can be wrong here, though.
(In reply to comment #1) > Thanks for a bug report. Thank you for following up on my report. > I donot see anything special about evolution in the > backtrace, it's just like you wrote above, two threads are waiting for a > password prompt and nothing else evolution-related is happening in there. The > main thread is stuck on a tooltip querying, doing some X call. Is there any > runtime warning on the console when you are running evolution? I do not remember. I will take a look next time this happens. > And will anything change if you move mouse away from the evolution's window, thus it'll > not need to query a tooltip when it's run? I confess I've not much idea what > can be wrong here, though. Well I moved the mouse pointer away into other virtual desktops and put for example a terminal window above Evolution, but nothing changed. I will report back when I have more information.
Paul, do you have any update for the bug ?
(In reply to comment #3) > Paul, do you have any update for the bug ? It looks like the problem has been fixed somewhere in between. If the Evolution suite was the culprit then it must have been fixed in version 3.0.3 since I upgraded to that version on September 3rd. Therefore I am closing that bug as fixed although I do not know which commit solved it.