Bug 546581 – crash in Evolution Mail and Calendar:

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


Summary:	crash in Evolution Mail and Calendar:


Status:	RESOLVED DUPLICATE of bug 541872

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.22.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:	2008-08-06 12:54 UTC by ribadiscibadisci
Modified:	2008-08-07 01:26 UTC

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

Description ribadiscibadisci 2008-08-06 12:54:39 UTC

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-06-30 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-2-amd64 #1 SMP Mon Jul 14 11:05:23 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Murrine Brave Dark
Icon Theme: Mist

Memory status: size: 606683136 vsize: 606683136 resident: 50065408 share: 29978624 rss: 50065408 rss_rlim: 18446744073709551615
CPU usage: start_time: 1218006035 rtime: 1758 utime: 1436 stime: 322 cutime:1 cstime: 6 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7ffdd9893790 (LWP 5037)]
[New Thread 0x4035e950 (LWP 5114)]
[New Thread 0x40d61950 (LWP 5113)]
(no debugging symbols found)
0x00007ffdd5175edf in waitpid () from /lib/libpthread.so.0

+ Trace 204716

Thread 1 (Thread 0x7ffdd9893790 (LWP 5037))

#0 waitpid
from /lib/libpthread.so.0
#1 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#2 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#3 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#4 ??
from /usr/lib/xulrunner-1.9/libxul.so
#5 <signal handler called>
#6 ??
#7 ??
from /usr/lib/xulrunner-1.9/libxul.so
#8 ??
from /usr/lib/xulrunner-1.9/libxul.so
#9 ??
from /usr/lib/xulrunner-1.9/libxul.so
#10 ??
from /usr/lib/xulrunner-1.9/libxul.so
#11 ??
from /usr/lib/xulrunner-1.9/libxul.so
#12 ??
from /usr/lib/xulrunner-1.9/libxul.so
#13 XRE_TermEmbedding
from /usr/lib/xulrunner-1.9/libxul.so
#14 ??
from /usr/lib/xulrunner-1.9/libxul.so
#15 gecko_shutdown
from /usr/lib/evolution/2.22/plugins/liborg-gnome-evolution-rss.so
#16 exit
from /lib/libc.so.6
#17 __libc_start_main
from /lib/libc.so.6
#18 ??
#19 ??
#20 ??
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors ---------------------
scale = 1
new dimensions = (48,48)
we need to scale up
scale = 1
RSS: cleaning all remaining sessions ...done
(bug-buddy:22427): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(bug-buddy:22427): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(bug-buddy:22427): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(bug-buddy:22427): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(bug-buddy:22427): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
--------------------------------------------------

Comment 1 André Klapper 2008-08-07 01:26:28 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 541872 ***