GNOME Bugzilla – Bug 470751
crash in Evolution: Retrieving email
Last modified: 2009-05-20 06:10:27 UTC
What were you doing when the application crashed? Retrieving email Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.18-4-amd64 #1 SMP Fri May 4 00:37:33 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Grand-Canyon Icon Theme: Smokey-Red Memory status: size: 442720256 vsize: 442720256 resident: 31223808 share: 18214912 rss: 31223808 rss_rlim: 18446744073709551615 CPU usage: start_time: 1188222628 rtime: 253 utime: 218 stime: 35 cutime:1 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution-2.10' (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 47277109954640 (LWP 3842)] [New Thread 1115703632 (LWP 3886)] [New Thread 1107310928 (LWP 3885)] [New Thread 1090525520 (LWP 3868)] [New Thread 1098918224 (LWP 3867)] [New Thread 1082132816 (LWP 3864)] (no debugging symbols found) 0x00002aff87d80c7f in waitpid () from /lib/libpthread.so.0
+ Trace 158228
Thread 1 (Thread 47277109954640 (LWP 3842))
----------- .xsession-errors (268 sec old) --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 OggS-SEEK: at 0 want 60408 got 51136 (diff-requested 60408) OggS-SEEK: at 60352 want 520 got 0 (diff-requested -59832) OggS-SEEK: at 0 want 78328 got 68160 (diff-requested 78328) OggS-SEEK: at 78400 want 520 got 0 (diff-requested -77880) --------------------------------------------------
You are running Debian sid? Please tell me which version of libxml2 you are using? 2.6.29.dfsg-1 or 2.6.30.dfsg-1
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.
Please feel free to reopen the bug if the problem still occurs with a newer version of GNOME 2.26.2 or later, thanks.