Bug 473638 – crash in Tasks: exiting

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 473638 - crash in Tasks: exiting


Summary:	crash in Tasks: exiting


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-09-04 17:28 UTC by andrea
Modified:	2007-09-04 23:04 UTC

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

Description andrea 2007-09-04 17:28:06 UTC

Version: 2.10

What were you doing when the application crashed?
exiting


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

System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 21:50:50 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 677715968 vsize: 677715968 resident: 79704064 share: 32317440 rss: 79704064 rss_rlim: 18446744073709551615
CPU usage: start_time: 1188925199 rtime: 2528 utime: 2173 stime: 355 cutime:538 cstime: 56 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 46912741439936 (LWP 3236)]
[New Thread 1136945488 (LWP 3702)]
[New Thread 1105209680 (LWP 3400)]
[New Thread 1126455632 (LWP 3307)]
(no debugging symbols found)
0x00002aaaad8a897f in waitpid () from /lib64/libpthread.so.0

+ Trace 160436

Thread 2 (Thread 1136945488 (LWP 3702))

#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 (346 sec old) ---------------------
Decreasing itip formatter search count to 0
Increasing itip formatter search count to 1
Increasing itip formatter search count to 2
Decreasing itip formatter search count to 1
Decreasing itip formatter search count to 0
report junk?? An Offer
report junk?? Accredito temporaneamente bloccato
(evolution:3236): camel-imap-provider-WARNING **: No information for message 1
(evolution:3236): camel-imap-provider-WARNING **: No information for message 1
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3800003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------

Comment 1 Tobias Mueller 2007-09-04 23:04:37 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 ***