Bug 651090 – crash in Evolution: E-Mails abgerufen

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 651090 - crash in Evolution: E-Mails abgerufen


Summary:	crash in Evolution: E-Mails abgerufen


Status:	RESOLVED DUPLICATE of bug 330728

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.30.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:	2011-05-25 20:02 UTC by helmut_priebe
Modified:	2011-05-26 01:06 UTC

See Also:
GNOME target:	---
GNOME version:	2.29/2.30

Description helmut_priebe 2011-05-25 20:02:51 UTC

What were you doing when the application crashed?
E-Mails abgerufen


Distribution: Debian 6.0.1
Gnome Release: 2.30.2 2010-11-12 (Debian)
BugBuddy Version: 2.30.0

System: Linux 2.6.32-5-686 #1 SMP Wed May 18 07:08:50 UTC 2011 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10707000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Nodoka-Aqua
Icon Theme: Gion
GTK+ Modules: gnomebreakpad, gail-gnome, gail:atk-bridge, canberra-gtk-module

Memory status: size: 241344512 vsize: 241344512 resident: 49876992 share: 25882624 rss: 49876992 rss_rlim: 18446744073709551615
CPU usage: start_time: 1306325198 rtime: 2375 utime: 2199 stime: 176 cutime:16 cstime: 9 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xa86fcb70 (LWP 3486)]
[New Thread 0xb07b4b70 (LWP 2395)]
[New Thread 0xb0fb5b70 (LWP 2394)]
0xb7710424 in __kernel_vsyscall ()

+ Trace 227252

Thread 1 (Thread 0xb5d4e770 (LWP 2393))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 IA__g_spawn_sync
at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/glib/gspawn.c line 386
#3 IA__g_spawn_command_line_sync
at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/glib/gspawn.c line 700
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 segv_redirect
at main.c line 289
#6 <signal handler called>
#7 ect_check
at gal-a11y-e-cell-text.c line 83
#8 ect_get_name
at gal-a11y-e-cell-text.c line 95
#9 atk_object_get_name
at atkobject.c line 704
#10 spi_atk_bridge_init_base
at bridge.c line 1367
#11 spi_atk_bridge_init_nil
at bridge.c line 1379
#12 spi_atk_bridge_focus_tracker
at bridge.c line 726
#13 atk_focus_tracker_notify
at atkutil.c line 200
#14 gail_focus_notify
at /build/buildd-gtk+2.0_2.20.1-2-i386-TNeM25/gtk+2.0-2.20.1/modules/other/gail/gail.c line 589
#15 gail_focus_idle_handler
at /build/buildd-gtk+2.0_2.20.1-2-i386-TNeM25/gtk+2.0-2.20.1/modules/other/gail/gail.c line 542
#16 gdk_threads_dispatch
at /build/buildd-gtk+2.0_2.20.1-2-i386-TNeM25/gtk+2.0-2.20.1/gdk/gdk.c line 512
#17 g_idle_dispatch
at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/glib/gmain.c line 4065
#18 g_main_dispatch
at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/glib/gmain.c line 1960
#19 IA__g_main_context_dispatch
at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/glib/gmain.c line 2513
#20 g_main_context_iterate
at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/glib/gmain.c line 2591
#21 IA__g_main_loop_run
at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/glib/gmain.c line 2799
#22 IA__gtk_main
at /build/buildd-gtk+2.0_2.20.1-2-i386-TNeM25/gtk+2.0-2.20.1/gtk/gtkmain.c line 1219
#23 main
at main.c line 639


	Inferior 1 [process 2393] will be detached.

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


----------- .xsession-errors (67 sec old) ---------------------
** (mail-notification:2271): WARNING **: Marianne.Priebe@pop3-1.ewetel.net: Die SASL-Authentifizierung konnte nicht gestartet werden: SASL(-4): no mechanism available: No worthy mechs found
** (mail-notification:2271): WARNING **: 24663349@pop.gmx.net: Die SASL-Authentifizierung konnte nicht gestartet werden: SASL(-4): no mechanism available: No worthy mechs found
** (mail-notification:2271): WARNING **: helmut_priebe@ewetel.net: Die SASL-Authentifizierung konnte nicht gestartet werden: SASL(-4): no mechanism available: No worthy mechs found
** (mail-notification:2271): WARNING **: marianne_und_helmut@.ewetel.net: Die SASL-Authentifizierung konnte nicht gestartet werden: SASL(-4): no mechanism available: No worthy mechs found
** (mail-notification:2271): WARNING **: 24682625@pop.gmx.net: Die SASL-Authentifizierung konnte nicht gestartet werden: SASL(-4): no mechanism available: No worthy mechs found
** (mail-notification:2271): WARNING **: 38229188@pop.gmx.net: Die SASL-Authentifizierung konnte nicht gestartet werden: SASL(-4): no mechanism available: No worthy mechs found
** (mail-notification:2271): WARNING **: Marianne.Priebe@pop3-1.ewetel.net: Die SASL-Authentifizierung konnte nicht gestartet werden: SASL(-4): no mechanism available: No worthy mechs found
** (mail-notification:2271): WARNING **: 24663349@pop.gmx.net: Die SASL-Authentifizierung konnte nicht gestartet werden: SASL(-4): no mechanism available: No worthy mechs found
--------------------------------------------------

Comment 1 Fabio Durán Verdugo 2011-05-26 01:06:36 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 bug 330728 ***