Bug 521850 – crash in Movie Player: The movie was in pause. ...

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 521850 - crash in Movie Player: The movie was in pause. ...


Summary:	crash in Movie Player: The movie was in pause. ...


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:	2008-03-11 20:11 UTC by adrian15sgd
Modified:	2008-03-11 22:48 UTC

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

Description adrian15sgd 2008-03-11 20:11:42 UTC

Version: 2.18.3

What were you doing when the application crashed?
The movie was in pause. I was moving the cursor movie to see what happened later in the film.


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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 211660800 vsize: 211660800 resident: 63709184 share: 40677376 rss: 63709184 rss_rlim: 4294967295
CPU usage: start_time: 1205265969 rtime: 144 utime: 138 stime: 6 cutime:5 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 -1208198544 (LWP 3247)]
[New Thread -1349653616 (LWP 3256)]
[New Thread -1336960112 (LWP 3255)]
[New Thread -1326470256 (LWP 3254)]
[New Thread -1315980400 (LWP 3253)]
[New Thread -1305490544 (LWP 3252)]
[New Thread -1295000688 (LWP 3251)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 192117

Thread 7 (Thread -1295000688 (LWP 3251))

#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 ---------------------
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x1404016
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x1403f54
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  157
  Minor opcode:  6
  Resource id:  0x3f
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  157
  Minor opcode:  6
  Resource id:  0x3f
--------------------------------------------------

Comment 1 Philip Withnall 2008-03-11 22:48:03 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 ***