Bug 577636 – crash in Evolution Mail and Calendar: open application

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 577636 - crash in Evolution Mail and Calendar: open application


Summary:	crash in Evolution Mail and Calendar: open application


Status:	RESOLVED DUPLICATE of bug 575587

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.24.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-04-01 19:05 UTC by hamador
Modified:	2009-04-01 21:05 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description hamador 2009-04-01 19:05:11 UTC

What were you doing when the application crashed?
open application


Distribution: Debian squeeze/sid
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.24.2

System: Linux 2.6.29-1-686 #1 SMP Tue Mar 24 23:05:52 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: SphereCrystal

Memory status: size: 164864000 vsize: 164864000 resident: 48553984 share: 24793088 rss: 48553984 rss_rlim: 18446744073709551615
CPU usage: start_time: 1238612618 rtime: 125 utime: 109 stime: 16 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 0xb53149a0 (LWP 31170)]
[New Thread 0xb24feb90 (LWP 31189)]
[New Thread 0xb3eeab90 (LWP 31180)]
0xb8056424 in __kernel_vsyscall ()

+ Trace 214097

Thread 1 (Thread 0xb53149a0 (LWP 31170))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 IA__g_spawn_sync
at /build/buildd-glib2.0_2.20.0-2-i386-rcJiVy/glib2.0-2.20.0/glib/gspawn.c line 382
#3 IA__g_spawn_command_line_sync
at /build/buildd-glib2.0_2.20.0-2-i386-rcJiVy/glib2.0-2.20.0/glib/gspawn.c line 694
#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 414
#7 nsProfileLock::FatalSignalHandler
at nsProfileLock.cpp line 216
#8 <signal handler called>
#9 camel_message_info_uint32
at camel-folder-summary.c line 4547
#10 ??
from /usr/lib/evolution/2.24/plugins/liborg-jylefort-mail-notification.so
#11 ??
#12 ??
#13 ??
#14 ??
#15 ??
from /usr/lib/libdbus-glib-1.so.2
#16 ??
#17 ??
#18 IA__g_type_value_table_peek
at /build/buildd-glib2.0_2.20.0-2-i386-rcJiVy/glib2.0-2.20.0/gobject/gtype.c line 3893
#19 dbus_glib_marshal_mn_evolution_server_BOOLEAN__STRING_POINTER_POINTER
from /usr/lib/evolution/2.24/plugins/liborg-jylefort-mail-notification.so
#20 ??
from /usr/lib/libdbus-glib-1.so.2
#21 ??
#22 ??
#23 ??
#24 ??
#25 ??
#0 __kernel_vsyscall



----------- .xsession-errors (8 sec old) ---------------------
RSS Plugin enabled (evolution 2.24, evolution-rss 0.1.2)
stAte:-1
Reading RSS articles...
feed Framasoft - Logiciels Libres
warning: Lowest section in /usr/lib/libicudata.so.40 is .hash at 000000b4

(gnome-terminal:31002): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
** (evolution:31170): DEBUG: mailto URL command: evolution %s
** (evolution:31170): DEBUG: mailto URL program: evolution
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
warning: Lowest section in /usr/lib/libicudata.so.40 is .hash at 000000b4
--------------------------------------------------

Comment 1 Gianluca Borello 2009-04-01 21:05:03 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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