Bug 381079 – crash in Movie Player: Happened when playing a ...

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 381079 - crash in Movie Player: Happened when playing a ...


Summary:	crash in Movie Player: Happened when playing a ...


Status:	RESOLVED INCOMPLETE

Product:	totem
Classification:	Core
Component:	general
Version:	2.16.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:	2006-11-30 22:50 UTC by Oumar Aziz OUATTARA
Modified:	2007-01-13 02:50 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description Oumar Aziz OUATTARA 2006-11-30 22:50:44 UTC

Version: 2.16.2

What were you doing when the application crashed?
Happened when playing a .wmv video file with gstreamer video ouput set to SDL.

Another bug is happening when it 's set to "X windows (no Xv)


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 262262784 vsize: 0 resident: 262262784 share: 0 rss: 110235648 rss_rlim: 0
CPU usage: start_time: 1164921142 rtime: 0 utime: 195258 stime: 0 cutime:176199 cstime: 0 timeout: 19059 it_real_value: 0 frequency: 4

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226799440 (LWP 16541)]
[New Thread -1362101344 (LWP 20014)]
[New Thread -1426064480 (LWP 20012)]
[New Thread -1314608224 (LWP 20009)]
[New Thread -1331532896 (LWP 19986)]
[New Thread -1306182752 (LWP 19984)]
[New Thread -1279276128 (LWP 19981)]
[New Thread -1267278944 (LWP 19980)]
[New Thread -1252549728 (LWP 19979)]
[New Thread -1323140192 (LWP 19978)]
[New Thread -1297364064 (LWP 19977)]
[New Thread -1348338784 (LWP 19976)]
[New Thread -1339946080 (LWP 19975)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 90674

Thread 13 (Thread -1339946080 (LWP 19975))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 ??
from /usr/lib/libgthread-2.0.so.0
#10 ??
from /usr/lib/libgthread-2.0.so.0
#11 ??
#12 ??
from /usr/lib/libgthread-2.0.so.0
#13 ??
from /usr/lib/libgthread-2.0.so.0
#14 ??
#15 ??
from /usr/lib/libgthread-2.0.so.0
#16 ??
#17 ??
from /usr/lib/libgthread-2.0.so.0
#18 ??
#19 ??

Comment 1 Baptiste Mille-Mathias 2006-12-03 23:36:01 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

Comment 2 Oumar Aziz OUATTARA 2006-12-04 19:04:37 UTC

I reproduced the bug and here is a 5Mb attachment ^^

http://bilfous.free.fr/Datas/_usr_bin_totem.1000.crash.gz

Comment 3 André Klapper 2007-01-12 03:22:42 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://www.gnome.org/projects/totem/#bugs for more information on how to do so.
Thanks in advance!

Comment 4 Bruno Boaventura 2007-01-13 02:50:13 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!