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 514198 - crash in Movie Player: conflict between gnome a...
crash in Movie Player: conflict between gnome a...
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-02-04 00:56 UTC by primeman_gold
Modified: 2008-02-04 06:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description primeman_gold 2008-02-04 00:56:04 UTC
Version: 2.20.3

What were you doing when the application crashed?
conflict between gnome audio events(esd) and totem

My solution:
"libesd-alsa0" package install(automatically "libesd0" package deleted)
reboot

-Mission accomplished-

ps:
why "libesd-alsa0" is not standard(typical?)?
  (sorry, my poor english...)


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: 167034880 vsize: 167034880 resident: 37388288 share: 15724544 rss: 37388288 rss_rlim: 4294967295
CPU usage: start_time: 1202086126 rtime: 99 utime: 90 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 0xb6e886b0 (LWP 6970)]
[New Thread 0xb102eb90 (LWP 6978)]
[New Thread 0xb1e06b90 (LWP 6977)]
[New Thread 0xb2607b90 (LWP 6976)]
[New Thread 0xb2fd5b90 (LWP 6975)]
[New Thread 0xb3bbfb90 (LWP 6974)]
[New Thread 0xb43c0b90 (LWP 6973)]
[New Thread 0xb4c15b90 (LWP 6972)]
[New Thread 0xb5c01b90 (LWP 6971)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 4 (Thread 0xb2607b90 (LWP 6976))

  • #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 ---------------------
A handler is already registered for the path starting with path[0] = "org"
A handler is already registered for the path starting with path[0] = "org"
A handler is already registered for the path starting with path[0] = "org"
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
No accelerated IMDCT transform found
totem: pulsecore/mutex-posix.c:98: pa_mutex_unlock: Assertion `pthread_mutex_unlock(&m->mutex) == 0' 실패.
--------------------------------------------------
Comment 1 Philip Withnall 2008-02-04 06:57:18 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 ***