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


Summary:	crash in Tasks:


Status:	RESOLVED DUPLICATE of bug 448890

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-24 00:08 UTC by nigelshea
Modified:	2007-09-24 15:52 UTC

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

Description nigelshea 2007-09-24 00:08:04 UTC

Version: 2.10

What were you doing when the application crashed?



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.5-76.fc7 #1 SMP Thu Aug 30 13:08:59 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 601391104 vsize: 601391104 resident: 65679360 share: 40792064 rss: 65679360 rss_rlim: 18446744073709551615
CPU usage: start_time: 1190592058 rtime: 871 utime: 789 stime: 82 cutime:1 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 46912636302912 (LWP 4562)]
[New Thread 1126455632 (LWP 4650)]
[New Thread 1105209680 (LWP 4645)]
(no debugging symbols found)
0x00002aaaacdfd97f in waitpid () from /lib64/libpthread.so.0

+ Trace 164946

Thread 1 (Thread 46912636302912 (LWP 4562))

#0 waitpid
from /lib64/libpthread.so.0
#1 ??
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 ??
from /lib64/libglib-2.0.so.0
#4 ??
from /lib64/libglib-2.0.so.0
#5 ??
from /lib64/libglib-2.0.so.0
#6 g_slice_free1
from /lib64/libglib-2.0.so.0
#7 ??
from /lib64/libglib-2.0.so.0
#8 g_hash_table_remove_all
from /lib64/libglib-2.0.so.0
#9 g_hash_table_destroy
from /lib64/libglib-2.0.so.0
#10 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#11 ??
from /usr/lib64/libgtk-x11-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 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#16 ??
from /lib64/libgobject-2.0.so.0
#17 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#18 g_signal_emit
from /lib64/libgobject-2.0.so.0
#19 ??
from /usr/lib64/libgtk-x11-2.0.so.0
#20 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#21 ??
from /usr/lib64/libgdk-x11-2.0.so.0
#22 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#23 ??
from /lib64/libglib-2.0.so.0
#24 g_main_loop_run
from /lib64/libglib-2.0.so.0
#25 bonobo_main
from /usr/lib64/libbonobo-2.so.0
#26 main
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors ---------------------
egrep: writing output: Broken pipe
egrep: writing output: Broken pipe
egrep: writing output: Broken pipe
egrep: writing output: Broken pipe
egrep: writing output: Broken pipe
egrep: writing output: Broken pipe
egrep: writing output: Broken pipe
egrep: writing output: Broken pipe
egrep: writing output: Broken pipe
kbuildsycoca running...
Reusing existing ksycoca
kbuildsycoca running...
Reusing existing ksycoca
kbuildsycoca running...
Reusing existing ksycoca
--------------------------------------------------

Comment 1 palfrey 2007-09-24 15:52:46 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 448890 ***