Bug 500840 – crash in Movie Player: changing the video posit...

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 500840 - crash in Movie Player: changing the video posit...


Summary:	crash in Movie Player: changing the video posit...


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-12-01 10:58 UTC by rajivranjan
Modified:	2007-12-01 16:42 UTC

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

Description rajivranjan 2007-12-01 10:58:17 UTC

Version: 2.18.3

What were you doing when the application crashed?
changing the video position by using slide bar


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

System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 185499648 vsize: 185499648 resident: 50810880 share: 22994944 rss: 50810880 rss_rlim: 4294967295
CPU usage: start_time: 1196489354 rtime: 9668 utime: 9241 stime: 427 cutime:4 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 -1208796560 (LWP 18151)]
[New Thread -1235104880 (LWP 19275)]
[New Thread -1292485744 (LWP 18165)]
[New Thread -1281995888 (LWP 18164)]
[New Thread -1271506032 (LWP 18163)]
[New Thread -1261016176 (LWP 18162)]
[New Thread -1250526320 (LWP 18161)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 180302

Thread 7 (Thread -1250526320 (LWP 18161))

#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 ??
from /usr/lib/libgstreamer-0.10.so.0
#13 gst_pad_push
from /usr/lib/libgstreamer-0.10.so.0
#14 ??
from /usr/lib/gstreamer-0.10/libgstcoreelements.so
#15 ??
from /usr/lib/libgstreamer-0.10.so.0
#16 gst_pad_push
from /usr/lib/libgstreamer-0.10.so.0
#17 ??
from /usr/lib/libgstreamer-0.10.so.0
#18 ??
from /usr/lib/libgstreamer-0.10.so.0
#19 gst_pad_push
from /usr/lib/libgstreamer-0.10.so.0
#20 ??
from /usr/lib/libgstbase-0.10.so.0
#21 ??
from /usr/lib/libgstreamer-0.10.so.0
#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 (10 sec old) ---------------------
  Major opcode:  19
  Minor opcode:  0
  Resource id:  0x4a00007
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  19
  Minor opcode:  0
  Resource id:  0x208430c
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  19
  Minor opcode:  0
  Resource id:  0x200006a
QClipboard::setData: Cannot set X11 selection owner for CLIPBOARD
** ERROR **: file gstasfdemux.c: line 498 (gst_asf_demux_get_var_length): assertion failed: (*p_size >= 1)
aborting...
--------------------------------------------------

Comment 1 Philip Withnall 2007-12-01 16:42:14 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 ***