Bug 616511 – crash in Evolution Mail: nothing

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 616511 - crash in Evolution Mail: nothing


Summary:	crash in Evolution Mail: nothing


Status:	RESOLVED DUPLICATE of bug 615816

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2010-04-22 12:58 UTC by aalarcon
Modified:	2010-04-22 13:35 UTC

See Also:
GNOME target:	---
GNOME version:	2.27/2.28

Description aalarcon 2010-04-22 12:58:27 UTC

What were you doing when the application crashed?
nothing


Distribution: Debian squeeze/sid
Gnome Release: 2.28.2 2009-12-18 (Debian)
BugBuddy Version: 2.30.0

System: Linux 2.6.32-trunk-686 #1 SMP Sun Jan 10 06:32:16 UTC 2010 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10706901
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome-alternative
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 247648256 vsize: 247648256 resident: 66985984 share: 24510464 rss: 66985984 rss_rlim: 18446744073709551615
CPU usage: start_time: 1271937947 rtime: 8084 utime: 7494 stime: 590 cutime:398 cstime: 160 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xac3ccb70 (LWP 3885)]
[New Thread 0xb23fcb70 (LWP 3884)]
[New Thread 0xafbf7b70 (LWP 3846)]
[New Thread 0xb03f8b70 (LWP 3845)]
[New Thread 0xb476eb70 (LWP 3835)]
[New Thread 0xb4f6fb70 (LWP 3831)]
0xb7717424 in __kernel_vsyscall ()

+ Trace 221510

Thread 1 (Thread 0xb59c6760 (LWP 3797))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 IA__g_spawn_sync
at /build/buildd-glib2.0_2.24.0-1-i386-o5zIuQ/glib2.0-2.24.0/glib/gspawn.c line 386
#3 IA__g_spawn_command_line_sync
at /build/buildd-glib2.0_2.24.0-1-i386-o5zIuQ/glib2.0-2.24.0/glib/gspawn.c line 700
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 segv_redirect
at main.c line 432
#6 <signal handler called>
#7 ??
from /lib/libdbus-1.so.3
#8 ??
from /lib/libdbus-1.so.3
#9 ??
from /lib/libdbus-1.so.3
#10 dbus_timeout_handle
from /lib/libdbus-1.so.3
#11 ??
from /usr/lib/libgnome-keyring.so.0
#12 g_timeout_dispatch
at /build/buildd-glib2.0_2.24.0-1-i386-o5zIuQ/glib2.0-2.24.0/glib/gmain.c line 3396
#13 g_main_dispatch
at /build/buildd-glib2.0_2.24.0-1-i386-o5zIuQ/glib2.0-2.24.0/glib/gmain.c line 1960
#14 IA__g_main_context_dispatch
at /build/buildd-glib2.0_2.24.0-1-i386-o5zIuQ/glib2.0-2.24.0/glib/gmain.c line 2513
#15 g_main_context_iterate
at /build/buildd-glib2.0_2.24.0-1-i386-o5zIuQ/glib2.0-2.24.0/glib/gmain.c line 2591
#16 IA__g_main_loop_run
at /build/buildd-glib2.0_2.24.0-1-i386-o5zIuQ/glib2.0-2.24.0/glib/gmain.c line 2799
#17 bonobo_main
from /usr/lib/libbonobo-2.so.0
#18 main
at main.c line 732


	Inferior 1 [process 3797] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


---- Critical and fatal warnings logged during execution ----

** evolution **: file gkr-operation.c: line 350 (gkr_operation_request): should not be reached 


----------- .xsession-errors (32 sec old) ---------------------
refreshing...
ESSID : FRAX
ESSID : MISSY
ESSID : mymdiseC1os
ESSID : Renbal
ESSID : Arquitectura
ESSID : House
ESSID : Casa
ESSID : reyes_vallejo
ESSID : knowledge
ESSID : Canessa
(exe:5656): Gdk-WARNING **: XID collision, trouble ahead
** (evolution:3797): CRITICAL **: file gkr-operation.c: line 350 (gkr_operation_request): should not be reached
--------------------------------------------------

Comment 1 André Klapper 2010-04-22 13:35:39 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 bug 615816 ***