Bug 622603 – crash in Evolution: nada

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 622603 - crash in Evolution: nada


Summary:	crash in Evolution: nada


Status:	RESOLVED DUPLICATE of bug 616512

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:	2010-06-24 13:58 UTC by timo
Modified:	2010-06-24 14:12 UTC

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

Description timo 2010-06-24 13:58:29 UTC

What were you doing when the application crashed?
nada


Distribution: Debian squeeze/sid
Gnome Release: 2.30.0 2010-04-26 (Debian)
BugBuddy Version: 2.30.0

System: Linux 2.6.34-0.slh.9-sidux-686 #1 SMP PREEMPT Sat Jun 12 23:39:12 UTC 2010 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10707000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome-alternative
GTK+ Modules: gnomebreakpad

Memory status: size: 244490240 vsize: 244490240 resident: 39645184 share: 24965120 rss: 39645184 rss_rlim: 18446744073709551615
CPU usage: start_time: 1277382620 rtime: 2502 utime: 2348 stime: 154 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 0xabb4bb70 (LWP 8704)]
[New Thread 0xb0322b70 (LWP 8703)]
[New Thread 0xad34eb70 (LWP 8701)]
[New Thread 0xadb4fb70 (LWP 8700)]
[New Thread 0xb0d22b70 (LWP 8699)]
[New Thread 0xae350b70 (LWP 8697)]
[New Thread 0xab34ab70 (LWP 8696)]
[New Thread 0xacb4db70 (LWP 8695)]
[New Thread 0xac34cb70 (LWP 8694)]
[New Thread 0xaeb51b70 (LWP 7257)]
[New Thread 0xaf352b70 (LWP 7256)]
[New Thread 0xb4e2cb70 (LWP 7251)]
[New Thread 0xb562db70 (LWP 7248)]
0xb7715424 in __kernel_vsyscall ()

+ Trace 222553

Thread 9 (Thread 0xacb4db70 (LWP 8695))

#0 __kernel_vsyscall
#1 __lll_lock_wait
from /lib/i686/cmov/libpthread.so.0
#2 _L_lock_748
from /lib/i686/cmov/libpthread.so.0
#3 pthread_mutex_lock
from /lib/i686/cmov/libpthread.so.0
#4 segv_redirect
at main.c line 288
#5 <signal handler called>
#6 slab_allocator_alloc_chunk
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gslice.c line 1070
#7 magazine_cache_pop_magazine
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gslice.c line 678
#8 thread_memory_magazine1_reload
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gslice.c line 748
#9 IA__g_slice_alloc
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gslice.c line 825
#10 IA__g_slice_alloc0
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gslice.c line 845
#11 ??
from /usr/lib/libgnome-keyring.so.0
#12 gnome_keyring_is_available
from /usr/lib/libgnome-keyring.so.0
#13 e_passwords_init
at e-passwords.c line 1279
#14 ep_msg_new
at e-passwords.c line 486
#15 e_passwords_get_password
at e-passwords.c line 1441
#16 get_password
at mail-session.c line 201
#17 camel_session_get_password
at camel-session.c line 381
#18 pop3_try_authenticate
at camel-pop3-store.c line 516
#19 pop3_connect
at camel-pop3-store.c line 646
#20 camel_service_connect
at camel-service.c line 364
#21 camel_session_get_service_connected
at camel-session.c line 278
#22 mail_tool_get_inbox
at mail-tools.c line 56
#23 fetch_mail_exec
at mail-ops.c line 287
#24 mail_msg_proxy
at mail-mt.c line 471
#25 g_thread_pool_thread_proxy
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gthreadpool.c line 315
#26 g_thread_create_proxy
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gthread.c line 1893
#27 start_thread
from /lib/i686/cmov/libpthread.so.0
#28 clone
from /lib/i686/cmov/libc.so.6


	Inferior 1 [process 7246] 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 
** evolution **: file gkr-operation.c: line 350 (gkr_operation_request): should not be reached 


----------- .xsession-errors (1217 sec old) ---------------------
Finden eines Rechners gescheitert: iera.de: Der Name oder der Dienst ist nicht bekannt
evolution-mail-Message: Error occurred while existing dialogue active:
Finden eines Rechners gescheitert: cn2481153.pop.coolnic.de: Der Name oder der Dienst ist nicht bekannt
evolution-mail-Message: Error occurred while existing dialogue active:
Finden eines Rechners gescheitert: mail.zih.tu-dresden.de: Der Name oder der Dienst ist nicht bekannt
evolution-mail-Message: Error occurred while existing dialogue active:
Finden eines Rechners gescheitert: cn2481153.pop.coolnic.de: Der Name oder der Dienst ist nicht bekannt
evolution-mail-Message: Error occurred while existing dialogue active:
Finden eines Rechners gescheitert: iera.de: Der Name oder der Dienst ist nicht bekannt
evolution-mail-Message: Error occurred while existing dialogue active:
Finden eines Rechners gescheitert: mail.zih.tu-dresden.de: Der Name oder der Dienst ist nicht bekannt
** (evolution:7246): CRITICAL **: file gkr-operation.c: line 350 (gkr_operation_request): should not be reached
** (evolution:7246): CRITICAL **: file gkr-operation.c: line 350 (gkr_operation_request): should not be reached
--------------------------------------------------

Comment 1 Akhil Laddha 2010-06-24 14:12:52 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 616512 ***