Bug 516551 – 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 516551 - 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-02-14 21:39 UTC by gromig
Modified:	2008-02-14 23:18 UTC

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

Description gromig 2008-02-14 21:39:48 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.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Crux

Memory status: size: 140488704 vsize: 140488704 resident: 54984704 share: 27942912 rss: 54984704 rss_rlim: 4294967295
CPU usage: start_time: 1202995010 rtime: 2141 utime: 1985 stime: 156 cutime:1 cstime: 1 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 -1208584480 (LWP 28352)]
[New Thread -1250976880 (LWP 30471)]
[New Thread -1229333616 (LWP 29260)]
[New Thread -1250710640 (LWP 28567)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 189236

Thread 2 (Thread -1250976880 (LWP 30471))

#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 (9404 sec old) ---------------------
--> file:///home/gdromig
(nautilus:3299): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
BBDB spinning up...
(evolution:2951): e-data-server-DEBUG: Loading categories from "/home/gdromig/.evolution/categories.xml"
(evolution:2951): e-data-server-DEBUG: Loaded 29 categories
CalDAV Eplugin starting up ...
** (evolution:23163): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:23163): DEBUG: mailto URL program: evolution
CalDAV Eplugin starting up ...
** (evolution:28352): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:28352): DEBUG: mailto URL program: evolution
(evolution:28352): e-data-server-DEBUG: Loading categories from "/home/gdromig/.evolution/categories.xml"
(evolution:28352): e-data-server-DEBUG: Loaded 29 categories
BBDB spinning up...
--------------------------------------------------

Comment 1 Tobias Mueller 2008-02-14 23:18:55 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 ***