Bug 589220 – crash in Evolution Mail and Calendar: Started Evolution in Fed...

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


Summary:	crash in Evolution Mail and Calendar: Started Evolution in Fed...


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-21 08:36 UTC by uwe
Modified:	2009-07-21 16:52 UTC

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

Description uwe 2009-07-21 08:36:17 UTC

What were you doing when the application crashed?
Started Evolution in Fedora 11


Distribution: Fedora release 11 (Leonidas)
Gnome Release: 2.26.3 2009-07-07 (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: 370356224 vsize: 370356224 resident: 65290240 share: 28798976 rss: 65290240 rss_rlim: 18446744073709551615
CPU usage: start_time: 1248162715 rtime: 951 utime: 694 stime: 257 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 3563)]
[New Thread 0xafcfab70 (LWP 3490)]
[New Thread 0xa76c8b70 (LWP 3473)]
[New Thread 0xaf2f9b70 (LWP 3470)]
[New Thread 0xa6cc7b70 (LWP 3332)]
[New Thread 0xa80c9b70 (LWP 3264)]
[New Thread 0xacb57b70 (LWP 3251)]
[New Thread 0xad558b70 (LWP 3250)]
[New Thread 0xb06fbb70 (LWP 3239)]
[New Thread 0xb1afdb70 (LWP 3237)]
[New Thread 0xb3affb70 (LWP 3234)]
[New Thread 0xb469cb70 (LWP 3217)]
[New Thread 0xb509db70 (LWP 3215)]
[New Thread 0xb7cafb70 (LWP 3212)]
0x00871424 in __kernel_vsyscall ()

+ Trace 216553

Thread 1 (Thread 0xb7fb1770 (LWP 3178))

#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 4598
#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 ---------------------
warning: .dynamic section for "/usr/lib/libicui18n.so.40" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libicuuc.so.40" 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
2009-07-21 09:54:43.029::INFO:  jetty-6.1.11
2009-07-21 09:54:43.223::INFO:  Started SocketConnector@127.0.0.1:8501
2009-07-21 09:54:43.223::INFO:  Started SocketConnector@127.0.0.1:8601
--------------------------------------------------

Comment 1 Fabio Durán Verdugo 2009-07-21 16:52:27 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 ***