Bug 513478 – crash in Tasks: editing 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 513478 - crash in Tasks: editing tasks.


Summary:	crash in Tasks: editing tasks.


Status:	RESOLVED DUPLICATE of bug 371913

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:	2008-01-31 16:42 UTC by Dave McFerren
Modified:	2008-02-05 08:44 UTC

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

Description Dave McFerren 2008-01-31 16:42:41 UTC

Version: 2.10

What were you doing when the application crashed?
editing tasks.


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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 168378368 vsize: 168378368 resident: 82513920 share: 47423488 rss: 82513920 rss_rlim: 4294967295
CPU usage: start_time: 1201790130 rtime: 4137 utime: 3715 stime: 422 cutime:1654 cstime: 113 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208650016 (LWP 16762)]
[New Thread -1307989104 (LWP 17309)]
[New Thread -1279403120 (LWP 16771)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 187612

Thread 1 (Thread -1208650016 (LWP 16762))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 e_table_model_row_count
from /usr/lib/evolution/2.10/libetable.so.0
#6 ??
from /usr/lib/evolution/2.10/components/libevolution-calendar.so
#7 e_util_marshal_VOID__INT_INT
from /usr/lib/evolution/2.10/libeutil.so.0
#8 g_closure_invoke
from /lib/libgobject-2.0.so.0
#9 ??
from /lib/libgobject-2.0.so.0
#10 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#11 g_signal_emit
from /lib/libgobject-2.0.so.0
#12 e_table_model_rows_deleted
from /usr/lib/evolution/2.10/libetable.so.0
#13 e_table_model_row_deleted
from /usr/lib/evolution/2.10/libetable.so.0
#14 ??
from /usr/lib/evolution/2.10/components/libevolution-calendar.so
#15 g_cclosure_marshal_VOID__POINTER
from /lib/libgobject-2.0.so.0
#16 g_closure_invoke
from /lib/libgobject-2.0.so.0
#17 ??
from /lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#19 g_signal_emit
from /lib/libgobject-2.0.so.0
#20 ??
from /usr/lib/libecal-1.2.so.7
#21 g_cclosure_marshal_VOID__POINTER
from /lib/libgobject-2.0.so.0
#22 g_closure_invoke
from /lib/libgobject-2.0.so.0
#23 ??
from /lib/libgobject-2.0.so.0
#24 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#25 g_signal_emit
from /lib/libgobject-2.0.so.0
#26 ??
from /usr/lib/libecal-1.2.so.7
#27 _ORBIT_skel_small_GNOME_Evolution_Calendar_CalViewListener_notifyObjectsModified
from /usr/lib/libecal-1.2.so.7
#28 ??
from /usr/lib/libORBit-2.so.0
#29 ORBit_OAObject_invoke
from /usr/lib/libORBit-2.so.0
#30 ORBit_small_invoke_adaptor
from /usr/lib/libORBit-2.so.0
#31 ??
from /usr/lib/libORBit-2.so.0
#32 ??
from /usr/lib/libORBit-2.so.0
#33 giop_thread_queue_process
from /usr/lib/libORBit-2.so.0
#34 ??
from /usr/lib/libORBit-2.so.0
#35 ??
from /usr/lib/libORBit-2.so.0
#36 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#37 ??
from /lib/libglib-2.0.so.0
#38 g_main_loop_run
from /lib/libglib-2.0.so.0
#39 bonobo_main
from /usr/lib/libbonobo-2.so.0
#40 main
#0 __kernel_vsyscall



----------- .xsession-errors (2063275 sec old) ---------------------
(K3bDevice::ScsiCommand) failed: 
                           command:    READ (10) (28)
                           errorcode:  0
                           sense key:  NO SENSE (2)
                           asc:        0
                           ascq:       0
(K3bDevice::Device) /dev/scd1: READ 10 failed!
(K3bDevice::ScsiCommand) failed: 
                           command:    READ (10) (28)
                           errorcode:  0
                           sense key:  NO SENSE (2)
                           asc:        0
                           ascq:       0
(K3bDevice::Device) /dev/scd1: READ 10 failed!
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Akhil Laddha 2008-02-05 08:44:18 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 371913 ***