Bug 476225 – crash in Movie Player:

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 476225 - crash in Movie Player:


Summary:	crash in Movie Player:


Status:	RESOLVED DUPLICATE of bug 450336

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-12 14:28 UTC by haruo-31
Modified:	2007-09-12 16:01 UTC

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

Description haruo-31 2007-09-12 14:28:37 UTC

Version: 2.18.2

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-1-amd64 #1 SMP Sun Jul 29 13:54:41 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Crux

Memory status: size: 496820224 vsize: 496820224 resident: 45731840 share: 20361216 rss: 45731840 rss_rlim: 18446744073709551615
CPU usage: start_time: 1189606848 rtime: 4959 utime: 4675 stime: 284 cutime:0 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 47378815925216 (LWP 4725)]
[New Thread 1124096336 (LWP 7212)]
[New Thread 1082132816 (LWP 7210)]
[New Thread 1115703632 (LWP 4732)]
[New Thread 1107310928 (LWP 4731)]
[New Thread 1098918224 (LWP 4730)]
[New Thread 1090525520 (LWP 4729)]
(no debugging symbols found)
0x00002b173b5b1be6 in poll () from /lib/libc.so.6

+ Trace 162362

Thread 5 (Thread 1107310928 (LWP 4731))

#0 waitpid
from /lib/libpthread.so.0
#1 ??
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 render_deformation
from /usr/lib/libvisual-0.4/actor/actor_JESS.so
#4 renderer
from /usr/lib/libvisual-0.4/actor/actor_JESS.so
#5 act_jess_render
from /usr/lib/libvisual-0.4/actor/actor_JESS.so
#6 visual_actor_run
from /usr/lib/libvisual-0.4.so.0
#7 ??
from /usr/lib/gstreamer-0.10/libgstlibvisual.so
#8 ??
from /usr/lib/libgstreamer-0.10.so.0
#9 gst_pad_push
from /usr/lib/libgstreamer-0.10.so.0
#10 ??
from /usr/lib/libgstreamer-0.10.so.0
#11 gst_pad_push
from /usr/lib/libgstreamer-0.10.so.0
#12 ??
from /usr/lib/libgstbase-0.10.so.0
#13 ??
from /usr/lib/libgstreamer-0.10.so.0
#14 gst_pad_push
from /usr/lib/libgstreamer-0.10.so.0
#15 ??
from /usr/lib/libgstbase-0.10.so.0
#16 ??
from /usr/lib/libgstreamer-0.10.so.0
#17 gst_pad_push
from /usr/lib/libgstreamer-0.10.so.0
#18 ??
from /usr/lib/libgstbase-0.10.so.0
#19 ??
from /usr/lib/libgstreamer-0.10.so.0
#20 gst_pad_push
from /usr/lib/libgstreamer-0.10.so.0
#21 ??
from /usr/lib/gstreamer-0.10/libgstcoreelements.so
#22 ??
from /usr/lib/libgstreamer-0.10.so.0
#23 ??
from /usr/lib/libglib-2.0.so.0
#24 ??
from /usr/lib/libglib-2.0.so.0
#25 start_thread
from /lib/libpthread.so.0
#26 clone
from /lib/libc.so.6
#27 ??



----------- .xsession-errors (50 sec old) ---------------------
(totem:4725): Gtk-WARNING **: Invalid input string
(totem:4725): Gtk-WARNING **: Invalid input string
sh: jackd: command not found
(totem:4725): Gtk-WARNING **: Invalid input string
(totem:4725): Gtk-WARNING **: Invalid input string
(totem:4725): Gtk-WARNING **: Invalid input string
sh: jackd: command not found
ウィンドウ・マネージャの警告: last_user_time (1106715296) is greater than comparison timestamp (4196004636).  This most likely represents a buggy client sending inaccurate timestamps in 
ウィンドウ・マネージャの警告: 0x2a00091 (Synaptic) appears to be one of the offending windows with a timestamp of 1106715296.  Working around...
sh: jackd: command not found
--------------------------------------------------

Comment 1 Philip Withnall 2007-09-12 16:01:29 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 450336 ***