GNOME Bugzilla – Bug 462931
crash in Movie Player: streaming audio
Last modified: 2007-08-03 18:41:55 UTC
Version: 2.16.5 What were you doing when the application crashed? streaming audio Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.20-1.2933.fc6 #1 SMP Mon Mar 19 10:42:48 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 129921024 vsize: 0 resident: 129921024 share: 0 rss: 24338432 rss_rlim: 0 CPU usage: start_time: 1186088790 rtime: 0 utime: 76 stime: 0 cutime:69 cstime: 0 timeout: 7 it_real_value: 0 frequency: 2 Backtrace was generated from '/usr/bin/totem' (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 -1208256816 (LWP 6637)] [New Thread -1296049264 (LWP 6655)] [New Thread -1285559408 (LWP 6654)] [New Thread -1275069552 (LWP 6653)] [New Thread -1262974064 (LWP 6652)] [New Thread -1246770288 (LWP 6651)] [New Thread -1236280432 (LWP 6650)] (no debugging symbols found) 0x0047f402 in __kernel_vsyscall ()
+ Trace 152418
Thread 5 (Thread -1262974064 (LWP 6652))
----------- .xsession-errors --------------------- ** (eggcups:3025): WARNING **: IPP request failed with status 1030 ** (eggcups:3025): WARNING **: IPP request failed with status 1030 ** (eggcups:3025): WARNING **: IPP request failed with status 1030 ** (eggcups:3025): WARNING **: IPP request failed with status 1030 ** (eggcups:3025): WARNING **: IPP request failed with status 1030 ** (eggcups:3025): WARNING **: IPP request failed with status 1030 ** (eggcups:3025): WARNING **: IPP request failed with status 1030 ** (eggcups:3025): WARNING **: IPP request failed with status 1030 --------------------------------------------------
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 365501 ***