Bug 346569 – Crash on close

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 346569 - Crash on close


Summary:	Crash on close


Status:	RESOLVED DUPLICATE of bug 330157

Product:	evolution
Classification:	Applications
Component:	Shell
Version:	2.6.x (obsolete)
Hardware:	Other All

Importance:	Normal critical
Target Milestone:	---
Assigned To:	Evolution Shell Maintainers Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-07-04 17:15 UTC by Guille -bisho-
Modified:	2006-07-04 17:50 UTC

See Also:
GNOME target:	---
GNOME version:	2.13/2.14

Description Guille -bisho- 2006-07-04 17:15:40 UTC

Steps to reproduce:
Whenever I close evolution I get this crash. I have installed
evolution-dbg and evo-data-server-dbt to see if it helps.

It is an old .evolution directory, with but with breezy I also have this
problem. I upgraded to Dapper to see if the problem was be resolved.

How often does this happen?
Always

If you need any other info, any other -dbg package installed, please,
ask me.

Stack trace:
Backtrace was generated from '/usr/bin/evolution-2.6'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1231676512 (LWP 13894)]
[New Thread -1314915408 (LWP 13905)]
[New Thread -1302332496 (LWP 13903)]
[New Thread -1259443280 (LWP 13901)]
[New Thread -1276228688 (LWP 13900)]
[New Thread -1267835984 (LWP 13897)]
[New Thread -1251013712 (LWP 13895)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 69190

Thread 2 (Thread -1314915408 (LWP 13905))

#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 pthread_mutex_init
from /lib/tls/i686/cmov/libc.so.6
#10 pthread_mutex_lock
from /lib/tls/i686/cmov/libc.so.6
#11 segv_redirect
at main.c line 433
#12 <signal handler called>
#13 camel_object_is
at camel-object.c line 1040
#14 camel_object_unref
at camel-object.c line 892
#15 folder_changed_free
at camel-vee-folder.c line 1430
#16 session_thread_msg_free
at camel-session.c line 510
#17 ms_thread_msg_free
at mail-session.c line 557
#18 camel_session_thread_msg_free
at camel-session.c line 612
#19 session_thread_destroy
at camel-session.c line 521
#20 thread_destroy_msg
at e-msgport.c line 958
#21 thread_dispatch
at e-msgport.c line 1061
#22 start_thread
from /lib/tls/i686/cmov/libpthread.so.0
#23 clone
from /lib/tls/i686/cmov/libc.so.6



Other information:
Distribution: Ubuntu 6.06 (dapper)
Version: GNOME2.14.2 2.6.x

Comment 1 Karsten Bräckelmann 2006-07-04 17:38:32 UTC

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.


Identical stacktrace as bug 314912, which is a duplicate of bug 320772. Matches the stacktrace of bug 320772 as well. Same description.

*** This bug has been marked as a duplicate of 320772 ***

Comment 2 Karsten Bräckelmann 2006-07-04 17:50:11 UTC

Actually marking this bug as a duplicate of bug 330157, since this crash is *not* fixed. Sorry for the noise.


*** This bug has been marked as a duplicate of 330157 ***