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 453001 - crash in Movie Player: open file video
crash in Movie Player: open file video
Status: RESOLVED DUPLICATE of bug 453000
Product: totem
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2007-07-02 06:17 UTC by danieljucan
Modified: 2007-07-02 19:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description danieljucan 2007-07-02 06:17:07 UTC
Version: 2.18.2

What were you doing when the application crashed?
open file video


Distribution: Debian lenny/sid
Gnome Release: 2.18.2 2007-05-28 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.18-4-amd64 #1 SMP Mon Mar 26 11:36:53 CEST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: SphereCrystal

Memory status: size: 502075392 vsize: 502075392 resident: 46829568 share: 16343040 rss: 46829568 rss_rlim: 18446744073709551615
CPU usage: start_time: 1183281370 rtime: 123 utime: 108 stime: 15 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 47580796306048 (LWP 8262)]
[New Thread 1140881728 (LWP 8270)]
[New Thread 1132489024 (LWP 8269)]
[New Thread 1124096320 (LWP 8268)]
[New Thread 1115703616 (LWP 8267)]
[New Thread 1107310912 (LWP 8266)]
[New Thread 1098918208 (LWP 8265)]
[New Thread 1090525504 (LWP 8264)]
[New Thread 1082132800 (LWP 8263)]
(no debugging symbols found)
0x00002b46412dc927 in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib/libpthread.so.0

Thread 4 (Thread 1124096320 (LWP 8268))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib/libc.so.6
  • #4 abort
    from /lib/libc.so.6
  • #5 __assert_fail
    from /lib/libc.so.6
  • #6 pa_mutex_unlock
    from /usr/lib/libpulse.so.0
  • #7 ??
    from /usr/lib/xine/plugins/1.1.7/xineplug_ao_out_pulseaudio.so
  • #8 ??
    from /usr/lib/libxine.so.1
  • #9 ??
    from /usr/lib/libxine.so.1
  • #10 ??
    from /usr/lib/xine/plugins/1.1.7/xineplug_decode_mad.so
  • #11 ??
    from /usr/lib/libxine.so.1
  • #12 start_thread
    from /lib/libpthread.so.0
  • #13 clone
    from /lib/libc.so.6
  • #14 ??


----------- .xsession-errors ---------------------
AFD changed from -2 to -1
xine: pulsecore/mutex-posix.c:81: pa_mutex_unlock: Assertion `_r == 0' failed.
Avertisment al managerului de ferestre:Received a _NET_WM_MOVERESIZE message for 0x3000157 (Player muz); these messages lack timestamps and therefore suck.
Avertisment al managerului de ferestre:last_user_time (4120072864) is greater than comparison timestamp (2165104206).  This most likely represents a buggy client sending inaccurate timestamps in messa
Avertisment al managerului de ferestre:0x3200081 (Synaptic) appears to be one of the offending windows with a timestamp of 4120072864.  Working around...
totem: pulsecore/mutex-posix.c:81: pa_mutex_unlock: Assertion `_r == 0' failed.
(bug-buddy:8158): GLib-GObject-WARNING **: invalid uninstantiatable type `event-after' in cast to `GObject'
(bug-buddy:8158): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed
(bug-buddy:8158): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed
(bug-buddy:8158): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
totem: pulsecore/mutex-posix.c:81: pa_mutex_unlock: Assertion `_r == 0' failed.
--------------------------------------------------
Comment 1 Christian Kirbach 2007-07-02 19:48:09 UTC

*** This bug has been marked as a duplicate of 453000 ***