Bug 504816 – crash in Tasks: Nothing. It happend duri...

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 504816 - crash in Tasks: Nothing. It happend duri...


Summary:	crash in Tasks: Nothing. It happend duri...


Status:	RESOLVED DUPLICATE of bug 447591

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-calendar-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-12-21 07:31 UTC by psz
Modified:	2007-12-21 10:43 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description psz 2007-12-21 07:31:48 UTC

What were you doing when the application crashed?
Nothing. It happend during the night when I was out of office.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 114208768 vsize: 114208768 resident: 25567232 share: 15073280 rss: 25567232 rss_rlim: 4294967295
CPU usage: start_time: 1198079715 rtime: 2375 utime: 2017 stime: 358 cutime:67 cstime: 53 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208699168 (LWP 29074)]
[New Thread -1231914096 (LWP 6368)]
[New Thread -1266123888 (LWP 6366)]
[New Thread -1254098032 (LWP 29087)]
[New Thread -1242403952 (LWP 29085)]
(no debugging symbols found)
0x0040b402 in __kernel_vsyscall ()

+ Trace 182511

Thread 3 (Thread -1266123888 (LWP 6366))

#0 __kernel_vsyscall
#1 __lll_mutex_lock_wait
from /lib/libpthread.so.0
#2 _L_mutex_lock_79
from /lib/libpthread.so.0
#3 pthread_mutex_lock
from /lib/libpthread.so.0
#4 ??
#5 <signal handler called>
#6 pthread_mutex_lock
from /lib/libpthread.so.0
#7 camel_message_info_free
from /usr/lib/libcamel-provider-1.2.so.10
#8 ??
from /usr/lib/libcamel-provider-1.2.so.10
#9 camel_message_info_free
from /usr/lib/libcamel-provider-1.2.so.10
#10 camel_folder_summary_clear
from /usr/lib/libcamel-provider-1.2.so.10
#11 ??
from /usr/lib/libcamel-provider-1.2.so.10
#12 camel_object_unref
from /usr/lib/libcamel-1.2.so.10
#13 ??
from /usr/lib/libcamel-provider-1.2.so.10
#14 camel_object_unref
from /usr/lib/libcamel-1.2.so.10
#15 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#16 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#17 ??
from /lib/libglib-2.0.so.0
#18 ??
from /lib/libglib-2.0.so.0
#19 start_thread
from /lib/libpthread.so.0
#20 clone
from /lib/libc.so.6

Comment 1 André Klapper 2007-12-21 10:43:37 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 447591 ***