GNOME Bugzilla – Bug 324889
Selecting calendar from event-notification drop-down from notification-area crashes EDS
Last modified: 2013-09-14 16:49:15 UTC
Distribution: Ubuntu 6.04 (dapper) Package: Evolution-Data-Server Severity: major Version: GNOME2.13.3 1.5.x Gnome-Distributor: Ubuntu Synopsis: Selecting calendar from event-notification drop-down from notification-area crashes EDS Bugzilla-Product: Evolution-Data-Server Bugzilla-Component: Calendar Bugzilla-Version: 1.5.x BugBuddy-GnomeVersion: 2.0 (2.13.0) Description: Description of the crash: Selecting calendar from event-notification drop-down from notification-area crashes EDS Steps to reproduce the crash: 1. Right-click on event-notification icon in notification window and select edit-preferences 2. Select any calendar from the preferences window 3. EDS crashes Expected Results: I guess that selecting a calendar from the preferences should cause me to get notifications for events from that calendar. How often does this happen? Every time Additional Information: Ubuntu Dapper, Evolution version 2.5.3-0ubuntu2 Debugging Information: Backtrace was generated from '/usr/libexec/evolution-alarm-notify' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1230969152 (LWP 5729)] [New Thread -1264432208 (LWP 7003)] [New Thread -1232335952 (LWP 5731)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in ?? ()
+ Trace 64785
------- Bug created by bug-buddy at 2005-12-23 16:54 -------
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
OK. I recompiled evolution with debugging symbols (pats self on back). I also found that bug-buddy was looking for debugging symbols at /usr/libexec/evolution-alarm-notify instead of the actual location in /usr/lib/evolution/2.6/ so I copied the binary to the exepcted place so I could get the backtrace. Backtrace was generated from '/usr/libexec/evolution-alarm-notify' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. [Thread debugging using libthread_db enabled] [New Thread -1230891328 (LWP 423)] [New Thread -1232258128 (LWP 424)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 64833
Thread 1 (Thread -1230891328 (LWP 423))
According to simple-dup-finder this is a unique stack trace.
*** Bug 325893 has been marked as a duplicate of this bug. ***
It seems the trace from Bug 325893 (marked duplicate of this) is much better than mine. Is it good enough, or should I try again myself?
yes indeed, thanks for pointing that out, Christopher. this is good enough, confirming. from Bug 325893
+ Trace 65001
Thread 1 (Thread -1232382272 (LWP 32660))
there are a few issues found with that part of the code. Will send a patch that will fix all those (including this).
the approved patch on the list is committed and the problem is fixed now.
*** Bug 326121 has been marked as a duplicate of this bug. ***
*** Bug 327211 has been marked as a duplicate of this bug. ***
Thanks for fixing, chakravarti.
The fix works for me. Thanks!!