GNOME Bugzilla – Bug 485366
crash in Evolution: Checking emails, letting...
Last modified: 2007-12-29 19:37:30 UTC
What were you doing when the application crashed? Checking emails, letting filters auto-sort... Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Simple Icon Theme: gnome Memory status: size: 219795456 vsize: 219795456 resident: 167665664 share: 9404416 rss: 167665664 rss_rlim: 4294967295 CPU usage: start_time: 1192016257 rtime: 1148 utime: 1022 stime: 126 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/bug-buddy/evolution-exchange-storage' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb66b16b0 (LWP 20594)] [New Thread 0xb660cb90 (LWP 20596)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 169236
----------- .xsession-errors --------------------- (gnome-panel:3610): Wnck-WARNING **: Unhandled action type (nil) (gnome-panel:3610): Wnck-WARNING **: Unhandled action type (nil) (gnome-panel:3610): Wnck-WARNING **: Unhandled action type (nil) (gnome-panel:3610): Wnck-WARNING **: Unhandled action type (nil) (gnome-panel:3610): Wnck-WARNING **: Unhandled action type (nil) (gnome-panel:3610): Wnck-WARNING **: Unhandled action type (nil) (gnome-panel:3610): Wnck-WARNING **: Unhandled action type (nil) (gnome-panel:3610): Wnck-WARNING **: Unhandled action type (nil) --------------------------------------------------
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! [1] debugging 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
I've installed (dpkg -l | grep dbg): ii evolution-data-server-dbg 1.10.3-1 ii evolution-dbg 2.10.3-1 ii evolution-exchange-dbg 2.10.3.dfsg-1 ii libglib2.0-0-dbg 2.14.1-5 ii libgnomeui-0-dbg 2.18.1-2 ii libgnomevfs2-0-dbg 1:2.20.0-1 ii libgtk2.0-0-dbg 2.10.13-1 ii libgtkhtml3.14-dbg 3.14.3-1 ii libpango1.0-0-dbg 1.18.2-1 .. and got the blow listing. I then added: ii libglib1.2-dbg 1.2.10-19 ... although the dependencies say it should be using libglib2, and the debug says it's using /usr/lib/libglib-2, I figured... what the hey. There's still untagged responses in there. I'm pretty sure I've rebooted since I installed libglib2.0-0-dbg, but I'll make sure to reboot again now, and see what happens. If there's something else (eg libgnome), I think I'll have to build a debug package. Note also that this usually happens on monday, when there's a lot of mail to sort; I'm not sure if that's predictable or not, or if that helps. If all this still isn't enough, some suggestions of what I've missed would be appreciated ;-] ----- Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Simple Icon Theme: gnome Memory status: size: 226652160 vsize: 226652160 resident: 173699072 share: 9396224 rss: 173699072 rss_rlim: 4294967295 CPU usage: start_time: 1193052805 rtime: 1405 utime: 1279 stime: 126 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/bug-buddy/evolution-exchange-storage' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb661a6b0 (LWP 13328)] [New Thread 0xb6575b90 (LWP 13330)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 171912
Thread 1 (Thread 0xb661a6b0 (LWP 13328))
----------- .xsession-errors --------------------- (gnome-panel:19646): Wnck-WARNING **: Unhandled action type (nil) (gnome-panel:19646): Wnck-WARNING **: Unhandled action type (nil) (gnome-panel:19646): Wnck-WARNING **: Unhandled action type (nil) (gnome-panel:19646): Wnck-WARNING **: Unhandled action type (nil) (gnome-panel:19646): Wnck-WARNING **: Unhandled action type (nil) (gnome-panel:19646): Wnck-WARNING **: Unhandled action type (nil) (gnome-panel:19646): Wnck-WARNING **: Unhandled action type (nil) (gnome-panel:19646): Wnck-WARNING **: Unhandled action type (nil) --------------------------------------------------
Additional information showed up after rebooting, and, presumably, actually using the debugging version of lib-glib or something. ;-] This may or may not be the same issue; it looks like it, and it happens at much the same time, but since the output in the original and second are missing some details, it's difficult to tell. Anyway: More debug info (with redundant start and finish, identical to listed above, removed; the gnome-panel warnings had a different PID, but other than that...): ----- Memory status: size: 230715392 vsize: 230715392 resident: 177676288 share: 9404416 rss: 177676288 rss_rlim: 4294967295 CPU usage: start_time: 1193662940 rtime: 973 utime: 842 stime: 131 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/bug-buddy/evolution-exchange-storage' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb66296b0 (LWP 26876)] [New Thread 0xb6584b90 (LWP 26878)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 173669
Thread 1 (Thread 0xb66296b0 (LWP 26876))
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 457291 ***