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 535140 - 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-05-27 19:00 UTC by ilfabrizio
Modified: 2008-05-28 06:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description ilfabrizio 2008-05-27 19:00:12 UTC
Version: 2.20.3

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 141275136 vsize: 141275136 resident: 27590656 share: 14524416 rss: 27590656 rss_rlim: 4294967295
CPU usage: start_time: 1211914805 rtime: 46 utime: 40 stime: 6 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6dac6b0 (LWP 25693)]
[New Thread 0xb21c5b90 (LWP 25700)]
[New Thread 0xb29c6b90 (LWP 25699)]
[New Thread 0xb3394b90 (LWP 25698)]
[New Thread 0xb3f7eb90 (LWP 25697)]
[New Thread 0xb47c1b90 (LWP 25696)]
[New Thread 0xb5020b90 (LWP 25695)]
[New Thread 0xb60bcb90 (LWP 25694)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 3 (Thread 0xb29c6b90 (LWP 25699))

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


----------- .xsession-errors ---------------------
Opening audio decoder: [mp3lib] MPEG layer-2, layer-3
AUDIO: 32000 Hz, 2 ch, s16le, 192.0 kbit/18.75% (ratio: 24000->128000)
Selected audio codec: [mp3] afm: mp3lib (mp3lib MPEG layer-2, layer-3)
==========================================================================
[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.8 (00.7) of 389.9 (06:29.8) ??,?%                                        
A:   0.8 (00.8) of 389.9 (06:29.8) ??,?%                                        
A:   1.0 (00.9) of 389.9 (06:29.8) ??,
Exiting... (Exit)
totem: pulsecore/mutex-posix.c:98: pa_mutex_unlock: Asserzione `pthread_mutex_unlock(&m->mutex) == 0' fallita.
--------------------------------------------------
Comment 1 Philip Withnall 2008-05-28 06:05:58 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 ***