Bug 577148 – crash in Evolution Mail and Calendar: I have just opened evolu...

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 577148 - crash in Evolution Mail and Calendar: I have just opened evolu...


Summary:	crash in Evolution Mail and Calendar: I have just opened evolu...


Status:	RESOLVED DUPLICATE of bug 523463

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:	2009-03-29 01:43 UTC by juan
Modified:	2009-04-06 06:59 UTC

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

Description juan 2009-03-29 01:43:32 UTC

What were you doing when the application crashed?
I have just opened evolution!!!!


Distribution: Debian 5.0
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-686 #1 SMP Sat Nov 8 19:00:26 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mac4Lin_GTK_v1.0_RC
Icon Theme: Mac4Lin_Icons_v1.0_RC

Memory status: size: 108433408 vsize: 108433408 resident: 25575424 share: 18440192 rss: 25575424 rss_rlim: 4294967295
CPU usage: start_time: 1238290977 rtime: 64 utime: 58 stime: 6 cutime:3 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb660b6d0 (LWP 1688)]
[New Thread 0xb2577b90 (LWP 1743)]
[New Thread 0xb3efdb90 (LWP 1719)]
[New Thread 0xb4effb90 (LWP 1714)]
[New Thread 0xb5892b90 (LWP 1712)]
0xb7f87424 in __kernel_vsyscall ()

+ Trace 213955

Thread 1 (Thread 0xb660b6d0 (LWP 1688))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 IA__g_spawn_sync
at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/glib/gspawn.c line 374
#3 IA__g_spawn_command_line_sync
at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/glib/gspawn.c line 682
#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 519
#7 <signal handler called>
#8 IA__g_main_context_check
at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/glib/gmain.c line 2491
#9 g_main_context_iterate
at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/glib/gmain.c line 2642
#10 IA__g_main_loop_run
at /build/buildd-glib2.0_2.16.6-1+lenny1-i386-HI4TzI/glib2.0-2.16.6/glib/gmain.c line 2853
#11 bonobo_main
from /usr/lib/libbonobo-2.so.0
#12 main
at main.c line 793
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
(evolution:1688): e-spinner.c-WARNING **: Cannot extract frame (108, 0) from the grid
(evolution:1688): e-spinner.c-WARNING **: Cannot extract frame (144, 0) from the grid
(evolution:1688): e-spinner.c-WARNING **: Cannot extract frame (180, 0) from the grid
(evolution:1688): e-spinner.c-WARNING **: Cannot extract frame (216, 0) from the grid
(evolution:1688): e-spinner.c-WARNING **: Cannot extract frame (252, 0) from the grid
--------------------------------------------------

Comment 1 Akhil Laddha 2009-04-06 06:59:06 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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