GNOME Bugzilla – Bug 370875
crash in Movie Player: configuring movie player
Last modified: 2006-12-10 17:15:11 UTC
Version: 2.16.2 What were you doing when the application crashed? configuring movie player Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:37:32 EDT 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled ----------- .xsession-errors --------------------- ** (eggcups:2484): WARNING **: IPP request failed with status 1030 Xlib: unexpected async reply (sequence 0xa)! ** Message: w 0 h 0 sidebar 0 ** Message: w 610 h 436 sidebar 190 ** Message: w 610 h 436 sidebar 190 ** Message: w 610 h 436 sidebar 190 closing gnome-mount 0.5 ** (totem:20825): WARNING **: Error checking whether the volume is a disc: No property volume.is_disc on device with id /org/freedesktop/Hal/devices/storage_model_GENERIC_DVD_DUAL_4XMax ** (bug-buddy:20857): WARNING **: Couldn't load icon for Movie Player ** (bug-buddy:20857): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 174960640 vsize: 0 resident: 174960640 share: 0 rss: 26058752 rss_rlim: 0 CPU usage: start_time: 1162617691 rtime: 0 utime: 5299 stime: 0 cutime:186 cstime: 0 timeout: 5113 it_real_value: 0 frequency: 0 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 -1208633648 (LWP 20825)] [New Thread 118164368 (LWP 20832)] [New Thread 71596944 (LWP 20831)] [New Thread 48036752 (LWP 20830)] [New Thread 37546896 (LWP 20829)] [New Thread 61107088 (LWP 20828)] [New Thread 86662032 (LWP 20827)] [New Thread 27057040 (LWP 20826)] (no debugging symbols found) 0x00132402 in __kernel_vsyscall ()
+ Trace 83079
Thread 1 (Thread -1208633648 (LWP 20825))
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 351181 ***
*** Bug 373635 has been marked as a duplicate of this bug. ***
*** Bug 375603 has been marked as a duplicate of this bug. ***
*** Bug 375425 has been marked as a duplicate of this bug. ***
*** Bug 381609 has been marked as a duplicate of this bug. ***
*** Bug 383366 has been marked as a duplicate of this bug. ***
*** Bug 383674 has been marked as a duplicate of this bug. ***