GNOME Bugzilla – Bug 503293
crash in Movie Player: Queria reproducir una pe...
Last modified: 2007-12-13 06:38:34 UTC
Version: 2.18.3 What were you doing when the application crashed? Queria reproducir una pelicula dvd Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 111468544 vsize: 111468544 resident: 32849920 share: 21053440 rss: 32849920 rss_rlim: 4294967295 CPU usage: start_time: 1197481189 rtime: 83 utime: 76 stime: 7 cutime:3 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 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 -1208563088 (LWP 3595)] [New Thread -1268958320 (LWP 3603)] [New Thread -1258468464 (LWP 3602)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 181685
Thread 2 (Thread -1268958320 (LWP 3603))
----------- .xsession-errors --------------------- Resource id: 0x340006a X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x340806a QClipboard::setData: Cannot set X11 selection owner for PRIMARY QClipboard::setData: Cannot set X11 selection owner for PRIMARY QClipboard::setData: Cannot set X11 selection owner for PRIMARY QClipboard::setData: Cannot set X11 selection owner for PRIMARY QClipboard::setData: Cannot set X11 selection owner for PRIMARY X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x1600007 JACK tmpdir identified as [/dev/shm] --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 434996 ***