Bug 393304 – 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 393304 - crash in Movie Player:


Summary:	crash in Movie Player:


Status:	RESOLVED DUPLICATE of bug 336370

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-01-05 22:12 UTC by Emmanuel BROEKS
Modified:	2007-01-06 16:18 UTC

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

Description Emmanuel BROEKS 2007-01-05 22:12:13 UTC

Version: 2.16.3

What were you doing when the application crashed?



Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-1.2869.fc6 #1 SMP Wed Dec 20 14:51:19 EST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled
----------- .xsession-errors (13364 sec old) ---------------------
PokerChildInterface: 
publishPacket(0): outbound: type = POKER_ROLES(124) serial = 0 roles = PLAY
PokerChildInterface: ** Message: reading glade file /usr/share/poker3d/data/interface/interface.glade
PokerChildInterface: 
window name : login_window
handleConfigureWindow2097244
XwncDesktop Window mapped login_window 1
window name : login_window
handleConfigureWindow2097244
** (process:3507): DEBUG: 200x166
handleRestackWindow2097244
handleRestackWindow2097244
** (process:3507): DEBUG: HandleHit login_window
PokerChildInterface: ** Message: login ok
PokerChildInterface: 
PokerInterfaceProtocol: dataReceived login
--------------------------------------------------

Memory status: size: 164823040 vsize: 0 resident: 164823040 share: 0 rss: 32985088 rss_rlim: 0
CPU usage: start_time: 1168034997 rtime: 0 utime: 1526 stime: 0 cutime:1361 cstime: 0 timeout: 165 it_real_value: 0 frequency: 7

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 -1208609072 (LWP 7106)]
[New Thread -1288873072 (LWP 7110)]
[New Thread -1272870000 (LWP 7109)]
[New Thread -1262380144 (LWP 7108)]
(no debugging symbols found)
0x00c86402 in __kernel_vsyscall ()

+ Trace 99713

Thread 2 (Thread -1288873072 (LWP 7110))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 gnome_gtk_module_info_get
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 gst_pad_alloc_buffer
from /usr/lib/libgstreamer-0.10.so.0
#13 gst_pad_push
from /usr/lib/libgstreamer-0.10.so.0
#14 gst_type_find_element_get_type
from /usr/lib/gstreamer-0.10/libgstcoreelements.so
#15 gst_pad_alloc_buffer
from /usr/lib/libgstreamer-0.10.so.0
#16 gst_pad_push
from /usr/lib/libgstreamer-0.10.so.0
#17 _gst_format_initialize
from /usr/lib/libgstreamer-0.10.so.0
#18 gst_pad_alloc_buffer
from /usr/lib/libgstreamer-0.10.so.0
#19 gst_pad_push
from /usr/lib/libgstreamer-0.10.so.0
#20 gst_base_src_get_type
from /usr/lib/libgstbase-0.10.so.0
#21 gst_task_set_lock
from /usr/lib/libgstreamer-0.10.so.0
#22 g_thread_pool_push
from /lib/libglib-2.0.so.0
#23 g_thread_create_full
from /lib/libglib-2.0.so.0
#24 start_thread
from /lib/libpthread.so.0
#25 clone
from /lib/libc.so.6

Comment 1 Jens Granseuer 2007-01-06 16:18:44 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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