Bug 332589 – customizing alarms crashing Evo

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 332589 - customizing alarms crashing Evo


Summary:	customizing alarms crashing Evo


Status:	RESOLVED DUPLICATE of bug 333706

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

Importance:	High critical
Target Milestone:	---
Assigned To:	Chenthill P
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-02-26 01:22 UTC by Karsten Bräckelmann
Modified:	2013-09-13 00:49 UTC

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

Attachments
Fixes the bug (1.30 KB, patch) 2006-08-18 10:18 UTC, Chenthill P	none	Details \| Review

Description Karsten Bräckelmann 2006-02-26 01:22:56 UTC

Calendar, Month View. Create New Appointment.
Set Alarms, choose Customize.
Select the appearing default one in the list.
Click "Edit" button, to customize it.

Evolution crashes instantly and reprocibly.


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 10897)]
[New Thread -1325409360 (LWP 13336)]
[Thread debugging using libthread_db enabled]
[New Thread -1230211392 (LWP 10897)]
[New Thread -1325409360 (LWP 13336)]
[Thread debugging using libthread_db enabled]
[New Thread -1230211392 (LWP 10897)]
[New Thread -1325409360 (LWP 13336)]
[New Thread -1260119120 (LWP 11014)]
[New Thread -1286505552 (LWP 10925)]
[New Thread -1296151632 (LWP 10924)]
[New Thread -1278112848 (LWP 10920)]
[New Thread -1269060688 (LWP 10903)]
[New Thread -1251677264 (LWP 10901)]
[New Thread -1243284560 (LWP 10900)]
[New Thread -1234891856 (LWP 10899)]
0xffffe410 in ?? ()

+ Trace 66516

#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 IA__gtk_text_buffer_set_text
at gtktextbuffer.c line 551
#11 alarm_to_dialog
at alarm-dialog.c line 368
#12 alarm_dialog_run
at alarm-dialog.c line 1132
#13 edit_clicked_cb
at alarm-list-dialog.c line 174
#14 IA__g_cclosure_marshal_VOID__VOID
at gmarshal.c line 77
#15 IA__g_closure_invoke
at gclosure.c line 490
#16 signal_emit_unlocked_R
at gsignal.c line 2438
#17 IA__g_signal_emit_valist
at gsignal.c line 2197
#18 IA__g_signal_emit
at gsignal.c line 2241
#19 IA__gtk_button_clicked
at gtkbutton.c line 834
#20 gtk_real_button_released
at gtkbutton.c line 1369
#21 IA__g_cclosure_marshal_VOID__VOID
at gmarshal.c line 77
#22 g_type_class_meta_marshal
at gclosure.c line 567
#23 IA__g_closure_invoke
at gclosure.c line 490
#24 signal_emit_unlocked_R
at gsignal.c line 2368
#25 IA__g_signal_emit_valist
at gsignal.c line 2197
#26 IA__g_signal_emit
at gsignal.c line 2241
#27 IA__gtk_button_released
at gtkbutton.c line 826
#28 gtk_button_button_release
at gtkbutton.c line 1262
#29 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 83
#30 g_type_class_meta_marshal
at gclosure.c line 567
#31 IA__g_closure_invoke
at gclosure.c line 490
#32 signal_emit_unlocked_R
at gsignal.c line 2476
#33 IA__g_signal_emit_valist
at gsignal.c line 2207
#34 IA__g_signal_emit
at gsignal.c line 2241
#35 gtk_widget_event_internal
at gtkwidget.c line 3735
#36 IA__gtk_propagate_event
at gtkmain.c line 2175
#37 IA__gtk_main_do_event
at gtkmain.c line 1412
#38 gdk_event_dispatch
at gdkevents-x11.c line 2291
#39 IA__g_main_context_dispatch
at gmain.c line 1916
#40 g_main_context_iterate
at gmain.c line 2547
#41 IA__g_main_loop_run
at gmain.c line 2751
#42 bonobo_main
at bonobo-main.c line 312
#43 main
at main.c line 603

Comment 1 Poornima 2006-05-06 06:49:43 UTC

Not reproducible in Evolution 2.6.x. 
Guenther: If it was consistent crash, can u test this again in evolution 2.6

Comment 2 Poornima 2006-06-06 08:55:22 UTC

Marking this bug for needinfo

Comment 3 André Klapper 2006-06-11 17:38:01 UTC

poornima: *obviously* you cannot reproduce this in 2.6, because stable releases do not have G_LOG_LEVEL_CRITICAL enabled by default, right? garrr...

anyway... guenther, able to reproduce it in 2.7.x where srini's EThread alarm notify code is included?

sigh...

Comment 4 Karsten Bräckelmann 2006-07-23 15:41:58 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 5 Harish Krishnaswamy 2006-08-10 12:59:36 UTC

Set target milestone to 2.8

Comment 6 Chenthill P 2006-08-18 10:18:18 UTC

Created attachment 71136 [details] [review]
Fixes the bug

Comment 7 Harish Krishnaswamy 2006-08-19 10:46:43 UTC

It would not be the text_buffer but description.value that you would be interested in handling the NULL condition :-). Please update the patch and commit to the HEAD and gnome-2.14 branches.

Comment 8 Chenthill P 2006-08-19 11:06:32 UTC


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