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


Summary:	crash in Tasks:


Status:	RESOLVED DUPLICATE of bug 445309

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-06-18 05:17 UTC by jld
Modified:	2007-06-18 11:52 UTC

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

Description jld 2007-06-18 05:17:52 UTC

Version: 2.10

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 686968832 vsize: 686968832 resident: 57020416 share: 37306368 rss: 57020416 rss_rlim: 18446744073709551615
CPU usage: start_time: 1182141739 rtime: 2481 utime: 2173 stime: 308 cutime:2 cstime: 8 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496463456 (LWP 23427)]
[New Thread 1115965776 (LWP 23790)]
[New Thread 1157658960 (LWP 23640)]
[New Thread 1094986064 (LWP 23544)]
(no debugging symbols found)
0x0000003eb680d89f in waitpid () from /lib64/libpthread.so.0

+ Trace 141802

Thread 2 (Thread 1115965776 (LWP 23790))

#0 __lll_mutex_lock_wait
from /lib64/libpthread.so.0
#1 _L_mutex_lock_103
from /lib64/libpthread.so.0
#2 pthread_mutex_lock
from /lib64/libpthread.so.0
#3 <signal handler called>
#4 pthread_mutex_lock
from /lib64/libpthread.so.0
#5 PR_Lock
from /usr/lib64/libnspr4.so
#6 ??
from /usr/lib64/libnspr4.so
#7 __nptl_deallocate_tsd
from /lib64/libpthread.so.0
#8 start_thread
from /lib64/libpthread.so.0
#9 clone
from /lib64/libc.so.6



----------- .xsession-errors ---------------------
(evolution:23427): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922
(evolution:23427): e-activity-handler.c-WARNING **: EActivityHandler: unknown operation 10922
(evolution:23427): e-activity-handler.c-WARNING **: EActivityHandler: unknown operation 10922
(evolution:23427): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922
(evolution:23427): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922
(evolution:23427): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922
--------------------------------------------------

Comment 1 André Klapper 2007-06-18 11:52:15 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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