Bug 527041 – crash in Movie Player: trying to tune into kcsm...

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 527041 - crash in Movie Player: trying to tune into kcsm...


Summary:	crash in Movie Player: trying to tune into kcsm...


Status:	RESOLVED DUPLICATE of bug 449658

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-04-08 23:58 UTC by tony
Modified:	2008-04-09 05:47 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description tony 2008-04-08 23:58:47 UTC

Version: 2.20.3

What were you doing when the application crashed?
trying to tune into kcsm.org's audio stream


Distribution: Debian lenny/sid
Gnome Release: 2.22.0 2008-03-14 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.15-1-k7 #2 Mon Mar 6 15:42:39 UTC 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Nuvola
Icon Theme: Nuvola

Memory status: size: 137195520 vsize: 137195520 resident: 28114944 share: 13549568 rss: 28114944 rss_rlim: 4294967295
CPU usage: start_time: 1207699084 rtime: 168 utime: 143 stime: 25 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 "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6de2720 (LWP 1251)]
[New Thread 0xb1894b90 (LWP 1260)]
[New Thread 0xb22f8b90 (LWP 1259)]
[New Thread 0xb2af9b90 (LWP 1258)]
[New Thread 0xb34c7b90 (LWP 1257)]
[New Thread 0xb40b1b90 (LWP 1256)]
[New Thread 0xb48b2b90 (LWP 1255)]
[New Thread 0xb510db90 (LWP 1254)]
[New Thread 0xb6157b90 (LWP 1253)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 194664

Thread 4 (Thread 0xb2af9b90 (LWP 1258))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 __kernel_vsyscall
#7 raise
from /lib/i686/cmov/libc.so.6
#8 abort
from /lib/i686/cmov/libc.so.6
#9 __assert_fail
from /lib/i686/cmov/libc.so.6
#10 ??
from /usr/lib/libpulse.so.0
#11 ??
from /usr/lib/libpulse.so.0
#12 ??
from /usr/lib/libpulse.so.0
#13 ??
#14 ??
from /usr/lib/libpulse.so.0
#15 ??
#16 ??
from /usr/lib/libpulse.so.0
#17 ??
#18 pa_threaded_mainloop_unlock
from /usr/lib/libpulse.so.0



----------- .xsession-errors (90159 sec old) ---------------------
gdm[4938]: DEBUG: Forking extra process: /etc/gdm/PreSession/Default
gdm[4939]: DEBUG: Attempting to parse key string: xdmcp/Enable=false
gdm[4939]: DEBUG: Attempting to parse key string: daemon/ServAuthDir=/var/lib/gdm
gdm[4939]: DEBUG: Attempting to parse key string: daemon/RootPath=/sbin:/usr/sbin:/bin:/usr/bin
gdm[4938]: DEBUG: Attempting to parse key string: daemon/DefaultPath=/bin:/usr/bin
gdm[4938]: DEBUG: Attempting to parse key string: daemon/BaseXsession=/etc/gdm/Xsession
gdm[4938]: DEBUG: Running /etc/gdm/Xsession /usr/bin/gnome-session for tony on :0
/etc/gdm/Xsession: Beginning session setup...
/etc/gdm/Xsession: Executing /usr/bin/gnome-session failed, will try to run x-terminal-emulator
(gnome-terminal:4938): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.
(gnome-terminal:4938): atk-bridge-WARNING **: IOR not set.
(gnome-terminal:4938): atk-bridge-WARNING **: Could not locate registry
--------------------------------------------------

Comment 1 Philip Withnall 2008-04-09 05:47:15 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 449658 ***