Bug 525080 – crash in Movie Player (Xine): Nothing

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 525080 - crash in Movie Player (Xine): Nothing


Summary:	crash in Movie Player (Xine): Nothing


Status:	RESOLVED DUPLICATE of bug 449658

Product:	totem
Classification:	Core
Component:	general
Version:	2.20.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	General Totem maintainer(s)
QA Contact:	General Totem maintainer(s)

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-03-30 07:32 UTC by erghezi
Modified:	2008-03-30 08:22 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description erghezi 2008-03-30 07:32:59 UTC

Version: 2.20.3

What were you doing when the application crashed?
Nothing


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: ClearlooksClassic
Icon Theme: UbuntuStudio

Memory status: size: 149426176 vsize: 149426176 resident: 33927168 share: 15605760 rss: 33927168 rss_rlim: 4294967295
CPU usage: start_time: 1206862450 rtime: 148 utime: 128 stime: 20 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/totem-xine'

(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 0xb6d70720 (LWP 6208)]
[New Thread 0xb160db90 (LWP 6217)]
[New Thread 0xb20c0b90 (LWP 6216)]
[New Thread 0xb28c1b90 (LWP 6215)]
[New Thread 0xb328fb90 (LWP 6214)]
[New Thread 0xb3e79b90 (LWP 6213)]
[New Thread 0xb467ab90 (LWP 6212)]
[New Thread 0xb4ed6b90 (LWP 6211)]
[New Thread 0xb5f3db90 (LWP 6210)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 193665

Thread 4 (Thread 0xb28c1b90 (LWP 6215))

#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 ---------------------
(gecko:4436): Gtk-CRITICAL **: gtk_text_buffer_get_insert: assertion `GTK_IS_TEXT_BUFFER (buffer)' failed
(gecko:4436): Gtk-CRITICAL **: gtk_text_buffer_get_iter_at_mark: assertion `GTK_IS_TEXT_MARK (mark)' failed
(gecko:4436): Gtk-CRITICAL **: _gtk_text_layout_get_block_cursor: assertion `layout != NULL' failed
(gecko:4436): Gtk-CRITICAL **: gtk_text_layout_get_cursor_locations: assertion `layout != NULL' failed
(gecko:4436): Gdk-CRITICAL **: gdk_window_invalidate_rect: assertion `window != NULL' failed
(gecko:4436): Gdk-CRITICAL **: gdk_window_invalidate_rect: assertion `window != NULL' failed
totem-xine: pulsecore/mutex-posix.c:98: pa_mutex_unlock: Assertion `pthread_mutex_unlock(&m->mutex) == 0' failed.
totem-xine: pulsecore/mutex-posix.c:98: pa_mutex_unlock: Assertion `pthread_mutex_unlock(&m->mutex) == 0' failed.
totem-xine: pulsecore/mutex-posix.c:98: pa_mutex_unlock: Assertion `pthread_mutex_unlock(&m->mutex) == 0' failed.
--------------------------------------------------

Comment 1 Philip Withnall 2008-03-30 08:22:34 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 ***