Bug 477629 – crash in Tasks:

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 477629 - crash in Tasks:


Summary:	crash in Tasks:


Status:	RESOLVED DUPLICATE of bug 441638

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-09-17 02:00 UTC by michael
Modified:	2007-09-26 18:39 UTC

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

Description michael 2007-09-17 02:00:20 UTC

Version: 2.10

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 323280896 vsize: 323280896 resident: 112365568 share: 92737536 rss: 112365568 rss_rlim: 4294967295
CPU usage: start_time: 1189979380 rtime: 2288 utime: 2070 stime: 218 cutime:40 cstime: 26 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 -1209222416 (LWP 2997)]
[New Thread -1509594224 (LWP 5766)]
[New Thread -1283744880 (LWP 4863)]
[New Thread -1407763568 (LWP 4861)]
[New Thread -1418646640 (LWP 4857)]
[New Thread -1298240624 (LWP 3835)]
[New Thread -1330103408 (LWP 3322)]
[New Thread -1319220336 (LWP 3063)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 163437

Thread 4 (Thread -1407763568 (LWP 4861))

#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 ??
from /lib/libglib-2.0.so.0
#7 ??
from /lib/libglib-2.0.so.0
#8 ??
from /lib/libglib-2.0.so.0
#9 g_slice_free_chain_with_offset
from /lib/libglib-2.0.so.0
#10 g_slist_free
from /lib/libglib-2.0.so.0
#11 g_strsplit
from /lib/libglib-2.0.so.0
#12 camel_uid_cache_new
from /usr/lib/libcamel-provider-1.2.so.10
#13 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#14 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#15 ??
from /lib/libglib-2.0.so.0
#16 ??
from /lib/libglib-2.0.so.0
#17 start_thread
from /lib/libpthread.so.0
#18 clone
from /lib/libc.so.6



----------- .xsession-errors (7 sec old) ---------------------
warning: .dynamic section for "/usr/lib/evolution/2.10/libetable.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/evolution/2.10/libevolution-widgets-a11y.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/evolution/2.10/libevolution-a11y.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/evolution/2.10/libeutil.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------

Comment 1 Tobias Mueller 2007-09-26 18:39:10 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 441638 ***