Bug 335267 – Evolution consistenly crashes on exit

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 335267 - Evolution consistenly crashes on exit


Summary:	Evolution consistenly crashes on exit


Status:	RESOLVED OBSOLETE

Product:	evolution
Classification:	Applications
Component:	general
Version:	2.4.x (obsolete)
Hardware:	Other other

Importance:	High critical
Target Milestone:	---
Assigned To:	Harish Krishnaswamy
QA Contact:	Evolution QA team

URL:
Whiteboard:

Duplicates:	347579 (view as bug list)
Depends on:
Blocks:

Reported:	2006-03-20 19:01 UTC by vik
Modified:	2008-11-17 22:14 UTC

See Also:
GNOME target:	---
GNOME version:	2.11/2.12

Description vik 2006-03-20 19:02:00 UTC

Distribution: Ubuntu 5.10 (breezy)
Package: Evolution
Priority: Normal
Version: GNOME2.12.1 unspecified
Gnome-Distributor: Ubuntu
Synopsis: Evolution consistenly crashes on exit
Bugzilla-Product: Evolution
Bugzilla-Component: Miscellaneous
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.12.0)
Description:
Description of the crash:

Evolution displays an "Application closed unexpectedly" dialogue.

Steps to reproduce the crash:
1.  Modify a mail folder (ie delete mail message)
2. Select quit
3. Watch crash

Expected Results:

Clean exit.

How often does this happen?

Every time

Additional Information:

Ubuntu Breezy installation. The .evolution directory has been copied
back & forth between 2 PCs a few times, both running Breezy.


Debugging Information:

Backtrace was generated from '/usr/bin/evolution-2.4'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1229780768 (LWP 7277)]
[New Thread -1298617424 (LWP 7820)]
[New Thread -1281360976 (LWP 7289)]
[New Thread -1278977104 (LWP 7286)]
[New Thread -1270182992 (LWP 7285)]
[New Thread -1261782096 (LWP 7283)]
[New Thread -1253221456 (LWP 7282)]
[New Thread -1244435536 (LWP 7280)]
[New Thread -1236042832 (LWP 7279)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 67076

Thread 3 (Thread -1281360976 (LWP 7289))

#0 __kernel_vsyscall
#1 __lll_mutex_lock_wait
from /lib/tls/i686/cmov/libpthread.so.0
#2 _L_mutex_lock_33
from /lib/tls/i686/cmov/libpthread.so.0
#3 ??
#4 ??
#5 ??
from /lib/tls/i686/cmov/libpthread.so.0
#6 ??
#7 ??
#8 ??
from /lib/tls/i686/cmov/libc.so.6
#9 ??
#10 ??
#11 ??
#12 pthread_mutex_lock
from /lib/tls/i686/cmov/libc.so.6
#13 pthread_mutex_lock
from /lib/tls/i686/cmov/libc.so.6
#14 es_menu_hook_get_type
#15 <signal handler called>
#16 ??
#17 camel_vee_folder_get_location
from /usr/lib/libcamel-provider-1.2.so.6
#18 camel_object_trigger_event
from /usr/lib/libcamel-1.2.so.0
#19 camel_vee_folder_get_location
from /usr/lib/libcamel-provider-1.2.so.6
#20 camel_vee_folder_remove_folder
from /usr/lib/libcamel-provider-1.2.so.6
#21 camel_vee_folder_get_location
from /usr/lib/libcamel-provider-1.2.so.6
#22 camel_object_unref
from /usr/lib/libcamel-1.2.so.0
#23 camel_vee_folder_get_location
from /usr/lib/libcamel-provider-1.2.so.6
#24 camel_session_get_filter_driver
from /usr/lib/libcamel-provider-1.2.so.6
#25 mail_send
from /usr/lib/evolution/2.4/components/libevolution-mail.so
#26 camel_session_thread_msg_free
from /usr/lib/libcamel-provider-1.2.so.6
#27 camel_session_thread_msg_free
from /usr/lib/libcamel-provider-1.2.so.6
#28 e_thread_new
from /usr/lib/libedataserver-1.2.so.4
#29 e_thread_busy
from /usr/lib/libedataserver-1.2.so.4
#30 start_thread
from /lib/tls/i686/cmov/libpthread.so.0
#31 clone
from /lib/tls/i686/cmov/libc.so.6





------- Bug created by bug-buddy at 2006-03-20 19:02 -------

Comment 1 André Klapper 2006-03-21 22:45:36 UTC

could be a duplicate of bug 272556, but the stacktrace is not totally identical

Comment 2 André Klapper 2006-07-15 09:01:42 UTC

*** Bug 347579 has been marked as a duplicate of this bug. ***

Comment 3 André Klapper 2006-07-15 09:02:24 UTC

confirming as per duplicate.

Comment 4 André Klapper 2008-11-15 21:50:21 UTC

Does this still happen with 2.22 or 2.24?
If not, it's probably OBSOLETE.

Comment 5 Vik Olliver 2008-11-17 21:26:57 UTC

Not happened for a long, long time. I think we're a good few releases of Ubuntu down the line now. Might as well kill it.