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 523472 - crash in Movie Player: I was trying to listen t...
crash in Movie Player: I was trying to listen t...
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-19 21:49 UTC by chals
Modified: 2008-03-19 22:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description chals 2008-03-19 21:49:19 UTC 
Version: 2.20.3

What were you doing when the application crashed?
I was trying to listen to an mp3 song


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 Sun Feb 10 20:20:49 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 141369344 vsize: 141369344 resident: 30707712 share: 12812288 rss: 30707712 rss_rlim: 4294967295
CPU usage: start_time: 1205966814 rtime: 73 utime: 64 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6df76b0 (LWP 6942)]
[New Thread 0xb14e1b90 (LWP 6952)]
[New Thread 0xb218cb90 (LWP 6951)]
[New Thread 0xb298db90 (LWP 6950)]
[New Thread 0xb335bb90 (LWP 6949)]
[New Thread 0xb3f45b90 (LWP 6948)]
[New Thread 0xb4788b90 (LWP 6947)]
[New Thread 0xb4fe5b90 (LWP 6946)]
[New Thread 0xb6092b90 (LWP 6945)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 192894

Thread 4 (Thread 0xb298db90 (LWP 6950))

  • #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 ---------------------
ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave
ALSA snd_pcm_open error: Device or resource busy
totem: pulsecore/mutex-posix.c:98: pa_mutex_unlock: Assertion `pthread_mutex_unlock(&m->mutex) == 0' failed.
(bug-buddy:6919): libebook-WARNING **: Can't find installed BookFactories
(bug-buddy:6919): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
ALSA lib pcm_dmix.c:996:(snd_pcm_dmix_open) unable to open slave
ALSA snd_pcm_open error: Device or resource busy
totem: pulsecore/mutex-posix.c:98: pa_mutex_unlock: Assertion `pthread_mutex_unlock(&m->mutex) == 0' failed.
--------------------------------------------------
Comment 1 Philip Withnall 2008-03-19 22:38:03 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 ***