GNOME Bugzilla – Bug 479387
crash in Movie Player: restart my pc
Last modified: 2007-09-23 08:49:58 UTC
Version: 2.18.3 What were you doing when the application crashed? restart my pc 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.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 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: 133910528 vsize: 133910528 resident: 43216896 share: 23486464 rss: 43216896 rss_rlim: 4294967295 CPU usage: start_time: 1190505932 rtime: 3274 utime: 3092 stime: 182 cutime:8 cstime: 1 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 -1208518032 (LWP 3533)] [New Thread -1299047536 (LWP 3573)] [New Thread -1259361392 (LWP 3538)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 164736
Thread 2 (Thread -1299047536 (LWP 3573))
----------- .xsession-errors (430 sec old) --------------------- Artist: Album: Year: Comment: Genre: Other ========================================================================== Opening audio decoder: [mp3lib] MPEG layer-2, layer-3 AUDIO: 44100 Hz, 2 ch, s16le, 128.0 kbit/9.07% (ratio: 16000->176400) Selected audio codec: [mp3] afm: mp3lib (mp3lib MPEG layer-2, layer-3) ========================================================================== AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample) Video: no video Starting playback... A: 0.0 (00.0) of 511.0 (08:31.0) ??,?% A: 0.0 (00.0) of 511.0 (08:31.0) ??,?% A: 0.1 (00.0) of 511.0 (08:31.0) ??, ...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 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 469349 ***