GNOME Bugzilla – Bug 322726
Alarm notify crashed when enabled a exchange account.
Last modified: 2006-07-18 09:45:32 UTC
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 1099759776 (LWP 26127)] [New Thread 1111493552 (LWP 3220)] [Thread debugging using libthread_db enabled] [New Thread 1099759776 (LWP 26127)] [New Thread 1111493552 (LWP 3220)] [Thread debugging using libthread_db enabled] [New Thread 1099759776 (LWP 26127)] [New Thread 1111493552 (LWP 3220)] [New Thread 1101650864 (LWP 26128)] 0xffffe410 in ?? ()
+ Trace 64322
Thread 1 (Thread 1099759776 (LWP 26127))
Not reproducible consistently.
In my case I can always reproduce it. Just open the preferences and select the Calendar checkbox in the Exchange account, it always crashes for me. I'm using evolution-2.5.3-1 from an up to date Fedora Devel system on a VMWare 5.5.1 machine. I'll try to get a backtrace and see what happens. Any idea about this bug?
Created attachment 56338 [details] Backtrace May be it's not very useful but this is my gdb session with no debugging symbols. If you really need to, just ask and I'll take the trouble to install the debuginfo packages and see if we can get a detailed backtrace.
the stack trace in comment #2 is a different bug ... a duplicate of 324889 whose fix is waiting in patches for approval .. the bug submitted originally needs to be looked into separately. thanx.
The code seems to be ok. But i think some other memory corruption is reflection here. I got the same crash once. It happens only with exchange account with multiple calendars as far as i have seen until now.
There has been a lot of changes made to the alarm code now. Please check if its still happening with the latest builds.
Back then in the rawhide days for fedora core 5 there was a clock icon in the notification area and I could right click it and select the calendars I wanted to notify me. If I selected the Exchange account it would crash. But no there is no clock icon in the notification area but there is a process running in background and I get notifications popups and evolution popups when a date or meeting is about to begin. So, if nobody else complains I think this bug could be closed since it is working fine with me. The only thing I was wondering is why there is no clock icon any more??
reassigning chakravarthi's bugs to avoid rotting.
refering to comment 5: chen refers to srini's ethread rewrite of the alarm code which is included in the latest (unstable) evolution 2.7.x version. poornima: ping
Closing this bug as 'Obsolete' as i dont see any alarm crashes while enabling exchange account after srini fixed many issues in alarm code.