Bug 514721 – crash in Evolution: Desactivando una cuenta

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 514721 - crash in Evolution: Desactivando una cuenta


Summary:	crash in Evolution: Desactivando una cuenta


Status:	RESOLVED DUPLICATE of bug 324168

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.12.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-02-06 11:04 UTC by aalvarez
Modified:	2008-02-08 04:18 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description aalvarez 2008-02-06 11:04:55 UTC

What were you doing when the application crashed?
Desactivando una cuenta


Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.23.14 #2 SMP PREEMPT Wed Jan 23 12:18:56 CET 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 148180992 vsize: 148180992 resident: 71901184 share: 20205568 rss: 71901184 rss_rlim: 4294967295
CPU usage: start_time: 1202295578 rtime: 465 utime: 431 stime: 34 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb699b8c0 (LWP 4152)]
[New Thread 0xb33dbb90 (LWP 4162)]
[New Thread 0xb3bf1b90 (LWP 4161)]
[New Thread 0xb453bb90 (LWP 4159)]
[New Thread 0xb55ffb90 (LWP 4156)]
[New Thread 0xb5f8cb90 (LWP 4154)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 188270

Thread 1 (Thread 0xb699b8c0 (LWP 4152))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 ??
#6 ??
#7 ??
#8 ??
#9 ??
from /lib/i686/cmov/libc.so.6
#10 ??
from /usr/lib/libcamel-provider-1.2.so.10
#11 ??
#12 ??
#13 <signal handler called>
#14 camel_folder_summary_content_info_free
from /usr/lib/libcamel-provider-1.2.so.10
#15 camel_message_info_free
from /usr/lib/libcamel-provider-1.2.so.10
#16 ??
from /usr/lib/libcamel-provider-1.2.so.10
#17 ??
#18 free
from /lib/i686/cmov/libc.so.6
#19 camel_message_info_free
from /usr/lib/libcamel-provider-1.2.so.10
#20 camel_folder_summary_clear
from /usr/lib/libcamel-provider-1.2.so.10
#21 ??
from /usr/lib/libcamel-provider-1.2.so.10
#22 ??
#23 ??
from /usr/lib/libcamel-provider-1.2.so.10
#24 ??
from /usr/lib/libcamel-provider-1.2.so.10
#25 ??
from /usr/lib/libcamel-1.2.so.10
#26 ??
#27 ??
#28 ??
#29 camel_object_unref
from /usr/lib/libcamel-1.2.so.10
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
(evolution:4844): evolution-mail-WARNING **: Cannot activate OAFIID:GNOME_Spell_Dictionary:0.3
(evolution:4844): camel-WARNING **: Trying to check junk data is OBJECT 'CamelObject'
(evolution:4844): camel-CRITICAL **: camel_object_cast: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed
CalDAV Eplugin starting up ...
get aalvarez imap://aalvarez@correo.fotoprix.com/
Find Items 0
(evolution:4152): evolution-mail-WARNING **: Cannot activate OAFIID:GNOME_Spell_Dictionary:0.3
(evolution:4152): camel-WARNING **: Trying to check junk data is OBJECT 'CamelObject'
(evolution:4152): camel-CRITICAL **: camel_object_cast: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed
--------------------------------------------------

Comment 1 Akhil Laddha 2008-02-08 04:18:21 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 324168 ***