Bug 352715 – Evolution crash on startup

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 352715 - Evolution crash on startup


Summary:	Evolution crash on startup


Status:	RESOLVED DUPLICATE of bug 274329

Product:	evolution
Classification:	Applications
Component:	Mailer
Version:	unspecified
Hardware:	Other other

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-08-24 18:43 UTC by Gary Bickford
Modified:	2006-08-25 01:58 UTC

See Also:
GNOME target:	---
GNOME version:	2.9/2.10

Description Gary Bickford 2006-08-24 18:43:16 UTC

Distribution: Fedora Core release 4 (Stentz)
Package: Evolution
Severity: normal
Version: GNOME2.10.0 unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: Evolution crash on startup
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:
Evolution crashes on startup, no matter how it is started.  Problem may
be related to large imap folder, or possibly confusion between previous
state and new state - it says retrieving message 8652 when it crashes.  
I often view and edit mail using webmail as well as evolution, because
evolution often doesn't show all the mail.

Steps to reproduce the crash:
1. Start Evolution
2. 
3. 

Expected Results:


How often does this happen?
It now crashes all the time.  I haven't figured out how to fix it.


Additional Information:



Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
`shared object read from target memory' has disappeared; keeping its
symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208219984 (LWP 1838)]
[New Thread -1297093728 (LWP 1876)]
[New Thread -1286603872 (LWP 1875)]
[New Thread -1274881120 (LWP 1869)]
[New Thread -1264391264 (LWP 1868)]
[New Thread -1263826016 (LWP 1849)]
[New Thread -1252688992 (LWP 1848)]
[New Thread -1221219424 (LWP 1846)]
[New Thread -1242199136 (LWP 1844)]
[New Thread -1231709280 (LWP 1843)]
[New Thread -1210729568 (LWP 1841)]
(no debugging symbols found)
0x00be6402 in __kernel_vsyscall ()

+ Trace 70933

Thread 1 (Thread -1208219984 (LWP 1838))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/libc.so.6
#6 abort
from /lib/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 dbus_connection_setup_with_g_main
from /usr/lib/libdbus-glib-1.so.1
#10 org_gnome_new_mail_config
from /usr/lib/evolution/2.2/plugins/liborg-gnome-new-mail-notify.so
#11 e_plugin_xml_content
from /usr/lib/evolution/2.2/libeutil.so.0
#12 e_plugin_invoke
from /usr/lib/evolution/2.2/libeutil.so.0
#13 e_event_target_new
from /usr/lib/evolution/2.2/libeutil.so.0
#14 e_event_emit
from /usr/lib/evolution/2.2/libeutil.so.0
#15 em_folder_view_open_selected
from /usr/lib/evolution/2.2/components/libevolution-mail.so
#16 mail_empty_trash
from /usr/lib/evolution/2.2/components/libevolution-mail.so
#17 mail_msg_free
from /usr/lib/evolution/2.2/components/libevolution-mail.so
#18 g_vasprintf
from /usr/lib/libglib-2.0.so.0
#19 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#20 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#21 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#22 bonobo_main
from /usr/lib/libbonobo-2.so.0
#23 main





------- Bug created by bug-buddy at 2006-08-24 18:43 -------

Comment 1 Sergej Kotliar 2006-08-25 01:58: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.


Exact copy of 351492, which is a duplicate of 274329.

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