GNOME Bugzilla – Bug 509754
crash in Tasks: Estaba cambiendo de foco...
Last modified: 2008-01-25 15:29:16 UTC
Version: 2.10 What were you doing when the application crashed? Estaba cambiendo de foco entre la ventana de redacción de un mail y la principal de evolution Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 20:27:10 EST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 613572608 vsize: 613572608 resident: 56913920 share: 38055936 rss: 56913920 rss_rlim: 18446744073709551615 CPU usage: start_time: 1200431979 rtime: 791 utime: 729 stime: 62 cutime:46 cstime: 19 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912518200400 (LWP 2815)] [New Thread 1105209680 (LWP 3093)] [New Thread 1126455632 (LWP 2840)] [New Thread 1115699536 (LWP 2834)] (no debugging symbols found) 0x000000384600d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 185488
Thread 1 (Thread 46912518200400 (LWP 2815))
----------- .xsession-errors --------------------- (evolution:2815): libebook-WARNING **: invalid escape, passing it through (evolution:2815): libebook-WARNING **: invalid escape, passing it through (evolution:2815): libebook-WARNING **: invalid escape, passing it through (evolution:2815): libebook-WARNING **: invalid escape, passing it through (evolution:2815): libebook-WARNING **: invalid escape, passing it through (evolution:2815): libebook-WARNING **: invalid escape, passing it through (evolution:2815): libebook-WARNING **: invalid escape, passing it through warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff737fd000 --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 458670 ***