Bug 417778 – evo crashes on "enable account"

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 417778 - evo crashes on "enable account"


Summary:	evo crashes on "enable account"


Status:	RESOLVED DUPLICATE of bug 324168

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

Importance:	Normal critical
Target Milestone:	---
Assigned To:	evolution-mail-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-03-13 08:11 UTC by James Utter
Modified:	2008-01-22 06:32 UTC

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

Description James Utter 2007-03-13 08:11:04 UTC

Steps to reproduce:
1. If you have an email account which has Search Folders linking to it, go to "Evolution Preferences"
2. Select the account and press Disable 
3. Then press Enable

Evolution is consistently crashing for me upon clicking enable.


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 -1231968576 (LWP 11601)]
[New Thread -1265775696 (LWP 11623)]
[New Thread -1255277648 (LWP 11622)]
[New Thread -1246884944 (LWP 11621)]
[New Thread -1238254672 (LWP 11620)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 118217

Thread 3 (Thread -1255277648 (LWP 11622))

#0 __kernel_vsyscall
#1 __lll_mutex_lock_wait
from /lib/tls/i686/cmov/libpthread.so.0
#2 _L_mutex_lock_29
from /lib/tls/i686/cmov/libpthread.so.0
#3 ??
#4 g_mem_gc_friendly
from /usr/lib/libglib-2.0.so.0
#5 ??
#6 ??
#7 ??
#8 ??
#9 pthread_mutex_destroy
from /lib/tls/i686/cmov/libpthread.so.0
#10 segv_redirect
at main.c line 433
#11 <signal handler called>
#12 camel_message_info_free
at camel-folder-summary.c line 2661
#13 vee_message_info_free
at camel-vee-summary.c line 45
#14 camel_message_info_free
at camel-folder-summary.c line 2678
#15 unmatched_check_uid
at camel-vee-folder.c line 866
#16 g_hash_table_foreach
from /usr/lib/libglib-2.0.so.0
#17 vee_rebuild_folder
at camel-vee-folder.c line 1015
#18 vee_add_folder
at camel-vee-folder.c line 1605
#19 camel_vee_folder_add_folder
at camel-vee-folder.c line 223
#20 vfolder_adduri_do
at mail-vfolder.c line 280
#21 mail_msg_received
at mail-mt.c line 570
#22 thread_dispatch
at e-msgport.c line 998
#23 start_thread
from /lib/tls/i686/cmov/libpthread.so.0
#24 clone
from /lib/tls/i686/cmov/libc.so.6



Other information:
Here is the output when running from terminal.

~$ evolution-2.6
CalDAV Eplugin starting up ...
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.AccessDenied) A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.freedesktop.NetworkManager" member "state" error name "(unset)" destination "org.freedesktop.NetworkManager")

(evolution-2.6:11907): camel-WARNING **: Search returned an invalid result type

(evolution-2.6:11907): camel-WARNING **: Search returned an invalid result type

(evolution-2.6:11907): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.6/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
BBDB spinning up...

Comment 1 James Utter 2007-03-13 08:18:15 UTC

note: ok all those warnings on the terminal are irrelevant - they occur before the crash.

Also note: the crash occurs whether or not "mail-notification" is running

Comment 2 James Utter 2007-03-13 08:19:53 UTC

perhaps related to bug #323262 ?

Comment 3 Sankar P 2008-01-22 06:32:12 UTC


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