GNOME Bugzilla – Bug 341424
evolution crashes on startup while opening a certain folder
Last modified: 2009-05-08 06:33:57 UTC
Steps to reproduce: although this is 100% reproducable for me it won't for you. I *think* evo is starting in a folder where it is supposed to do a full message search. and voila it gives this bt. Stack trace: gdb /usr/bin/evolution-2.6 GNU gdb 6.4-debian Copyright 2005 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "powerpc-linux-gnu"...Using host libthread_db library "/lib/tls/libthread_db.so.1". (gdb) r Starting program: /usr/bin/evolution-2.6 [Thread debugging using libthread_db enabled] [New Thread 805658656 (LWP 3626)] (evolution-2.6:3626): evolution-mail-WARNING **: ignored this junk plugin: not enabled or we have already loaded one (evolution-2.6:3626): e-utils-WARNING **: Plugin 'Spamassassin junk plugin' failed to load hook 'org.gnome.evolution.mail.junk:1.0' (evolution-2.6:3626): camel-WARNING **: camel_exception_get_id called with NULL parameter. [New Thread 816538848 (LWP 3659)] [New Thread 825058528 (LWP 3660)] [Thread 825058528 (LWP 3660) exited] [New Thread 833840352 (LWP 3661)] libnm_glib_nm_state_cb: dbus returned an error. (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files [New Thread 825058528 (LWP 3662)] [New Thread 842228960 (LWP 3663)] [New Thread 850617568 (LWP 3664)] [New Thread 859006176 (LWP 3665)] [Thread 850617568 (LWP 3664) exited] [New Thread 850617568 (LWP 3679)] Program received signal SIGSEGV, Segmentation fault.
+ Trace 68167
Thread 805658656 (LWP 3626)
Other information:
Created attachment 65253 [details] Valgrind of evo until it crashes
bug 338451 could be a dup of this
*** Bug 365734 has been marked as a duplicate of this bug. ***
*** Bug 373450 has been marked as a duplicate of this bug. ***
Does this still happen with 2.22 or 2.24? If not, it's probably OBSOLETE.
Thanks for taking the time to report this bug; however, closing due to lack of response of the reporter, sorry. if you still see this issue with a current release of evolution (2.26.1.1 or later), please reopen. thanks in advance.