GNOME Bugzilla – Bug 317790
Evolution is not responding
Last modified: 2009-10-27 04:34:12 UTC
Distribution/Version: Ubuntu Breezy 5.10 Well, quite usal: 1. Start Up 2. Fetch Mail via IMAP 3. Read Mail 4a. Change Folder while it's fetching new headers 4b. Read New Mail while it's fetching new headers 5. Wait...wait....wait....Evolution is not responding
Created attachment 52957 [details] Strace Log of a "not responding" evolution session Because there is no real crash, I hope you can do something with this strace log.
hi stephan, thanks for the bug report. Could you provide a stack trace of the hang? You could connect to the running (and hung) evolution process and a "thread apply all bt" would be of great help. Thanks
something similar for me... easy to reproduce: 1. go to one folder with a gpg signed mail 2. search for that mail so other disappear from the view 3. select the mail 4. reset the search 5. watch how evolution locks up while verifying the signature below is the "thread apply all bt" backtrace... hope it's useful even with all the ????
+ Trace 63355
X-Mailer: bug-buddy 2.10.0 Distribution: SuSE Linux 9.3 (i586) Package: Evolution Severity: normal Version: GNOME2.10.0 2.4.x Gnome-Distributor: SUSE Synopsis: crash/deadlock while expunging IMAP trash folder Bugzilla-Product: Evolution Bugzilla-Component: Mailer Bugzilla-Version: 2.4.x BugBuddy-GnomeVersion: 2.0 (2.10.0) i'm going to submit another stack trace here. had deleted about 80 messages in a folder, went to the trash folder and chose "expunge". i then could still click on another folder in the folder list and it was marked, but evolution did not change to that folder anymore. after a while, i got the "your application has crashed" gnome popup. this is IMAP and not IMAP4rev1, i'd say that this is not 100% reproducible but happens from time to time. so let the stacktrace dupfinder mark this as a dup... ;-) Debugging Information: Backtrace was generated from '/opt/gnome/bin/evolution-2.4' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 1097879136 (LWP 10535)] [New Thread 1119374256 (LWP 10594)] [Thread debugging using libthread_db enabled] [New Thread 1097879136 (LWP 10535)] [New Thread 1119374256 (LWP 10594)] [Thread debugging using libthread_db enabled] [New Thread 1097879136 (LWP 10535)] [New Thread 1119374256 (LWP 10594)] [New Thread 1127226288 (LWP 10593)] [New Thread 1153682352 (LWP 10574)] [New Thread 1151048624 (LWP 10564)] [New Thread 1148648368 (LWP 10562)] [New Thread 1144445872 (LWP 10560)] [New Thread 1142340528 (LWP 10559)] [New Thread 1140239280 (LWP 10558)] [New Thread 1135635376 (LWP 10556)] [New Thread 1131428784 (LWP 10554)] [New Thread 1125125040 (LWP 10551)] [New Thread 1121479600 (LWP 10550)] [New Thread 1117146032 (LWP 10548)] [New Thread 1110653872 (LWP 10537)] 0xffffe410 in ?? ()
+ Trace 63398
Thread 6 (Thread 1148648368 (LWP 10562))
reopening, don't know if it's enough information though
Created attachment 53226 [details] gdb trace this is a gdb trace as requested.
Stephans stack trace surely shows a hang. The trace in comment #3 points to some lockup in dbus ( guess its the new mail notify plugin). Stephan try disabling the new-mail-notify plugin (in Edit->plugins), This should solve this issue. Its a work around really. Am sure a lot of dbus issues were fixed in the 2.4.x release. Do you have dbus installed?? Andre, the stack trace you provided (comment #4)is a crash. I am sure i have seen this trace before, dont really remember though. Thanks.
Hey, well yes, I'm running latest gnome (2.12.1 that is). Just disabled now the new-email-notify plugin...let's see what's happening :) \sh
Disabling the new-mail-notify plugin doesn't solve it for me... it's still freezing when I do what I've written in comment #3 btw... this is in a imap4 folder
Hi, after disabling the new mail notifier plugin I have crashes again. less then before, but anyways. Here is the stack trace:
+ Trace 63472
regards, \sh
Fixed this on HEAD quite sometime ago. Closing bug
reopening bug. Sebastian still faces the issue, with his gnome 2.13-91 build.
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.
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.