Bug 451582 – crash in Tasks: quitting 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 451582 - crash in Tasks: quitting evolution


Summary:	crash in Tasks: quitting evolution


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-27 12:24 UTC by Boris Goldowsky
Modified:	2007-06-27 13:34 UTC

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

Description Boris Goldowsky 2007-06-27 12:24:29 UTC

Version: 2.10

What were you doing when the application crashed?
quitting evolution


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: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 692416512 vsize: 692416512 resident: 100651008 share: 57884672 rss: 100651008 rss_rlim: 18446744073709551615
CPU usage: start_time: 1182943073 rtime: 735 utime: 638 stime: 97 cutime:25 cstime: 17 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 46912496455264 (LWP 18301)]
[New Thread 1126455632 (LWP 19045)]
[New Thread 1115965776 (LWP 18936)]
[New Thread 1105475920 (LWP 18378)]
0x000000337420d89f in waitpid () from /lib64/libpthread.so.0

+ Trace 144089

Thread 2 (Thread 1126455632 (LWP 19045))

#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 (10 sec old) ---------------------
Executing reader on sql '
                                      SELECT * FROM PodcastFeeds ORDER BY Title
                                      '
Setting IO Backend to Banshee.IO.Unix.IOConfig (unix)
(Banshee:18963): GStreamer-CRITICAL **: gst_element_set_state: assertion `GST_IS_ELEMENT (element)' failed
GStreamer resource error: Busy
(Banshee:18963): GStreamer-CRITICAL **: gst_element_set_state: assertion `GST_IS_ELEMENT (element)' failed
Could not fetch recommendations: The remote server returned an error: (404) Not Found.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1800021 (Music Play)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
(evolution:18301): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922
--------------------------------------------------

Comment 1 palfrey 2007-06-27 13:34:19 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 ***