Bug 351492 – Evolution crashes at start

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 351492 - Evolution crashes at start


Summary:	Evolution crashes at start


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-15 16:06 UTC by Gary Bickford
Modified:	2006-08-15 16:47 UTC

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

Description Gary Bickford 2006-08-15 16:06:43 UTC

Distribution: Fedora Core release 4 (Stentz)
Package: Evolution
Severity: major
Version: GNOME2.10.0 unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: Evolution crashes at start
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:
Evolution is crashing every time I start it.

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

Expected Results:
evolution runs

How often does this happen?
every time

Additional Information:
If I just start evolution from the command line or from a button, then
the standard evolution mail window comes up before it crashes.  It also
occurs when I click a link in the browser to send an email.  In that
case, both the standard evolution mail window and the compose window
come up correctly, then the crash occurs.  


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 -1208805712 (LWP 10322)]
[New Thread -1286607968 (LWP 10335)]
[New Thread -1276118112 (LWP 10334)]
[New Thread -1243182176 (LWP 10333)]
[New Thread -1253672032 (LWP 10332)]
[New Thread -1264235616 (LWP 10329)]
[New Thread -1232295008 (LWP 10326)]
[New Thread -1221805152 (LWP 10325)]
[New Thread -1211315296 (LWP 10324)]
(no debugging symbols found)
0x00be6402 in __kernel_vsyscall ()

+ Trace 70500

Thread 1 (Thread -1208805712 (LWP 10322))

#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-15 16:06 -------

Comment 1 Rob Bradford 2006-08-15 16:43:03 UTC

Thanks for the bug report!

This is possibly a duplicate of #274329. Do you have the "New Mail Notification" plugin turned on?

Comment 2 Rob Bradford 2006-08-15 16:47:35 UTC

All the evidence suggests this indeed a duplicate of #274329. This has been fixed in Evolution 2.4 and later. Alternatively to work around it you can just disable the "New Mail Notification" plugin.

Once again thanks for reporting this bug!

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