Bug 465074 – crash in Movie Player: Maximizing the window to...

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 465074 - crash in Movie Player: Maximizing the window to...


Summary:	crash in Movie Player: Maximizing the window to...


Status:	RESOLVED DUPLICATE of bug 349105

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-08-09 15:43 UTC by cdanks
Modified:	2007-08-09 17:34 UTC

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

Description cdanks 2007-08-09 15:43:46 UTC

Version: 2.16.4

What were you doing when the application crashed?
Maximizing the window to see the image better


Distribution: Red Hat Enterprise Linux Client release 5 (Tikanga)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 599351296 vsize: 599351296 resident: 66293760 share: 18534400 rss: 66293760 rss_rlim: -1
CPU usage: start_time: 1186674170 rtime: 181 utime: 158 stime: 23 cutime:0 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 "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 46912498565072 (LWP 13627)]
[New Thread 1147169088 (LWP 13640)]
[New Thread 1126189376 (LWP 13638)]
[New Thread 1115699520 (LWP 13637)]
[New Thread 1094719808 (LWP 13636)]
[New Thread 1105209664 (LWP 13635)]
[New Thread 1084229952 (LWP 13633)]
0x000000399e0c48c6 in poll () from /lib64/libc.so.6

+ Trace 153989

Thread 4 (Thread 1115699520 (LWP 13637))

#0 waitpid
from /lib64/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 raise
from /lib64/libc.so.6
#4 abort
from /lib64/libc.so.6
#5 g_logv
from /lib64/libglib-2.0.so.0
#6 g_log
from /lib64/libglib-2.0.so.0
#7 g_assert_warning
from /lib64/libglib-2.0.so.0
#8 gst_caps_subtract
from /usr/lib64/libgstreamer-0.10.so.0
#9 gst_caps_is_subset
from /usr/lib64/libgstreamer-0.10.so.0
#10 gst_caps_is_equal
from /usr/lib64/libgstreamer-0.10.so.0
#11 gst_base_transform_get_type
from /usr/lib64/libgstbase-0.10.so.0
#12 gst_pad_accept_caps
from /usr/lib64/libgstreamer-0.10.so.0
#13 gst_base_transform_get_type
from /usr/lib64/libgstbase-0.10.so.0
#14 gst_pad_accept_caps
from /usr/lib64/libgstreamer-0.10.so.0
#15 gst_base_transform_get_type
from /usr/lib64/libgstbase-0.10.so.0
#16 gst_pad_accept_caps
from /usr/lib64/libgstreamer-0.10.so.0
#17 gst_ghost_pad_new_no_target
from /usr/lib64/libgstreamer-0.10.so.0
#18 gst_pad_accept_caps
from /usr/lib64/libgstreamer-0.10.so.0
#19 gst_pad_accept_caps
from /usr/lib64/libgstreamer-0.10.so.0
#20 gst_stream_selector_get_type
from /usr/lib64/gstreamer-0.10/libgstplaybin.so
#21 gst_pad_accept_caps
from /usr/lib64/libgstreamer-0.10.so.0
#22 gst_ghost_pad_new_no_target
from /usr/lib64/libgstreamer-0.10.so.0
#23 gst_pad_accept_caps
from /usr/lib64/libgstreamer-0.10.so.0
#24 gst_theora_dec_get_type
from /usr/lib64/gstreamer-0.10/libgsttheora.so
#25 gst_pad_alloc_buffer
from /usr/lib64/libgstreamer-0.10.so.0
#26 gst_pad_push
from /usr/lib64/libgstreamer-0.10.so.0
#27 gst_queue_get_type
from /usr/lib64/gstreamer-0.10/libgstcoreelements.so
#28 gst_task_set_lock
from /usr/lib64/libgstreamer-0.10.so.0
#29 g_thread_pool_push
from /lib64/libglib-2.0.so.0
#30 g_thread_create_full
from /lib64/libglib-2.0.so.0
#31 start_thread
from /lib64/libpthread.so.0
#32 clone
from /lib64/libc.so.6
#33 ??

Comment 1 Iestyn Pryce 2007-08-09 17:34:23 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.

Duplicate via stacktrace in Bug 450143

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