Bug 449846 – crash in Tasks: Closing the application.

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 449846 - crash in Tasks: Closing the application.


Summary:	crash in Tasks: Closing the application.


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-21 18:35 UTC by jussi.lehtola
Modified:	2007-06-21 22:25 UTC

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

Description jussi.lehtola 2007-06-21 18:35:37 UTC

Version: 2.10

What were you doing when the application crashed?
Closing the application.


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: No
Accessibility: Disabled
GTK+ Theme: Mist
Icon Theme: Mist

Memory status: size: 567537664 vsize: 567537664 resident: 57110528 share: 26423296 rss: 57110528 rss_rlim: 18446744073709551615
CPU usage: start_time: 1182450155 rtime: 430 utime: 377 stime: 53 cutime:2 cstime: 4 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 46912507207904 (LWP 13671)]
[New Thread 1147169104 (LWP 13911)]
(no debugging symbols found)
0x0000003405a0d89f in waitpid () from /lib64/libpthread.so.0

+ Trace 142722

Thread 2 (Thread 1147169104 (LWP 13911))

#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 (8 sec old) ---------------------
(evolution:13671): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922
(evolution:13671): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922
(evolution:13671): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922
(evolution:13671): e-activity-handler.c-WARNING **: EActivityHandler: unknown operation 10922
(evolution:13671): e-activity-handler.c-WARNING **: EActivityHandler: unknown operation 10922
(evolution:13671): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922
--------------------------------------------------

Comment 1 André Klapper 2007-06-21 22:25:08 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 445309 ***

Comment 2 André Klapper 2007-06-21 22:25:49 UTC

uhm, sorry for the wrong comment, there are no questions in the other report. :-)