Bug 492423 – crash in Movie Player: Double Click real video ...

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 492423 - crash in Movie Player: Double Click real video ...


Summary:	crash in Movie Player: Double Click real video ...


Status:	RESOLVED DUPLICATE of bug 423668

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-11-01 17:40 UTC by aragorn
Modified:	2007-11-02 06:39 UTC

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

Description aragorn 2007-11-01 17:40:34 UTC

Version: 2.18.3

What were you doing when the application crashed?
Double Click real video .rm file on desktop opened file with Totem


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.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 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: 213200896 vsize: 213200896 resident: 37957632 share: 26300416 rss: 37957632 rss_rlim: 4294967295
CPU usage: start_time: 1193938584 rtime: 170 utime: 147 stime: 23 cutime:8 cstime: 1 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 -1209177488 (LWP 4005)]
[New Thread -1375831152 (LWP 4027)]
[New Thread -1365341296 (LWP 4026)]
[New Thread -1354851440 (LWP 4025)]
[New Thread -1344361584 (LWP 4024)]
[New Thread -1333871728 (LWP 4023)]
[New Thread -1323381872 (LWP 4022)]
[New Thread -1312892016 (LWP 4021)]
[New Thread -1302402160 (LWP 4020)]
[New Thread -1291912304 (LWP 4019)]
[New Thread -1281422448 (LWP 4018)]
[New Thread -1270932592 (LWP 4017)]
[New Thread -1260442736 (LWP 4016)]
[New Thread -1249948784 (LWP 4015)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 174403

Thread 14 (Thread -1249948784 (LWP 4015))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 gst_adapter_flush
from /usr/lib/libgstbase-0.10.so.0
#5 ??
from /usr/lib/gstreamer-0.10/libgstrmdemux.so
#6 ??
from /usr/lib/gstreamer-0.10/libgstrmdemux.so
#7 ??
from /usr/lib/libgstreamer-0.10.so.0
#8 ??
from /lib/libglib-2.0.so.0
#9 ??
from /lib/libglib-2.0.so.0
#10 start_thread
from /lib/libpthread.so.0
#11 clone
from /lib/libc.so.6



----------- .xsession-errors (9 sec old) ---------------------
  Minor opcode:  6
  Resource id:  0x65
JACK tmpdir identified as [/dev/shm]
*** attempt to put segment in horiz list twice
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  157
  Minor opcode:  6
  Resource id:  0x65
QObject::connect: No such slot BlueCurve::BlueCurveClient::contextHelp()
QObject::connect:  (sender name:   'help')
QObject::connect:  (receiver name: 'unnamed')
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  157
  Minor opcode:  6
  Resource id:  0x65
--------------------------------------------------

Comment 1 Philip Withnall 2007-11-02 06:39:38 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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