Bug 515479 – crash in Tasks: just closing the app

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 515479 - crash in Tasks: just closing the app


Summary:	crash in Tasks: just closing the app


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-09 21:08 UTC by gromig
Modified:	2008-02-10 19:26 UTC

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

Description gromig 2008-02-09 21:08:53 UTC

Version: 2.10

What were you doing when the application crashed?
just closing the app



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.14-64.fc7 #1 SMP Sun Jan 20 23:54:08 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: 125771776 vsize: 125771776 resident: 40468480 share: 27713536 rss: 40468480 rss_rlim: 4294967295
CPU usage: start_time: 1202561673 rtime: 1663 utime: 1552 stime: 111 cutime:0 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 -1208756512 (LWP 12598)]
[New Thread -1260749936 (LWP 15017)]
[New Thread -1250260080 (LWP 14790)]
[New Thread -1229132912 (LWP 12665)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 188690

Thread 2 (Thread -1260749936 (LWP 15017))

#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 (3402 sec old) ---------------------
** (evolution:12598): DEBUG: mailto URL program: evolution
--- Hash table keys for warning below:
--> file:///home/gdromig
(nautilus:12744): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
camel-Message: --
camel-Message: --
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4200099 (XScreenSav)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
camel-Message: --
camel-Message: --
BBDB spinning up...
(evolution:12598): e-data-server-DEBUG: Loading categories from "/home/gdromig/.evolution/categories.xml"
(evolution:12598): e-data-server-DEBUG: Loaded 29 categories
--------------------------------------------------

Comment 1 Tobias Mueller 2008-02-10 19:26:23 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 ***