GNOME Bugzilla – Bug 381341
crash in Movie Player: Setting visualisation si...
Last modified: 2006-12-03 23:12:06 UTC
Version: 2.16.2 What were you doing when the application crashed? Setting visualisation size to 'Normal' 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.2849.fc6 #1 SMP Fri Nov 10 12:45:28 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled ----------- .xsession-errors --------------------- Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Max failures exceeded, exiting now ** (bug-buddy:4582): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 162013184 vsize: 0 resident: 162013184 share: 0 rss: 29696000 rss_rlim: 0 CPU usage: start_time: 1164979820 rtime: 0 utime: 2895 stime: 0 cutime:2598 cstime: 0 timeout: 297 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 -1208371504 (LWP 4051)] [New Thread 88837008 (LWP 4578)] [New Thread 78347152 (LWP 4058)] [New Thread 49867664 (LWP 4057)] [New Thread 39377808 (LWP 4056)] [New Thread 63466384 (LWP 4055)] [New Thread 104201104 (LWP 4054)] [New Thread 133430160 (LWP 4053)] [New Thread 26753936 (LWP 4052)] (no debugging symbols found) 0x0079d402 in __kernel_vsyscall ()
+ Trace 90873
Thread 1 (Thread -1208371504 (LWP 4051))
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 ***