GNOME Bugzilla – Bug 447743
crash in Evolution: nothing, I was using ano...
Last modified: 2008-01-31 22:48:21 UTC
What were you doing when the application crashed? nothing, I was using another application Distribution: Debian lenny/sid Gnome Release: 2.18.2 2007-05-28 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.21-1-686 #1 SMP Sat May 26 16:14:59 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Gorilla Icon Theme: Gorilla Memory status: size: 41025536 vsize: 41025536 resident: 14331904 share: 8826880 rss: 14331904 rss_rlim: 4294967295 CPU usage: start_time: 1181872432 rtime: 291 utime: 231 stime: 60 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/bug-buddy/evolution-exchange-storage' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1233458992 (LWP 5071)] [New Thread -1234130032 (LWP 5073)] (no debugging symbols found) 0xb707cb11 in ?? () from /lib/libpthread.so.0
+ Trace 141096
----------- .xsession-errors (657 sec old) --------------------- Window manager warning: Property _NET_WM_ICON_NAME on window 0x2e020a9 contained invalid UTF-8 (gnome-panel:30088): Wnck-WARNING **: Property _NET_WM_NAME contained invalid UTF-8 (gnome-panel:30088): Wnck-WARNING **: Property _NET_WM_ICON_NAME contained invalid UTF-8 Window manager warning: Property _NET_WM_NAME on window 0x2e0270a contained invalid UTF-8 Window manager warning: Property _NET_WM_ICON_NAME on window 0x2e0270a contained invalid UTF-8 (gnome-panel:30088): Wnck-WARNING **: Property _NET_WM_NAME contained invalid UTF-8 (gnome-panel:30088): Wnck-WARNING **: Property _NET_WM_ICON_NAME contained invalid UTF-8 --------------------------------------------------
*** Bug 447745 has been marked as a duplicate of this bug. ***
*** Bug 447776 has been marked as a duplicate of this bug. ***
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
*** Bug 448035 has been marked as a duplicate of this bug. ***
*** Bug 448631 has been marked as a duplicate of this bug. ***
okay below is a slightly better stack trace. I'm still working on getting it to use the files in /usr/lib/debug. hmm.
+ Trace 143748
Thread 1 (Thread -1233897264 (LWP 12259))
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 420503 ***