Bug 455557 – crash in Movie Player: Estaba, viendo el funcio...

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 455557 - crash in Movie Player: Estaba, viendo el funcio...


Summary:	crash in Movie Player: Estaba, viendo el funcio...


Status:	RESOLVED DUPLICATE of bug 348455

Product:	totem
Classification:	Core
Component:	general
Version:	2.16.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-07-10 13:40 UTC by carlos
Modified:	2007-07-11 13:33 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description carlos 2007-07-10 13:40:02 UTC

Version: 2.16.4

What were you doing when the application crashed?
Estaba, viendo el funcionamiento del video. Al terminar la imagen 003 es cuando se colgo.
Saludos


Distribution: CentOS release 5 (Final)
Gnome Release: 2.16.0 2007-02-18 (CentOS)
BugBuddy Version: 2.16.0

Memory status: size: 217481216 vsize: 0 resident: 217481216 share: 0 rss: 78934016 rss_rlim: 0
CPU usage: start_time: 1184073916 rtime: 0 utime: 7984 stime: 0 cutime:7502 cstime: 0 timeout: 482 it_real_value: 0 frequency: 4

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209091872 (LWP 3738)]
[New Thread -1340855408 (LWP 3804)]
[New Thread -1319875696 (LWP 3802)]
[New Thread -1298891888 (LWP 3800)]
(no debugging symbols found)
0x00c32402 in __kernel_vsyscall ()

+ Trace 147011

Thread 4 (Thread -1298891888 (LWP 3800))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/i686/nosegneg/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 gst_file_src_get_type
from /usr/lib/gstreamer-0.10/libgstcoreelements.so
#5 gst_base_src_get_type
from /usr/lib/libgstbase-0.10.so.0
#6 gst_base_src_get_type
from /usr/lib/libgstbase-0.10.so.0
#7 gst_pad_get_range
from /usr/lib/libgstreamer-0.10.so.0
#8 gst_pad_pull_range
from /usr/lib/libgstreamer-0.10.so.0
#9 gst_ghost_pad_new_no_target
from /usr/lib/libgstreamer-0.10.so.0
#10 gst_pad_get_range
from /usr/lib/libgstreamer-0.10.so.0
#11 gst_pad_pull_range
from /usr/lib/libgstreamer-0.10.so.0
#12 gst_type_find_element_get_type
from /usr/lib/gstreamer-0.10/libgstcoreelements.so
#13 gst_pad_get_range
from /usr/lib/libgstreamer-0.10.so.0
#14 gst_pad_pull_range
from /usr/lib/libgstreamer-0.10.so.0
#15 gst_avi_demux_get_type
from /usr/lib/gstreamer-0.10/libgstavi.so
#16 gst_task_set_lock
from /usr/lib/libgstreamer-0.10.so.0
#17 g_thread_pool_push
from /lib/libglib-2.0.so.0
#18 g_thread_create_full
from /lib/libglib-2.0.so.0
#19 start_thread
from /lib/i686/nosegneg/libpthread.so.0
#20 clone
from /lib/i686/nosegneg/libc.so.6

Comment 1 Philip Withnall 2007-07-11 13:33:36 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 348455 ***