GNOME Bugzilla – Bug 509466
crash in Evolution Mail during startup
Last modified: 2008-09-15 08:44:29 UTC
What were you doing when the application crashed? I have no idea what happened, this bug report dialogue came out of nowhere! Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 45613056 vsize: 45613056 resident: 9531392 share: 8032256 rss: 9531392 rss_rlim: 4294967295 CPU usage: start_time: 1200340399 rtime: 5 utime: 3 stime: 2 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/bug-buddy/evolution-alarm-notify' (no debugging symbols found) Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb68806b0 (LWP 9627)] [New Thread 0xb6616b90 (LWP 9657)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 185336
Thread 1 (Thread 0xb68806b0 (LWP 9627))
----------- .xsession-errors --------------------- evolution-alarm-notify-Message: Setting timeout for 14800 1200355200 1200340400 evolution-alarm-notify-Message: Tue Jan 15 13:00:00 2008 evolution-alarm-notify-Message: Tue Jan 15 08:53:20 2008 evolution-alarm-notify-Message: Setting timeout for 14800 1200355200 1200340400 evolution-alarm-notify-Message: Tue Jan 15 13:00:00 2008 evolution-alarm-notify-Message: Tue Jan 15 08:53:20 2008 ** Message: failed to load session from /home/jasen/.nautilus/saved-session-86LR2T evolution-alarm-notify-ERROR **: Could not create the alarm notify service factory aborting... /usr/lib/bug-buddy/evolution-alarm-notify: No such file or directory. --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, the 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 help fixing this by installing some debugging packages [1], start the application as normal, and try to 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! [1] Please install debug packages for evolution, evolution-data-server, gtkhtml, gtk, glib, gnome-vfs, pango, libgnome and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
what I was doing was logging into my gnome desktop, I don't normally use evolution so it is unconfigured, but is being launced when I log in for some reason, and crashing immediately. after installing debug libs: --------------------------------------------------------- Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 52957184 vsize: 52957184 resident: 9560064 share: 8044544 rss: 9560064 rss_rlim: 4294967295 CPU usage: start_time: 1201117505 rtime: 6 utime: 4 stime: 2 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/bug-buddy/evolution-alarm-notify' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb689a6b0 (LWP 10157)] [New Thread 0xb6630b90 (LWP 10179)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 186532
Thread 1 (Thread 0xb689a6b0 (LWP 10157))
----------- .xsession-errors --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 --------------------------------------------------
could be a dup of bug 348149
Nope, it isn't that. I dont remember the bug, but alarm notify starts and crashes. It is the dupe of that bug.
Yup, please update to 2.12 or better, this has been fixed there. *** This bug has been marked as a duplicate of 273699 ***