GNOME Bugzilla – Bug 490649
crash in Tasks:
Last modified: 2007-10-26 23:11:02 UTC
Version: 2.10 What were you doing when the application crashed? 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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: OSX Memory status: size: 185921536 vsize: 185921536 resident: 46653440 share: 33525760 rss: 46653440 rss_rlim: 4294967295 CPU usage: start_time: 1193432793 rtime: 103 utime: 88 stime: 15 cutime:0 cstime: 1 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 15244)] [New Thread -1348494448 (LWP 15273)] [New Thread -1338004592 (LWP 15272)] [New Thread -1315964016 (LWP 15270)] [New Thread -1240265840 (LWP 15262)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 173125
Thread 1 (Thread -1208199456 (LWP 15244))
----------- .xsession-errors (1643474 sec old) --------------------- ** (realplay.bin:5409): WARNING **: Superbuffer pos (8041675) > maxPosition(8032000) ** (realplay.bin:5409): WARNING **: Superbuffer pos (8041862) > maxPosition(8032000) ** (realplay.bin:5409): WARNING **: Superbuffer pos (8042061) > maxPosition(8032000) ** (realplay.bin:5409): WARNING **: Superbuffer pos (8042269) > maxPosition(8032000) ** (realplay.bin:5409): WARNING **: Superbuffer pos (8042464) > maxPosition(8032000) ** (realplay.bin:5409): WARNING **: Superbuffer pos (8042671) > maxPosition(8032000) ** (realplay.bin:5409): WARNING **: Superbuffer pos (8042870) > maxPosition(8032000) ...Too much output, ignoring rest... --------------------------------------------------
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 364700 ***