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


Summary:	crash in Movie Player:


Status:	RESOLVED DUPLICATE of bug 514928

Product:	totem
Classification:	Core
Component:	general
Version:	2.20.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:	2008-02-07 14:39 UTC by maxim
Modified:	2008-02-08 02:03 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description maxim 2008-02-07 14:39:05 UTC

Version: 2.20.3

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.23-1-amd64 #1 SMP Fri Nov 30 12:19:15 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome

Memory status: size: 264470528 vsize: 264470528 resident: 23965696 share: 15253504 rss: 23965696 rss_rlim: 18446744073709551615
CPU usage: start_time: 1202395393 rtime: 48 utime: 38 stime: 10 cutime:2 cstime: 2 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 0x2b71df959410 (LWP 2516)]
[New Thread 0x40800950 (LWP 2518)]
(no debugging symbols found)
0x00002b71db67934f in waitpid () from /lib/libpthread.so.0

+ Trace 188421

Thread 1 (Thread 0x2b71df959410 (LWP 2516))

#0 waitpid
from /lib/libpthread.so.0
#1 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#2 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#3 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#4 <signal handler called>
#5 strncpy
from /lib/libc.so.6
#6 ??
from /usr/lib/gstreamer-0.10/libgstbluetooth.so
#7 ??
from /usr/lib/libgstbase-0.10.so.0
#8 gst_element_change_state
from /usr/lib/libgstreamer-0.10.so.0
#9 ??
from /usr/lib/libgstreamer-0.10.so.0
#10 ??
from /usr/lib/gstreamer-0.10/libgstautodetect.so
#11 gst_element_change_state
from /usr/lib/libgstreamer-0.10.so.0
#12 ??
from /usr/lib/libgstreamer-0.10.so.0
#13 ??
from /usr/lib/libgstreamer-0.10.so.0
#14 gst_element_change_state
from /usr/lib/libgstreamer-0.10.so.0
#15 ??
from /usr/lib/libgstreamer-0.10.so.0
#16 ??
from /usr/lib/gstreamer-0.10/libgstgconfelements.so
#17 ??
from /usr/lib/gstreamer-0.10/libgstgconfelements.so
#18 ??
from /usr/lib/gstreamer-0.10/libgstgconfelements.so
#19 gst_element_change_state
from /usr/lib/libgstreamer-0.10.so.0
#20 ??
from /usr/lib/libgstreamer-0.10.so.0
#21 bacon_video_widget_new
#22 ??
#23 main
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors ---------------------
(gnome-panel:3731): Wnck-WARNING **: Property _NET_WM_ICON_NAME contained invalid UTF-8
Предупреждение менеджера окон: Свойство _NET_WM_ICON_NAME для окна 0x3a00025 содержало недопустимые данные UTF-8
Предупреждение менеджера окон: Свойство _NET_WM_NAME для окна 0x3a00943 содержало недопустимые данные UTF-8
Предупреждение менеджера окон: Свойство _NET_WM_ICON_NAME для окна 0x3a00943 содержало недопустимые данные UTF-8
(gnome-panel:3731): Wnck-WARNING **: Property _NET_WM_NAME contained invalid UTF-8
(gnome-panel:3731): Wnck-WARNING **: Property _NET_WM_ICON_NAME contained invalid UTF-8
Предупреждение менеджера окон: неверный параметр WM_TRANSIENT_FOR окна 0x87 указан для 0xe0eae5 ().
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fffd5cd4000
--------------------------------------------------

Comment 1 André Klapper 2008-02-08 02:03:07 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 514928 ***