Bug 440643 – crash in Evolution: Subscribing IMAP folder ...

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 440643 - crash in Evolution: Subscribing IMAP folder ...


Summary:	crash in Evolution: Subscribing IMAP folder ...


Status:	RESOLVED DUPLICATE of bug 377715

Product:	evolution
Classification:	Applications
Component:	general
Version:	2.10.x (obsolete)
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-05-23 08:44 UTC by Frederic Crozat
Modified:	2007-06-21 17:00 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description Frederic Crozat 2007-05-23 08:44:44 UTC

What were you doing when the application crashed?
Subscribing IMAP folder and checking a newly subscribed folder


Distribution: Mandriva Linux release 2007.1 (Official) for i586
Gnome Release: 2.18.0 2007-03-15 (Mandriva)
BugBuddy Version: 2.18.0

System: Linux 2.6.17-13mdv #1 SMP Fri Mar 23 19:03:31 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Ia Ora Blue
Icon Theme: gnome

Memory status: size: 504492032 vsize: 504492032 resident: 258740224 share: 12054528 rss: 258740224 rss_rlim: 4294967295
CPU usage: start_time: 1179741602 rtime: 811405 utime: 471595 stime: 339810 cutime:219 cstime: 513 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1236642080 (LWP 6557)]
[New Thread -1269916768 (LWP 6875)]
[New Thread -1343226976 (LWP 6578)]
[New Thread -1322255456 (LWP 6577)]
[New Thread -1316639840 (LWP 6576)]
[New Thread -1308247136 (LWP 6575)]
[New Thread -1299854432 (LWP 6572)]
[New Thread -1280312416 (LWP 6570)]
[New Thread -1261487200 (LWP 6566)]
[New Thread -1253094496 (LWP 6565)]
0xbfffe410 in __kernel_vsyscall ()

+ Trace 135647

Thread 4 (Thread -1322255456 (LWP 6577))

#0 __kernel_vsyscall
#1 __lll_mutex_lock_wait
from /lib/i686/libpthread.so.0
#2 _L_mutex_lock_71
from /lib/i686/libpthread.so.0
#3 pthread_kill
from /lib/i686/libpthread.so.0
#4 <signal handler called>
#5 ??
#6 camel_message_info_uint32
at camel-folder-summary.c line 2985
#7 vee_info_uint32
at camel-vee-summary.c line 71
#8 camel_message_info_uint32
at camel-folder-summary.c line 2985
#9 vtrash_getv
at camel-vtrash-folder.c line 141
#10 camel_object_get
at camel-object.c line 1598
#11 camel_folder_get_unread_message_count
at camel-folder.c line 584
#12 update_1folder
at mail-folder-cache.c line 367
#13 folder_changed
at mail-folder-cache.c line 462
#14 camel_object_trigger_event
at camel-object.c line 1504
#15 vtrash_add_folder
at camel-vtrash-folder.c line 520
#16 camel_vee_folder_add_folder
at camel-vee-folder.c line 223
#17 camel_store_get_folder
at camel-store.c line 266
#18 mail_tool_uri_to_folder
at mail-tools.c line 333
#19 get_folder_get
at mail-ops.c line 1221
#20 mail_msg_received
at mail-mt.c line 582
#21 thread_dispatch
at e-msgport.c line 1005
#22 start_thread
from /lib/i686/libpthread.so.0
#23 clone
from /lib/i686/libc.so.6



----------- .xsession-errors (972656 sec old) ---------------------
(evolution:14937): camel-WARNING **: Could not find key entry for word 'definitely': Aucun fichier ou r\xe9pertoire de ce type
(evolution:14937): camel-WARNING **: Could not find key entry for word 'just': Aucun fichier ou r\xe9pertoire de ce type
(evolution:14937): camel-WARNING **: Could not find key entry for word 'global': Aucun fichier ou r\xe9pertoire de ce type
(evolution:14937): camel-WARNING **: Could not find key entry for word 'why': Aucun fichier ou r\xe9pertoire de ce type
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 palfrey 2007-05-23 13:39:06 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance!

Comment 2 Frederic Crozat 2007-05-23 14:35:00 UTC

ahem, stacktrace has debugging symbols ;)

Comment 3 palfrey 2007-05-23 14:51:12 UTC

Ah, yep... too quick on clicking the stock responses! Can you reproduce this under gdb? Preferably with G_SLICE set to debug-blocks in the environment first..

Comment 4 André Klapper 2007-06-21 17:00:02 UTC

it's just the same issue as bug 377715.

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