After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 522671 - crash in Movie Player:
crash in Movie Player:
Status: RESOLVED DUPLICATE of bug 449658
Product: totem
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2008-03-15 20:56 UTC by wout
Modified: 2008-03-15 23:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description wout 2008-03-15 20:56:33 UTC
Version: 2.20.3

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.0 2008-03-14 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.24.3 #1 PREEMPT Thu Mar 13 21:37:29 CET 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glider
Icon Theme: gnome

Memory status: size: 160976896 vsize: 160976896 resident: 43241472 share: 21962752 rss: 43241472 rss_rlim: 4294967295
CPU usage: start_time: 1205614585 rtime: 95 utime: 86 stime: 9 cutime:0 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 0xb6d68720 (LWP 8652)]
[New Thread 0xb16a8b90 (LWP 8663)]
[New Thread 0xb21b9b90 (LWP 8661)]
[New Thread 0xb29b9b90 (LWP 8660)]
[New Thread 0xb3386b90 (LWP 8659)]
[New Thread 0xb3f6fb90 (LWP 8658)]
[New Thread 0xb476fb90 (LWP 8657)]
[New Thread 0xb4fdfb90 (LWP 8656)]
[New Thread 0xb6014b90 (LWP 8655)]
(no debugging symbols found)
0xb71ffc1d in poll () from /lib/libc.so.6

Thread 4 (Thread 0xb29b9b90 (LWP 8660))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 __assert_fail
    from /lib/libc.so.6
  • #8 ??
    from /usr/lib/libpulse.so.0
  • #9 ??
    from /usr/lib/libpulse.so.0
  • #10 ??
    from /usr/lib/libpulse.so.0
  • #11 ??
  • #12 ??
    from /usr/lib/libpulse.so.0
  • #13 ??
  • #14 ??
    from /usr/lib/libpulse.so.0
  • #15 ??
  • #16 pa_threaded_mainloop_unlock
    from /usr/lib/libpulse.so.0


----------- .xsession-errors ---------------------
==========================================================================
[AO OSS] audio_setup: Can't open audio device /dev/dsp: Device or resource busy
[AO_ALSA] alsa-lib: pcm_hw.c:1132:(snd_pcm_hw_open) open /dev/snd/pcmC0D0p failed: Device or resource busy
[AO_ALSA] alsa-lib: pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave
[AO_ALSA] Playback open error: Device or resource busy
[AO ESD] latency: [server: 0.28s, net: 0.00s] (adjust 0.28s)
AO: [esd] 44100Hz 2ch s16le (2 bytes per sample)
Video: no video
Starting playback...
A:  -0.0 (unknown) of 28052.6 ( 7:47:32.5) ??,?%                                
A:   0.2 (00.1) of 28052.6 ( 7:47:32.5) ??,?%                                   
A:   0.3 (00.3) of 28052.6 ( 7:47:32.5
A:   2.8 (02.7) of 28052.6 ( 7:47:32.5)  1.8%                                   
A:   2.9 (02.9) of 28052.6 ( 7:47:32.5)  1.7%                                   
A:   3.1 (03.0) of 28052.6 ( 7:47:32.5
A:   3.3 (03.2) of 28052.6 ( 7:47:32.5)  1.9%                                   
Exiting... (Quit)
totem: pulsecore/mutex-posix.c:98: pa_mutex_unlock: Controletest 'pthread_mutex_unlock(&m->mutex) == 0' faalt.
--------------------------------------------------
Comment 1 Philip Withnall 2008-03-15 23:22:08 UTC
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 449658 ***