GNOME Bugzilla – Bug 218177
Disable IMAP Account causes crash
Last modified: 2013-09-13 00:48:58 UTC
Package: Evolution Priority: Normal Version: 1.0 Synopsis: Disable IMAP Account causes crash Bugzilla-Product: Evolution Bugzilla-Component: Mailer Description: Whenever I disable an IMAP account it causes a crash. Debugging Information: (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 1024 (LWP 14213)] [New Thread 2049 (LWP 14229)] [New Thread 1026 (LWP 14230)] [New Thread 2051 (LWP 14231)] [New Thread 3076 (LWP 14234)] 0x40c264f9 in wait4 () from /lib/libc.so.6
+ Trace 15762
Unknown reporter: dcolling@abyssnet.com, changed to bugbuddy-import@ximian.com.
Unfortunately, through no fault of your own, this trace is pretty useless. If you can reproduce this crash with a specific set of actions, please let us know, and please keep submitting traces- the next one may be the one that helps us fix the bug. Thanks!
Ok, it is pretty easy to reproduce here: create an imap mailbox then delete it. Crash. The IMAP server is HP OpenMail for Linux if that is any use. I'll test it against UW IMAP2000 here to see if that makes a difference.
it would be great, if you can attach the complete stack trace of the discussion with the server?
closing due to lack of user response.
*** Bug 302025 has been marked as a duplicate of this bug. ***
Stack trace from bug #302025 Backtrace was generated from '/opt/gnome/bin/evolution' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 1095053824 (LWP 31390)] [New Thread 1129155504 (LWP 547)] [Thread debugging using libthread_db enabled] [New Thread 1095053824 (LWP 31390)] [New Thread 1129155504 (LWP 547)] [Thread debugging using libthread_db enabled] [New Thread 1095053824 (LWP 31390)] [New Thread 1129155504 (LWP 547)] [New Thread 1128889264 (LWP 546)] [New Thread 1123838896 (LWP 31660)] [New Thread 1119828912 (LWP 31640)] [New Thread 1117727664 (LWP 31639)] [New Thread 1114844080 (LWP 31411)] [New Thread 1112542128 (LWP 31403)] [New Thread 1108347824 (LWP 31402)] [New Thread 1106242480 (LWP 31399)] [New Thread 1104141232 (LWP 31398)] 0xffffe410 in ?? ()
+ Trace 59036
Thread 1 (Thread 1095053824 (LWP 31390))
Based on the stack trace reopening the bug.
I cant reproduce this irrespective of what i do, The stack trace seems to give out little except for the straight forward information that this line crashes if (mi->real->summary == ssummary) Hence mi->real should be NULL the scenarios when it becomes NULL is still shrouded in darkness as i cant reproduce it. Let me know if this is still reproducible on latest version or i can just close the bug
I reported this bug a long time ago when I was using IMAP provided by HP OpenMail. I no longer use that IMAP. I just tried deleting an IMAP account served by Dovecot and there was no crash, so I guess it can be closed as far as I am concerned. The original bug was very blatant: it crashed immediately when you pushed the delete button.
ok. Closing the bug as OBSOLETE. Thanks
Shreyas: Just got the crash with Evolution 2.3.8. Reopening the bug. Backtrace was generated from '/opt/gnome/bin/evolution' Using host libthread_db library "/lib/tls/libthread_db.so.1". `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. [Thread debugging using libthread_db enabled] [New Thread 1099326016 (LWP 17543)] [New Thread 1266576304 (LWP 17684)] [Thread debugging using libthread_db enabled] [New Thread 1099326016 (LWP 17543)] [New Thread 1266576304 (LWP 17684)] [New Thread 1266310064 (LWP 17683)] [New Thread 1206913968 (LWP 17588)] [New Thread 1203301296 (LWP 17581)] [New Thread 1201200048 (LWP 17580)] [New Thread 1199098800 (LWP 17579)] [New Thread 1196604336 (LWP 17577)] [New Thread 1196338096 (LWP 17576)] [New Thread 1194236848 (LWP 17575)] [New Thread 1192135600 (LWP 17557)] [New Thread 1150598064 (LWP 17556)] [New Thread 1148103600 (LWP 17555)] [Thread debugging using libthread_db enabled] [New Thread 1099326016 (LWP 17543)] [New Thread 1266576304 (LWP 17684)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 62635
Thread 1 (Thread 1099326016 (LWP 17543))
Nagappan, reopening this bug and marking the other a duplicate was kind of pointless ... But anyway, if you can recreate it, can you try in valgrind. I've never seen this before.
This bug has been fixed on head.