Bug 510370 – crash in Evolution: I was changing the activ...

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 510370 - crash in Evolution: I was changing the activ...


Summary:	crash in Evolution: I was changing the activ...


Status:	RESOLVED DUPLICATE of bug 523463

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-01-18 11:18 UTC by toni
Modified:	2009-02-20 03:38 UTC

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

Description toni 2008-01-18 11:18:26 UTC

What were you doing when the application crashed?
I was changing the activity of a count in preferences.


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

System: Linux 2.6.23-1-686 #1 SMP Fri Dec 21 13:57:07 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Amaranth
Icon Theme: gnome

Memory status: size: 238505984 vsize: 238505984 resident: 55537664 share: 19488768 rss: 55537664 rss_rlim: 4294967295
CPU usage: start_time: 1200651505 rtime: 7391 utime: 6327 stime: 1064 cutime:66 cstime: 128 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb67ed6b0 (LWP 4289)]
[New Thread 0xacbfcb90 (LWP 5037)]
[New Thread 0xae3ffb90 (LWP 4423)]
[New Thread 0xaf5f6b90 (LWP 4367)]
[New Thread 0xb05f8b90 (LWP 4362)]
[New Thread 0xafdf7b90 (LWP 4358)]
[New Thread 0xb0df9b90 (LWP 4343)]
[New Thread 0xb15fab90 (LWP 4342)]
[New Thread 0xb1dfbb90 (LWP 4341)]
[New Thread 0xb25fcb90 (LWP 4340)]
[New Thread 0xb35feb90 (LWP 4338)]
[New Thread 0xb3dffb90 (LWP 4337)]
[New Thread 0xb4790b90 (LWP 4336)]
[New Thread 0xb4fb0b90 (LWP 4334)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 185809

Thread 5 (Thread 0xb05f8b90 (LWP 4362))

#0 __kernel_vsyscall
#1 __lll_lock_wait
from /lib/i686/cmov/libpthread.so.0
#2 _L_lock_95
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 422
#5 <signal handler called>
#6 camel_folder_summary_content_info_free
at camel-folder-summary.c line 1121
#7 camel_message_info_free
at camel-folder-summary.c line 2807
#8 vee_message_info_free
at camel-vee-summary.c line 45
#9 camel_message_info_free
at camel-folder-summary.c line 2810
#10 vee_rebuild_folder
at camel-vee-folder.c line 1010
#11 vee_add_folder
at camel-vee-folder.c line 1606
#12 camel_vee_folder_add_folder
at camel-vee-folder.c line 224
#13 vfolder_adduri_do
at mail-vfolder.c line 280
#14 mail_msg_received
at mail-mt.c line 582
#15 thread_dispatch
at e-msgport.c line 1005
#16 start_thread
from /lib/i686/cmov/libpthread.so.0
#17 clone
from /lib/i686/cmov/libc.so.6



----------- .xsession-errors (233 sec old) ---------------------
get bankarota@moviments.net pop://bankarota%40moviments.net@mail.moviments.net/
Find Items 0
get insershow@moviments.net pop://insershow%40moviments.net@mail.moviments.net/
Find Items 0
get toni pop://toni@mail.sindominio.net/
Find Items 0
** (nm-applet:4006): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.18" is not allowed to own the service "org.freedesktop.Networ
get toni pop://toni@mail.pangea.org/
Find Items 0
get toni pop://toni@mail.pangea.org/
Find Items 0
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Akhil Laddha 2009-02-20 03:38:38 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 523463 ***