GNOME Bugzilla – Bug 412626
evolution-alarm-notifier crashes during startup
Last modified: 2007-06-20 23:42:32 UTC
Steps to reproduce: 1. 2. 3. Stack trace: Memory status: size: 60227584 vsize: 0 resident: 60227584 share: 0 rss: 9678848 rss_rlim: 0 CPU usage: start_time: 1172583401 rtime: 0 utime: 13 stime: 0 cutime:11 cstime: 0 timeout: 2 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/libexec/evolution-alarm-notify' (no debugging symbols found) 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) [Thread debugging using libthread_db enabled] [New Thread -1233377616 (LWP 5092)] [New Thread -1243288672 (LWP 5175)] [New Thread -1234629728 (LWP 5105)] (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) 0xffffe410 in __kernel_vsyscall ()
+ Trace 114315
Thread 1 (Thread -1233377616 (LWP 5092))
Other information:
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please install some debugging packages [1], start the application as normal, and reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the Details, now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! Also, which Evolution version and which distribution is this? [1] debugging packages for evolution, evolution-data-server, gtkhtml, gtk, glib, gnome-vfs, libgnome and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
(In reply to comment #1) > Thanks for taking the time to report this bug. > Unfortunately, that stack trace is missing some elements that will help a lot > to solve the problem, so it will be hard for the developers to fix that crash. > Could you please install some debugging packages [1], start the application as > normal, and reproduce the crash, if possible? > > Once bug-buddy pops up, you can find the stacktrace in the Details, now > containing way more information. Please copy that stacktrace and paste it as a > comment here. Thanks in advance! > > Also, which Evolution version and which distribution is this? > > [1] debugging packages for evolution, evolution-data-server, gtkhtml, gtk, > glib, gnome-vfs, libgnome and libgnomeui (as far as those packages are provided > by your distribution). More details can be found here: > http://live.gnome.org/GettingTraces > Evolution version 2.8.1-0ubuntu4 and distribution is ubuntu edgy (6.10). Evolution was installed as part of the distribution and upgraded during the upgrade from ubuntu dapper to edgy. I have not configured Evolution and do not use it, however, bug-buddy pops up every time I start my computer with the Evolution-alarm-notify problem unless I remove Evolution from the autostarted applications. I am short on time until Saturday, March 3, when I will be able to configure Evolution and the asked for debugging packages then try to reproduce the crash.
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
Sorry for the delay, had to go out of state on family business for several days. Installed the debugging packages I could find for my distribution. Bug buddy report follows: Memory status: size: 60231680 vsize: 0 resident: 60231680 share: 0 rss: 9842688 rss_rlim: 0 CPU usage: start_time: 1175753426 rtime: 0 utime: 15 stime: 0 cutime:12 cstime: 0 timeout: 3 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/libexec/evolution-alarm-notify' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1232750928 (LWP 5163)] [New Thread -1234003040 (LWP 5193)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 125144
Thread 1 (Thread -1232750928 (LWP 5163))
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 273699 ***
*** Bug 430681 has been marked as a duplicate of this bug. ***