Bug 519016 – crash in Evolution Mail: disabling an imap accoun...

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 519016 - crash in Evolution Mail: disabling an imap accoun...


Summary:	crash in Evolution Mail: disabling an imap accoun...


Status:	RESOLVED DUPLICATE of bug 324168

Product:	evolution
Classification:	Applications
Component:	general
Version:	2.12.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Shell Maintainers Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-02-27 09:39 UTC by adrinux
Modified:	2008-02-28 06:12 UTC

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

Description adrinux 2008-02-27 09:39:00 UTC

What were you doing when the application crashed?
disabling an imap account


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

System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: SmoothGNOME-Red
Icon Theme: Neu

Memory status: size: 150593536 vsize: 150593536 resident: 39829504 share: 22425600 rss: 39829504 rss_rlim: 4294967295
CPU usage: start_time: 1204102720 rtime: 2922 utime: 2610 stime: 312 cutime:3030 cstime: 360 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 0xb677c8e0 (LWP 6050)]
[New Thread 0xb22aeb90 (LWP 6223)]
[New Thread 0xb2abcb90 (LWP 6188)]
[New Thread 0xb3335b90 (LWP 6179)]
[New Thread 0xb3deab90 (LWP 6159)]
[New Thread 0xb4decb90 (LWP 6149)]
[New Thread 0xb55edb90 (LWP 6146)]
[New Thread 0xb5e0db90 (LWP 6144)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 190593

Thread 1 (Thread 0xb677c8e0 (LWP 6050))

#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 ??
from /usr/lib/libglib-2.0.so.0
#8 ??
from /lib/i686/cmov/libc.so.6
#9 ??
#10 ??
from /usr/lib/libcamel-provider-1.2.so.10
#11 ??
#12 ??
#13 <signal handler called>
#14 camel_message_info_free
from /usr/lib/libcamel-provider-1.2.so.10
#15 ??
from /usr/lib/libcamel-provider-1.2.so.10
#16 ??
#17 free
from /lib/i686/cmov/libc.so.6
#18 camel_message_info_free
from /usr/lib/libcamel-provider-1.2.so.10
#19 camel_folder_summary_clear
from /usr/lib/libcamel-provider-1.2.so.10
#20 ??
from /usr/lib/libcamel-provider-1.2.so.10
#21 ??
#22 ??
from /usr/lib/libcamel-provider-1.2.so.10
#23 ??
from /usr/lib/libcamel-provider-1.2.so.10
#24 ??
from /usr/lib/libcamel-1.2.so.10
#25 ??
#26 ??
#27 ??
#28 camel_object_unref
from /usr/lib/libcamel-1.2.so.10
#0 __kernel_vsyscall



----------- .xsession-errors (9 sec old) ---------------------
report junk?? Curso Prático de Licenciamento Ambiental
report junk?? Carnaval de Ovar 2008
report junk?? SHU APRESENTA...
report junk?? Feira de objectos de Design e Decoracao - Mercado Ferreira Borges
report junk?? E-Learning
camel-Message: --
camel-Message: --
BBDB spinning up...
(evolution:6050): evolution-mail-WARNING **: Cannot activate OAFIID:GNOME_Spell_Dictionary:0.3
--------------------------------------------------

Comment 1 Akhil Laddha 2008-02-28 06:12:54 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 ***