Bug 352759 – crash on 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 352759 - crash on Evolution


Summary:	crash on Evolution


Status:	RESOLVED DUPLICATE of bug 355864

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

Importance:	High critical
Target Milestone:	---
Assigned To:	Milan Crha
QA Contact:	Evolution QA team

URL:
Whiteboard:

Duplicates:	332292 (view as bug list)
Depends on:
Blocks:

Reported:	2006-08-24 23:15 UTC by Brian Kerrick Nickel
Modified:	2013-09-13 00:51 UTC

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

Description Brian Kerrick Nickel 2006-08-24 23:15:18 UTC

What were you doing when the application crashed?
Quickly checked and unchecked a calendar in month view.


Distribution: Gentoo Base System version 1.12.4
Gnome Release: 2.15.91 2006-08-12 (Gentoo)
BugBuddy Version: 2.15.90

Memory status: size: 360697856 vsize: 0 resident: 360697856 share: 0 rss: 34557952 rss_rlim: 0
CPU usage: start_time: 1156460657 rtime: 0 utime: 801 stime: 0 cutime:760 cstime: 0 timeout: 41 it_real_value: 0 frequency: 0

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1237702976 (LWP 11897)]
[New Thread -1524728928 (LWP 12180)]
[New Thread -1515996256 (LWP 12178)]
[New Thread -1434457184 (LWP 11958)]
[New Thread -1426064480 (LWP 11957)]
[New Thread -1415955552 (LWP 11948)]
[New Thread -1333826656 (LWP 11918)]
[New Thread -1325040736 (LWP 11917)]
[New Thread -1316648032 (LWP 11912)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 70959

Thread 1 (Thread -1237702976 (LWP 11897))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 libgnomeui_segv_handle
at gnome-ui-init.c line 867
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/libc.so.6
#6 abort
from /lib/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_return_if_fail_warning
from /usr/lib/libglib-2.0.so.0
#10 e_week_view_event_item_draw
at e-week-view-event-item.c line 838
#11 gnome_canvas_item_move
from /usr/lib/libgnomecanvas-2.so.0
#12 gnome_canvas_request_redraw_uta
from /usr/lib/libgnomecanvas-2.so.0
#13 gtk_marshal_VOID__UINT_STRING
from /usr/lib/libgtk-x11-2.0.so.0
#14 g_cclosure_new_swap
from /usr/lib/libgobject-2.0.so.0
#15 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_has_handler_pending
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#19 gtk_widget_activate
from /usr/lib/libgtk-x11-2.0.so.0
#20 gtk_widget_send_expose
from /usr/lib/libgtk-x11-2.0.so.0
#21 gnome_canvas_item_grab_focus
from /usr/lib/libgnomecanvas-2.so.0
#22 gnome_canvas_item_grab_focus
from /usr/lib/libgnomecanvas-2.so.0
#23 g_child_watch_add
from /usr/lib/libglib-2.0.so.0
#24 g_source_remove_poll
from /usr/lib/libglib-2.0.so.0
#25 g_main_context_acquire
from /usr/lib/libglib-2.0.so.0
#26 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#27 bonobo_main
at bonobo-main.c line 311
#28 main
at main.c line 614
#0 __kernel_vsyscall

Comment 1 André Klapper 2006-08-25 07:42:17 UTC

g_return_if_fail(event->spans_index + wveitem->span_num < week_view->spans->len);
is the offending line in the code.

unique stacktrace.

Comment 2 Christian Kirbach 2006-08-25 17:25:50 UTC

excellent trace, confirming

Comment 3 Brian Kerrick Nickel 2006-08-25 19:17:48 UTC

"excellent trace, confirming" - I love you evolution guys. You're always so nice and helpful, even on all my bugs where my traces sucked.

Comment 4 Christian Kirbach 2006-08-25 22:43:20 UTC

I have no idea whether you are serious or sarcastic, but this is not the best place for criticism. Please point your comments to the bugsquad mailing list [1]. Constructive criticism is usually most welcome. And notice that I am not an "evolution guy".

[1] http://mail.gnome.org/mailman/listinfo/gnome-bugsquad

Comment 5 Brian Kerrick Nickel 2006-08-25 23:36:20 UTC

Sorry, I was being serious. I've had dozens of bugs ignored with the generic "Get better stacktraces" response, but whenever I report a bug in evolution, I get some solid responses. I was just really excited that I had finally submitted a decent trace.

Comment 6 Chenthill P 2006-09-01 04:54:09 UTC

*** Bug 332292 has been marked as a duplicate of this bug. ***

Comment 7 Milan Crha 2007-08-10 08:12:46 UTC

I could not reproduce this bug, but I think it's the same issue like with bug #355864 and that patch there can possibly solve this one too. (I didn't find anything wrong with week_view->spans, when I was watching the code. But I can be wrong.)

Comment 8 Milan Crha 2007-08-23 09:16:59 UTC


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