Bug 511475 – 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 511475 - crash in Tasks:


Summary:	crash in Tasks:


Status:	RESOLVED DUPLICATE of bug 445309

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.10.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-23 08:54 UTC by truonghuutram
Modified:	2008-01-24 15:15 UTC

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

Description truonghuutram 2008-01-23 08:54:51 UTC

Version: 2.10

What were you doing when the application crashed?



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

System: Linux 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 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: 128348160 vsize: 128348160 resident: 44486656 share: 34258944 rss: 44486656 rss_rlim: 4294967295
CPU usage: start_time: 1201078011 rtime: 821 utime: 773 stime: 48 cutime:1 cstime: 2 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 -1209018656 (LWP 4406)]
[New Thread -1229145200 (LWP 4640)]
[New Thread -1262494832 (LWP 4443)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 186453

Thread 2 (Thread -1229145200 (LWP 4640))

#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 PR_Lock
from /usr/lib/libnspr4.so
#8 ??
from /usr/lib/libnspr4.so
#9 __nptl_deallocate_tsd
from /lib/libpthread.so.0
#10 start_thread
from /lib/libpthread.so.0
#11 clone
from /lib/libc.so.6



----------- .xsession-errors (246 sec old) ---------------------
(gnome-terminal:3369): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
CalDAV Eplugin starting up ...
** (evolution:4166): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:4166): DEBUG: mailto URL program: evolution
CalDAV Eplugin starting up ...
** (evolution:4324): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:4324): DEBUG: mailto URL program: evolution
adding certinfo Nicolas Niclausse <nicolas.niclausse@sophia.inria.fr>
adding certinfo Nicolas Niclausse <nicolas.niclausse@sophia.inria.fr>
adding certinfo Nicolas Niclausse <nicolas.niclausse@sophia.inria.fr>
CalDAV Eplugin starting up ...
** (evolution:4406): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:4406): DEBUG: mailto URL program: evolution
camel-Message: --
camel-Message: --
--------------------------------------------------

Comment 1 Tobias Mueller 2008-01-24 15:15:08 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 445309 ***