Bug 477515 – crash in Movie Player: changed position in wmv ...

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 477515 - crash in Movie Player: changed position in wmv ...


Summary:	crash in Movie Player: changed position in wmv ...


Status:	RESOLVED DUPLICATE of bug 336370

Product:	totem
Classification:	Core
Component:	general
Version:	2.18.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:	2007-09-16 15:51 UTC by Martin Jürgens
Modified:	2007-09-16 19:22 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description Martin Jürgens 2007-09-16 15:51:34 UTC

Version: 2.18.3

What were you doing when the application crashed?
changed position in wmv video.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 169906176 vsize: 169906176 resident: 58748928 share: 39219200 rss: 58748928 rss_rlim: 4294967295
CPU usage: start_time: 1189956951 rtime: 154 utime: 139 stime: 15 cutime:7 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208841616 (LWP 19940)]
[New Thread -1299186800 (LWP 19955)]
[New Thread -1283388528 (LWP 19953)]
[New Thread -1272898672 (LWP 19950)]
[New Thread -1262408816 (LWP 19949)]
[New Thread -1251918960 (LWP 19948)]
[New Thread -1241429104 (LWP 19947)]
[New Thread -1225225328 (LWP 19945)]
0x00110402 in __kernel_vsyscall ()

+ Trace 163348

Thread 7 (Thread -1241429104 (LWP 19947))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/libc.so.6
#6 abort
from /lib/libc.so.6
#7 g_logv
from /lib/libglib-2.0.so.0
#8 g_log
from /lib/libglib-2.0.so.0
#9 g_assert_warning
from /lib/libglib-2.0.so.0
#10 ??
from /usr/lib/gstreamer-0.10/libgstasf.so
#11 ??
from /usr/lib/gstreamer-0.10/libgstasf.so
#12 gst_pad_chain_unchecked
at gstpad.c line 3451
#13 gst_pad_push
at gstpad.c line 3617
#14 gst_type_find_element_chain
at gsttypefindelement.c line 570
#15 gst_pad_chain_unchecked
at gstpad.c line 3451
#16 gst_pad_push
at gstpad.c line 3617
#17 gst_proxy_pad_do_chain
at gstghostpad.c line 191
#18 gst_pad_chain_unchecked
at gstpad.c line 3451
#19 gst_pad_push
at gstpad.c line 3617
#20 gst_base_src_loop
at gstbasesrc.c line 1770
#21 gst_task_func
at gsttask.c line 192
#22 ??
from /lib/libglib-2.0.so.0
#23 ??
from /lib/libglib-2.0.so.0
#24 start_thread
from /lib/libpthread.so.0
#25 clone
from /lib/libc.so.6



----------- .xsession-errors (4504 sec old) ---------------------
found key:VIDEO_OPTIONS_EFFECTS_QUALITY
found key:VIDEO_OPTIONS_ENV_MAPPING
found key:VIDEO_OPTIONS_LIGHTMAPS
found key:VIDEO_OPTIONS_SHADOWS
found key:VIDEO_OPTIONS_TEXTURE_QUALITY
found key:VIDEO_OPTIONS_VIEWDISTANCE
found key:VIDEO_OPTIONS_RENDER_WITH_SPAWN
found key:SOUND_OPTIONS_DISABLE_ALL
found key:SOUND_OPTIONS_MASTER_VOLUME
found key:SOUND_OPTIONS_MUSIC_ON_OFF
found key:SOUND_OPTIONS_SOUND_DETAIL
found key:SOUND_OPTIONS_LOCALIZED_VOICE
found key:CONFIRMATION_QUIT
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Philip Withnall 2007-09-16 19:22:34 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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