GNOME Bugzilla – Bug 561644
Evolution crashed while closing
Last modified: 2009-09-08 04:12:19 UTC
Steps to reproduce: Not Reproducible. I had one exchange-mapi account and one groupwise account in Evolution. Evolution just crashed when I tried close it. Stack trace: exchange-mapi-connection.c(1214): Leaving exchange_mapi_connection_fetch_items: folder-id 0660FED31A000001 [New Thread 0xab7b5b90 (LWP 4002)] [Thread 0xac7b5b90 (LWP 3995) exited] [Thread 0xb52ddb90 (LWP 3994) exited] [Thread 0xab7b5b90 (LWP 4002) exited] [New Thread 0xab7b5b90 (LWP 4003)] [Thread 0xab7b5b90 (LWP 4003) exited] [New Thread 0xab7b5b90 (LWP 4008)] removing cache for Mailbox - KVBV Prasad/account 1258 0x8569fb8 done .. now 1258 [Thread 0xab7b5b90 (LWP 4008) exited] [New Thread 0xab7b5b90 (LWP 4033)] Program received signal SIGSEGV, Segmentation fault. __pthread_mutex_lock (mutex=0x736b4261) at pthread_mutex_lock.c:51 51 pthread_mutex_lock.c: No such file or directory. in pthread_mutex_lock.c (gdb) t a a bt
+ Trace 210034
Thread 1 (Thread 0xb5fa0760 (LWP 3561))
Other information:
I do not know if it is dup of bug 554861 but it still happened after 2.24.1.
Similar crash when switching between public folders in MAPI account Program received signal SIGSEGV, Segmentation fault. __pthread_mutex_lock (mutex=0x61726170) at pthread_mutex_lock.c:51 51 pthread_mutex_lock.c: No such file or directory. in pthread_mutex_lock.c (gdb) t a a bt
+ Trace 210041
Thread 1 (Thread 0xb5fa0760 (LWP 12364))
It doesn't look like the crash is because of MAPI. can you try with srag's suggestion on bug 554861 and check whether this still happens ?
I've tested with 2.24.1 and the latest evolution-mapi rpms while doing the above testing. Anyway, I was not able to reproduce it always and could not find a particular scenario where it crashes exactly.
*** Bug 566023 has been marked as a duplicate of this bug. ***
Based on the dup : Moving to Evolution.
*** Bug 575815 has been marked as a duplicate of this bug. ***
could be dupe of bug 554861 which was marked as fixed but crash seems to be still there.
*** Bug 580597 has been marked as a duplicate of this bug. ***
last dupe in 2.26.x
got crash in 2.26.1.1 ..looks same Program received signal SIGSEGV, Segmentation fault. 0x00007fb36dfd758a in pthread_mutex_lock () from /lib64/libpthread.so.0 (gdb) t a a bt
+ Trace 215212
Thread 1 (Thread 0x7fb371e747f0 (LWP 4922))
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 473887 ***
*** Bug 594364 has been marked as a duplicate of this bug. ***