Bug 588380 – crash in Evolution Mail and Calendar: Started Evolution

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 588380 - crash in Evolution Mail and Calendar: Started Evolution


Summary:	crash in Evolution Mail and Calendar: Started Evolution


Status:	RESOLVED DUPLICATE of bug 564745

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.26.x (obsolete)
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2009-07-12 16:17 UTC by uwe
Modified:	2009-07-12 20:17 UTC

See Also:
GNOME target:	---
GNOME version:	2.25/2.26

Description uwe 2009-07-12 16:17:11 UTC

What were you doing when the application crashed?
Started Evolution


Distribution: Fedora release 11 (Leonidas)
Gnome Release: 2.26.2 2009-06-01 (Red Hat, Inc)
BugBuddy Version: 2.26.0

System: Linux 2.6.29.5-191.fc11.i686.PAE #1 SMP Tue Jun 16 23:19:53 EDT 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10601901
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
GTK+ Modules: canberra-gtk-module, pk-gtk-module, gnomebreakpad

Memory status: size: 371175424 vsize: 371175424 resident: 66232320 share: 28852224 rss: 66232320 rss_rlim: 18446744073709551615
CPU usage: start_time: 1247415258 rtime: 630 utime: 498 stime: 132 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb24feb70 (LWP 12682)]
[New Thread 0xa70feb70 (LWP 12634)]
[New Thread 0xa64ffb70 (LWP 12620)]
[New Thread 0xad559b70 (LWP 12617)]
[New Thread 0xac157b70 (LWP 12608)]
[New Thread 0xacb58b70 (LWP 12607)]
[New Thread 0xb06fbb70 (LWP 12601)]
[New Thread 0xb1afdb70 (LWP 12599)]
[New Thread 0xb3affb70 (LWP 12596)]
[New Thread 0xb467cb70 (LWP 12595)]
[New Thread 0xb507db70 (LWP 12594)]
[New Thread 0xb7d76b70 (LWP 12593)]
0x00591424 in __kernel_vsyscall ()

+ Trace 216393

Thread 1 (Thread 0xb8078770 (LWP 12583))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 g_spawn_sync
from /lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#6 segv_redirect
at main.c line 426
#7 nsProfileLock::FatalSignalHandler
at nsProfileLock.cpp line 216
#8 <signal handler called>
#9 camel_message_info_uint32
at camel-folder-summary.c line 4584
#10 ??
from /usr/lib/evolution/2.26/plugins/liborg-jylefort-mail-notification.so
#11 dbus_glib_marshal_mn_evolution_server_BOOLEAN__STRING_POINTER_POINTER
from /usr/lib/evolution/2.26/plugins/liborg-jylefort-mail-notification.so
#12 ??
from /usr/lib/libdbus-glib-1.so.2
#13 ??
from /usr/lib/libdbus-glib-1.so.2
#14 ??
from /lib/libdbus-1.so.3
#15 dbus_connection_dispatch
from /lib/libdbus-1.so.3
#16 ??
from /usr/lib/libdbus-glib-1.so.2
#17 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#18 ??
from /lib/libglib-2.0.so.0
#19 g_main_loop_run
from /lib/libglib-2.0.so.0
#20 bonobo_main
from /usr/lib/libbonobo-2.so.0
#21 main
at main.c line 704



----------- .xsession-errors (8 sec old) ---------------------
warning: .dynamic section for "/lib/libasound.so.2" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/lib/libwrap.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libasyncns.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libgdbm.so.2" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------

Comment 1 Fabio Durán Verdugo 2009-07-12 20:17:12 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.


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