Bug 324673 – Alarm notify crashed

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 324673 - Alarm notify crashed


Summary:	Alarm notify crashed


Status:	RESOLVED FIXED

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:	327508 327510

Reported:	2005-12-21 04:45 UTC by Poornima
Modified:	2013-09-13 00:53 UTC

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

Description Poornima 2005-12-21 04:45:27 UTC

1. Disabled 'exchange' account.
2. Restarted evolution
3. Executed some message menu options which had nothing to do with calendar.
4. Alarm notify crashed in few minutes.

Stack traces of crash.

Backtrace was generated from '/opt/gnome/libexec/evolution-alarm-notify'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 1099772064 (LWP 1089)]
[New Thread 1101609904 (LWP 1090)]
[Thread debugging using libthread_db enabled]
[New Thread 1099772064 (LWP 1089)]
[New Thread 1101609904 (LWP 1090)]
[Thread debugging using libthread_db enabled]
[New Thread 1099772064 (LWP 1089)]
[New Thread 1101609904 (LWP 1090)]
0xffffe410 in ?? ()

+ Trace 64732

Thread 1 (Thread 1099772064 (LWP 1089))

#0 ??
#1 ??
#2 ??
#3 ??
#4 __waitpid_nocancel
from /lib/tls/libpthread.so.0
#5 libgnomeui_module_info_get
from /opt/gnome/lib/libgnomeui-2.so.0
#6 <signal handler called>
#7 e_calendar_remove_op
at e-cal.c line 307
#8 open_calendar
at e-cal.c line 1724
#9 reopen_with_auth
at e-cal.c line 964
#10 g_child_watch_add
from /opt/gnome/lib/libglib-2.0.so.0
#11 g_main_context_dispatch
from /opt/gnome/lib/libglib-2.0.so.0
#12 g_main_context_check
from /opt/gnome/lib/libglib-2.0.so.0
#13 g_main_context_iteration
from /opt/gnome/lib/libglib-2.0.so.0
#14 ep_msg_send
at e-passwords.c line 179
#15 e_passwords_get_password
at e-passwords.c line 663
#16 alarm_notify_add_calendar
at alarm-notify.c line 352
#17 list_changed_cb
at alarm-notify.c line 147
#18 load_calendars_cb
at alarm-notify.c line 211
#19 g_main_context_wakeup
from /opt/gnome/lib/libglib-2.0.so.0
#20 g_main_context_dispatch
from /opt/gnome/lib/libglib-2.0.so.0
#21 g_main_context_check
from /opt/gnome/lib/libglib-2.0.so.0
#22 g_main_loop_run
from /opt/gnome/lib/libglib-2.0.so.0
#23 bonobo_main
from /opt/gnome/lib/libbonobo-2.so.0
#24 main
at notify-main.c line 169
#0 ??

Comment 1 Teppo Turtiainen 2005-12-23 20:15:03 UTC

According to simple-dup-finder this is a unique stack trace.

Comment 2 Chenthill P 2006-01-25 05:46:47 UTC

This might be a exchange specific bug.

Comment 3 Sushma Rai 2006-02-02 10:51:44 UTC

evolution-alarm-notify crashed, slightly different trace.
I had only one exchange account configured.

0xffffe410 in __kernel_vsyscall ()

+ Trace 65848

Thread 1 (Thread -1232533840 (LWP 25291))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 gnome_init_with_popt_table
from /opt/gnome/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 e_calendar_remove_op
from /opt/gnome/lib/libecal-1.2.so.3
#5 open_calendar
from /opt/gnome/lib/libecal-1.2.so.3
#6 reopen_with_auth
from /opt/gnome/lib/libecal-1.2.so.3
#7 g_list_copy
from /opt/gnome/lib/libglib-2.0.so.0
#8 g_main_context_dispatch
from /opt/gnome/lib/libglib-2.0.so.0
#9 g_main_context_check
from /opt/gnome/lib/libglib-2.0.so.0
#10 g_main_context_iteration
from /opt/gnome/lib/libglib-2.0.so.0
#11 ep_msg_send
from /opt/gnome/lib/libedataserverui-1.2.so.6
#12 e_passwords_get_password
from /opt/gnome/lib/libedataserverui-1.2.so.6
#13 auth_func_cb
#14 open_calendar
from /opt/gnome/lib/libecal-1.2.so.3
#15 reopen_with_auth
from /opt/gnome/lib/libecal-1.2.so.3
#16 g_list_copy
from /opt/gnome/lib/libglib-2.0.so.0
#17 g_main_context_dispatch
from /opt/gnome/lib/libglib-2.0.so.0
#18 g_main_context_check
from /opt/gnome/lib/libglib-2.0.so.0
#19 g_main_context_iteration
from /opt/gnome/lib/libglib-2.0.so.0
#20 ep_msg_send
from /opt/gnome/lib/libedataserverui-1.2.so.6
#21 e_passwords_get_password
from /opt/gnome/lib/libedataserverui-1.2.so.6
#22 auth_func_cb
#23 open_calendar
from /opt/gnome/lib/libecal-1.2.so.3
#24 reopen_with_auth
from /opt/gnome/lib/libecal-1.2.so.3
#25 g_list_copy
from /opt/gnome/lib/libglib-2.0.so.0
#26 g_main_context_dispatch
from /opt/gnome/lib/libglib-2.0.so.0
#27 g_main_context_check
from /opt/gnome/lib/libglib-2.0.so.0
#28 g_main_loop_run
from /opt/gnome/lib/libglib-2.0.so.0
#29 bonobo_main
from /opt/gnome/lib/libbonobo-2.so.0
#30 main
#0 __kernel_vsyscall

Comment 4 Sushma Rai 2006-02-02 11:04:17 UTC

My Evolution version is 2.5.90

Comment 5 Chenthill P 2006-02-09 13:51:29 UTC

This should have been fixed now. I have committed a fix in evolution-exchange on 
2006-02-06. This ensures that the backend is loaded before reopening the calendar when the mode is it set as remote in the backend. Pasting the ChangeLog,
2006-02-06  Chenthill Palanisamy  <pchenthill@novell.com>

	* calendar/e-cal-backend-exchange.c: (open_calendar), 
	(is_loaded), (class_init): Added the implementation.
	(set_mode): Notify read only status to the client. 
Please reopen if you find it happening.