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


Summary:	crash in Tasks:


Status:	RESOLVED DUPLICATE of bug 458670

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Triage Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-02-19 15:05 UTC by sander
Modified:	2008-02-20 06:36 UTC

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

Description sander 2008-02-19 15:05:45 UTC

Version: 2.10

What were you doing when the application crashed?



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

System: Linux 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 20:27:10 EST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 695980032 vsize: 695980032 resident: 79998976 share: 41234432 rss: 79998976 rss_rlim: 18446744073709551615
CPU usage: start_time: 1203426634 rtime: 5936 utime: 5486 stime: 450 cutime:37 cstime: 16 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 46912496428400 (LWP 3978)]
[New Thread 1105475920 (LWP 4827)]
[New Thread 1094986064 (LWP 3993)]
[New Thread 1094719824 (LWP 3990)]
(no debugging symbols found)
0x000000339c00d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 189737

Thread 1 (Thread 46912496428400 (LWP 3978))

#0 waitpid
from /lib64/libpthread.so.0
#1 ??
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 g_utf8_offset_to_pointer
from /lib64/libglib-2.0.so.0
#4 ??
from /usr/lib64/libedataserverui-1.2.so.8
#5 ??
from /usr/lib64/libedataserverui-1.2.so.8
#6 ??
from /usr/lib64/libedataserverui-1.2.so.8
#7 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#8 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#9 ??
from /lib64/libgobject-2.0.so.0
#10 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#11 g_signal_emit
from /lib64/libgobject-2.0.so.0
#12 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#13 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#14 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#15 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#16 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#17 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#18 ??
from /lib64/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#20 g_signal_emit
from /lib64/libgobject-2.0.so.0
#21 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#22 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#23 ??
from /usr/lib64/libgdk-x11-2.0.so.0
#24 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#25 ??
from /lib64/libglib-2.0.so.0
#26 g_main_loop_run
from /lib64/libglib-2.0.so.0
#27 bonobo_main
from /usr/lib64/libbonobo-2.so.0
#28 main
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors ---------------------
(evolution:3978): gtkhtml-WARNING **: Selection retrieval failed
(evolution:3978): gtkhtml-WARNING **: Selection retrieval failed
(evolution:3978): gtkhtml-WARNING **: Selection retrieval failed
/bin/bash: play: command not found
/bin/bash: play: command not found
/bin/bash: play: command not found
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fffa85fd000
--------------------------------------------------

Comment 1 Akhil Laddha 2008-02-20 06:36:46 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but
we are happy to tell you that the problem has already been fixed. It should be
solved in the next software version. You may want to check for a software
upgrade.


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