GNOME Bugzilla – Bug 512017
crash in Tasks:
Last modified: 2008-02-14 04:06:04 UTC
Version: 2.10 What were you doing when the application crashed? 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.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: marble-ice Icon Theme: Suede2 Memory status: size: 143929344 vsize: 143929344 resident: 11169792 share: 6475776 rss: 11169792 rss_rlim: 4294967295 CPU usage: start_time: 1201256031 rtime: 1507 utime: 1362 stime: 145 cutime:3 cstime: 3 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 -1208199456 (LWP 3868)] [New Thread -1280406640 (LWP 3967)] [New Thread -1251755120 (LWP 3965)] [New Thread -1219859568 (LWP 3926)] (no debugging symbols found) 0x00619402 in __kernel_vsyscall ()
+ Trace 186744
Thread 1 (Thread -1208199456 (LWP 3868))
----------- .xsession-errors (38 sec old) --------------------- ERROR: Couldn't parse info from xml.weather.yahoo.com ERROR: Couldn't parse info from xml.weather.yahoo.com ERROR: Couldn't parse info from xml.weather.yahoo.com ERROR: Couldn't parse info from xml.weather.yahoo.com ERROR: Couldn't parse info from xml.weather.yahoo.com ERROR: Couldn't parse info from xml.weather.yahoo.com ERROR: Couldn't parse info from xml.weather.yahoo.com ERROR: Couldn't parse info from xml.weather.yahoo.com 0 - PLACE 0 0 | 1110x856 ERROR: Couldn't parse info from xml.weather.yahoo.com ERROR: Couldn't parse info from xml.weather.yahoo.com ERROR: Couldn't parse info from xml.weather.yahoo.com ERROR: Couldn't parse info from xml.weather.yahoo.com ERROR: Couldn't parse info from xml.weather.yahoo.com ERROR: Couldn't parse info from xml.weather.yahoo.com --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 431396 ***