Bug 332292 – crash enabling/disabling webcal

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 332292 - crash enabling/disabling webcal


Summary:	crash enabling/disabling webcal


Status:	RESOLVED DUPLICATE of bug 352759

Product:	evolution
Classification:	Applications
Component:	Calendar
Version:	2.6.x
Hardware:	Other Linux

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-calendar-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-02-23 09:33 UTC by Karsten Bräckelmann
Modified:	2013-09-13 00:59 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Karsten Bräckelmann 2006-02-23 09:33:52 UTC

Enabled an existing webcal. Got error messages:
 Cannot connect to destination

Contents displayed, though (likely cached).

Disabled webcal again. Crash.

Seems to be reproducible.

Evolution 2.5.91, GNOME 2.13.91.
Including the crashing top-most thread only.


Backtrace was generated from '/opt/gnome-2.13/bin/evolution-2.6'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1230211392 (LWP 10282)]
[New Thread -1315968080 (LWP 10321)]
[Thread debugging using libthread_db enabled]
[New Thread -1230211392 (LWP 10282)]
[New Thread -1315968080 (LWP 10321)]
[New Thread -1278112848 (LWP 10308)]
[New Thread -1286505552 (LWP 10304)]
[New Thread -1269060688 (LWP 10288)]
[New Thread -1251677264 (LWP 10286)]
[New Thread -1243284560 (LWP 10285)]
[New Thread -1234891856 (LWP 10284)]
0xffffe410 in ?? ()

+ Trace 66437

#0 ??
#1 ??
#2 ??
#3 ??
#4 __waitpid_nocancel
from /lib/tls/libpthread.so.0
#5 libgnomeui_segv_handle
at gnome-ui-init.c line 792
#6 <signal handler called>
#7 IA__g_logv
at gmessages.c line 502
#8 IA__g_log
at gmessages.c line 517
#9 IA__g_return_if_fail_warning
at gmessages.c line 532
#10 e_week_view_event_item_draw
at e-week-view-event-item.c line 245
#11 gnome_canvas_group_draw
at gnome-canvas.c line 1680
#12 gnome_canvas_expose
at gnome-canvas.c line 2992
#13 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 83
#14 g_type_class_meta_marshal
at gclosure.c line 567
#15 IA__g_closure_invoke
at gclosure.c line 490
#16 signal_emit_unlocked_R
at gsignal.c line 2476
#17 IA__g_signal_emit_valist
at gsignal.c line 2207
#18 IA__g_signal_emit
at gsignal.c line 2241
#19 gtk_widget_event_internal
at gtkwidget.c line 3735
#20 do_update
at gnome-canvas.c line 3104
#21 idle_handler
at gnome-canvas.c line 3184
#22 g_idle_dispatch
at gmain.c line 3796
#23 IA__g_main_context_dispatch
at gmain.c line 1916
#24 g_main_context_iterate
at gmain.c line 2547
#25 IA__g_main_loop_run
at gmain.c line 2751
#26 bonobo_main
at bonobo-main.c line 312
#27 main
at main.c line 603

Comment 1 Karsten Bräckelmann 2006-02-23 09:36:42 UTC

Forgot to mention, this is using Month View.

Yes, Month View -- despite the fact there is an e_week_view_event_item_draw() function call in that stacktrace...

Comment 2 Karsten Bräckelmann 2006-02-24 01:27:37 UTC

I just got the very same stacktrace, doing a totally different thing:

* Month View. Click an Appointment (and see the cursor blinking).
* Hit Ctrl+D to delete.
  Crash.

Yes, this led to the *same* stacktrace...

Comment 3 Karsten Bräckelmann 2006-02-24 22:54:06 UTC

Just got the same stacktrace twice, after e-d-s died and Evolution told me about this by a couple of error messages.

Comment 4 Poornima 2006-07-03 11:21:39 UTC

guenther :Tried with all inputs given here, not able to reproduce it on evolution 2.6.2. Do u still see this crash. Is it conistent crash, it looks like random bug.

Comment 5 Karsten Bräckelmann 2006-07-23 15:35:48 UTC

Oh crap, not this game again...

Poornima, please note that this is a CRITICAL WARNING crasher, as the stacktrace clearly shows. Critical Warnings are disabled for stable GNOME releases. You definitely will not be able to reproduce a Critical Warning crash, *unless* you are running an *unstable* GNOME Desktop version. To be precise, gnome-session.

Yes, running an unstable Evo version on a stable GNOME Desktop will *not* show this either.


Poornima, we've had this discussion before already...

Comment 6 Harish Krishnaswamy 2006-08-10 12:59:31 UTC

Set target milestone to 2.8

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


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