Bug 476130 – crash in Tasks: Closing evolution

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 476130 - crash in Tasks: Closing evolution


Summary:	crash in Tasks: Closing evolution


Status:	RESOLVED DUPLICATE of bug 462501

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-12 08:19 UTC by Are Gravbrøt
Modified:	2007-09-26 05:34 UTC

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

Description Are Gravbrøt 2007-09-12 08:19:36 UTC

Version: 2.10

What were you doing when the application crashed?
Closing evolution


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: 606523392 vsize: 606523392 resident: 53862400 share: 33697792 rss: 53862400 rss_rlim: 18446744073709551615
CPU usage: start_time: 1189584277 rtime: 351 utime: 316 stime: 35 cutime:3 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 46912496373904 (LWP 15649)]
[New Thread 1126189392 (LWP 15897)]
[New Thread 1084229968 (LWP 15689)]
(no debugging symbols found)
0x00000033b240d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 162278

Thread 3 (Thread 1084229968 (LWP 15689))

#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 ??
from /lib64/libglib-2.0.so.0
#5 ??
from /lib64/libglib-2.0.so.0
#6 ??
from /lib64/libglib-2.0.so.0
#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 (125 sec old) ---------------------
xscreensaver: 10:14:23: 0: for window 0x36084d5 (Eclipse / Eclipse)
xscreensaver: 10:15:12: 0: unrecognised ClientMessage "_NET_ACTIVE_WINDOW" received
xscreensaver: 10:15:12: 0: for window 0x360a472 (Eclipse / Eclipse)
xscreensaver: 10:15:15: 0: unrecognised ClientMessage "_NET_ACTIVE_WINDOW" received
xscreensaver: 10:15:15: 0: for window 0x36084d5 (Eclipse / Eclipse)
xscreensaver: 10:15:20: 0: unrecognised ClientMessage "_NET_ACTIVE_WINDOW" received
xscreensaver: 10:15:20: 0: for window 0x360013d (Eclipse / Eclipse)
xscreensaver: 10:16:20: 0: unrecognised ClientMessage "_NET_ACTIVE_WINDOW" received
xscreensaver: 10:16:20: 0: for window 0x360b8f5 (gecko / Eclipse)
xscreensaver: 10:16:40: 0: unrecognised ClientMessage "_NET_ACTIVE_WINDOW" received
xscreensaver: 10:16:40: 0: for window 0x360bf6e (gecko / Eclipse)
xscreensaver: 10:16:42: 0: unrecognised ClientMessage "_NET_ACTIVE_WINDOW" received
xscreensaver: 10:16:42: 0: for window 0x360b8f5 (gecko / Eclipse)
xscreensaver: 10:16:46: 0: unrecognised ClientMessage "_NET_ACTIVE_WINDOW" received
xscreensaver: 10:16:46: 0: for window 0x360013d (Eclipse / Eclipse)
--------------------------------------------------

Comment 1 Lucky Wankhede 2007-09-26 05:34:12 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 462501 ***