GNOME Bugzilla – Bug 472949
crash in Tasks: Nothing. Evolution must ...
Last modified: 2007-10-07 17:03:34 UTC
Version: 2.10 What were you doing when the application crashed? Nothing. Evolution must have been checking my mail in the background. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 181575680 vsize: 181575680 resident: 82329600 share: 52801536 rss: 82329600 rss_rlim: 4294967295 CPU usage: start_time: 1188721487 rtime: 2936 utime: 2727 stime: 209 cutime:20 cstime: 11 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (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 -1208404256 (LWP 3913)] [New Thread -1426093168 (LWP 16562)] [New Thread -1241928816 (LWP 4188)] [New Thread -1260393584 (LWP 4186)] [New Thread -1249903728 (LWP 3949)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 159920
Thread 2 (Thread -1426093168 (LWP 16562))
----------- .xsession-errors (27928 sec old) --------------------- DEBUG: CXWindowsClipboard.cpp,512: available targets: TIMESTAMP (273), TARGETS (272), MULTIPLE (269), text/html (364), text/_moz_htmlcontext (514), text/_moz_htmlinfo (515), UTF8_STRING (238), COMPO DEBUG: CXWindowsClipboard.cpp,555: added format 2 for target text/html (364) (424 bytes) DEBUG: CXWindowsClipboard.cpp,555: added format 0 for target UTF8_STRING (238) (47 bytes) DEBUG: CXWindowsClipboard.cpp,348: close clipboard 1 INFO: CScreen.cpp,98: entering screen INFO: CScreen.cpp,116: leaving screen DEBUG: CXWindowsClipboard.cpp,313: open clipboard 0 DEBUG: CXWindowsClipboard.cpp,493: ICCCM fill clipboard 0 DEBUG: CXWindowsClipboard.cpp,512: available targets: TIMESTAMP (273), TARGETS (272), MULTIPLE (269), UTF8_STRING (238), COMPOUND_TEXT (424), TEXT (423), STRING (31) DEBUG: CXWindowsClipboard.cpp,555: added format 0 for target UTF8_STRING (238) (154 bytes) DEBUG: CXWindowsClipboard.cpp,348: close clipboard 0 DEBUG: CXWindowsClipboard.cpp,313: open clipboard 1 DEBUG: CXWindowsClipboard.cpp,493: ICCCM fill clipboard 1 DEBUG: CXWindowsClipboard.cpp,512: available targets: TIMESTAMP (273), TARGETS (272), MULTIPLE (269), text/html (364), text/_moz_htmlcontext (514), text/_moz_htmlinfo (515), UTF8_STRING (238), COMPO ...Too much output, ignoring rest... --------------------------------------------------
Thanks for taking the time to report this bug. I know, you have filed several bugs and you say, you have debug packages installed. However, 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. (rule of thumb: the more question marks are in the stacktrace, the less debug symbols could be found and it's actually essential for us, to get especially debug symbols for evolution libraries like here:
+ Trace 160836
Maybe you should report downstream, that you are not able to produce stracktraces. However, if you did not install debug packages at the time of the crasher and can reproduce this crash, you maybe could try to get a good trace and post it here.
[oli@ascension ~]$ rpm -qa | grep debuginfo pango-debuginfo-1.16.4-1.fc7 gtk2-debuginfo-2.10.11-7.fc7 wxGTK-debuginfo-2.8.3-2.fc7 gtkhtml3-debuginfo-3.14.1-1.fc7 glibc-debuginfo-common-2.6-3 glibc-debuginfo-2.6-3 evolution-debuginfo-2.10.1-4.fc7 evolution-data-server-debuginfo-1.10.1-1.fc7 glib-debuginfo-1.2.10-26.fc7 glib2-debuginfo-2.12.11-1.fc7 Heh yes, I'm kinda swimming in fc7 crash bugs here - I don't know how the developers and bug triagers handle it... Am I missing any debuginfo packages that we need to sort this out? If I'm missing some, let me know. I'm chasing up the eds vs. eds-debuginfo versioning issue now.
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 460409 ***