Bug 385189 – crash in Evolution: Checked a todo item

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 385189 - crash in Evolution: Checked a todo item


Summary:	crash in Evolution: Checked a todo item


Status:	RESOLVED DUPLICATE of bug 518551

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.8.x (obsolete)
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-12-12 20:27 UTC by David Pettersson
Modified:	2009-05-28 05:32 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description David Pettersson 2006-12-12 20:27:27 UTC

What were you doing when the application crashed?
Cheched a todo item.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 186810368 vsize: 0 resident: 186810368 share: 0 rss: 45428736 rss_rlim: 0
CPU usage: start_time: 1165952974 rtime: 0 utime: 2166 stime: 0 cutime:2031 cstime: 0 timeout: 135 it_real_value: 0 frequency: 4

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1233394000 (LWP 5486)]
[New Thread -1331508320 (LWP 5523)]
[New Thread -1297937504 (LWP 5505)]
[New Thread -1263920224 (LWP 5504)]
[New Thread -1274020960 (LWP 5502)]
[New Thread -1255527520 (LWP 5501)]
[New Thread -1255261280 (LWP 5490)]
_______________________________________________________________________________
     eax:FFFFFE00 ebx:0000190B  ecx:BFF37224  edx:00000000     eflags:00000246
     esi:0000000B edi:BFF377EC  esp:BFF37154  ebp:BFF37258     eip:FFFFE410
     cs:0073  ds:007B  es:007B  fs:0000  gs:0033  ss:007B    o d I t s Z a P c 
[007B:BFF37154]---------------------------------------------------------[stack]
BFF37184 : 00 00 00 00  B0 79 2B 08 - 14 B2 58 01  04 35 B7 08 .....y+...X..5..
BFF37174 : 24 72 F3 BF  00 00 00 00 - 34 72 F3 BF  00 35 B7 08 $r......4r...5..
BFF37164 : 14 07 E4 B7  00 00 00 00 - B6 C1 E0 B7  0B 19 00 00 ................
BFF37154 : 58 72 F3 BF  00 00 00 00 - 24 72 F3 BF  CB F6 0F B7 Xr......$r......
[007B:BFF377EC]---------------------------------------------------------[ data]
BFF377EC : A0 78 2B 08  68 43 13 B4 - 00 00 00 00  00 00 00 00 .x+.hC..........
BFF377FC : 00 00 00 00  18 00 00 00 - 0E 00 00 00  00 00 00 00 ................
[0073:FFFFE410]---------------------------------------------------------[ code]
0xffffe410 <__kernel_vsyscall+16>:	pop    %ebp
0xffffe411 <__kernel_vsyscall+17>:	pop    %edx
0xffffe412 <__kernel_vsyscall+18>:	pop    %ecx
0xffffe413 <__kernel_vsyscall+19>:	ret    
0xffffe414 <__kernel_vsyscall+20>:	nop    
0xffffe415 <__kernel_vsyscall+21>:	nop    
------------------------------------------------------------------------------
0xffffe410 in __kernel_vsyscall ()

+ Trace 93636

#0 __kernel_vsyscall
#1 waitpid
from /lib/tls/i686/cmov/libc.so.6
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 segv_redirect
at main.c line 426
#4 <signal handler called>
#5 e_table_selected_count
at e-table.c line 2030
#6 set_info
at tasks-component.c line 515
#7 e_util_marshal_VOID__INT_INT
at e-util-marshal.c line 813
#8 IA__g_closure_invoke
at gclosure.c line 490
#9 signal_emit_unlocked_R
at gsignal.c line 2440
#10 IA__g_signal_emit_valist
at gsignal.c line 2199
#11 IA__g_signal_emit
at gsignal.c line 2243
#12 e_table_model_rows_deleted
at e-table-model.c line 586
#13 e_table_model_row_deleted
at e-table-model.c line 603
#14 e_cal_view_objects_added_cb
at e-cal-model.c line 1383
#15 IA__g_cclosure_marshal_VOID__POINTER
at gmarshal.c line 601
#16 IA__g_closure_invoke
at gclosure.c line 490
#17 signal_emit_unlocked_R
at gsignal.c line 2440
#18 IA__g_signal_emit_valist
at gsignal.c line 2199
#19 IA__g_signal_emit
at gsignal.c line 2243
#20 e_cal_view_new
from /usr/lib/libecal-1.2.so.7
#21 IA__g_cclosure_marshal_VOID__POINTER
at gmarshal.c line 601
#22 IA__g_closure_invoke
at gclosure.c line 490
#23 signal_emit_unlocked_R
at gsignal.c line 2440
#24 IA__g_signal_emit_valist
at gsignal.c line 2199
#25 IA__g_signal_emit
at gsignal.c line 2243
#26 e_cal_view_listener_new
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 IOP_start_profiles
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 ORBit_recv_buffer_return_sys_exception
from /usr/lib/libORBit-2.so.0
#32 ORBit_recv_buffer_return_sys_exception
from /usr/lib/libORBit-2.so.0
#33 giop_thread_queue_process
from /usr/lib/libORBit-2.so.0
#34 giop_init
from /usr/lib/libORBit-2.so.0
#35 link_io_add_watch_fd
from /usr/lib/libORBit-2.so.0
#36 IA__g_main_context_dispatch
at gmain.c line 2045
#37 g_main_context_iterate
at gmain.c line 2677
#38 IA__g_main_loop_run
at gmain.c line 2881
#39 bonobo_main
from /usr/lib/libbonobo-2.so.0
#40 main
at main.c line 615

Comment 1 David Pettersson 2006-12-12 21:21:41 UTC

I was in a bit of a hurry when I reported this. I was checking away at my todo-list and after adding, checking and removing some items Evolution suddenly crashed.
  Looks like a fault in the table management? I was in the calendar view and had the todo items in the right side-panel.

Comment 2 Kjartan Maraas 2007-01-16 09:51:45 UTC

+ Trace 102645

#5 e_table_selected_count
at e-table.c line 2030


This looks kind of suspect yes. Anyone with e-table insight who could look at this?

Comment 3 Akhil Laddha 2009-05-28 05:32:23 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 518551 ***