Bug 459444 – crash in Rhythmbox Music Player: habe gerade "magnatune" ...

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 459444 - crash in Rhythmbox Music Player: habe gerade "magnatune" ...


Summary:	crash in Rhythmbox Music Player: habe gerade "magnatune" ...


Status:	RESOLVED DUPLICATE of bug 436456

Product:	rhythmbox
Classification:	Other
Component:	general
Version:	0.10.0
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	RhythmBox Maintainers
QA Contact:	RhythmBox Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-07-23 06:51 UTC by m.ottmar-werbung
Modified:	2007-07-24 12:19 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description m.ottmar-werbung 2007-07-23 06:51:37 UTC

What were you doing when the application crashed?
habe gerade "magnatune" (?) eingelesen - und einen Titzel zum abspielen gewählt


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.1-27.fc7 #1 SMP Tue Jul 17 17:13:26 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 278986752 vsize: 278986752 resident: 181694464 share: 22487040 rss: 181694464 rss_rlim: 4294967295
CPU usage: start_time: 1185172605 rtime: 5920 utime: 5609 stime: 311 cutime:4 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(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 -1208083920 (LWP 2697)]
[New Thread -1219945584 (LWP 2733)]
[New Thread -1268286576 (LWP 2729)]
[New Thread -1256199280 (LWP 2710)]
[New Thread -1245709424 (LWP 2706)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 149890

Thread 1 (Thread -1208083920 (LWP 2697))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
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 __assert_fail
from /lib/libc.so.6
#8 PyEval_EvalCodeEx
from /usr/lib/libpython2.5.so.1.0
#9 ??
from /usr/lib/libpython2.5.so.1.0
#10 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#11 ??
from /usr/lib/libpython2.5.so.1.0
#12 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#13 PyEval_CallObjectWithKeywords
from /usr/lib/libpython2.5.so.1.0
#14 PyObject_CallObject
from /usr/lib/libpython2.5.so.1.0
#15 ??
from /usr/lib/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
#16 ??
from /lib/libglib-2.0.so.0
#17 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#18 ??
from /lib/libglib-2.0.so.0
#19 g_main_loop_run
from /lib/libglib-2.0.so.0
#20 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#21 main
#0 __kernel_vsyscall



----------- .xsession-errors (20 sec old) ---------------------
** (gnome-cd:2610): WARNING **: ERROR: Konnte CD-Gerät nicht zum Lesen ansprechen.
** (gnome-cd:2610): WARNING **: ERROR: Konnte CD-Gerät nicht zum Lesen ansprechen.
** (gnome-cd:2610): WARNING **: ERROR: Konnte CD-Gerät nicht zum Lesen ansprechen.
** (gnome-cd:2610): WARNING **: ERROR: Konnte CD-Gerät nicht zum Lesen ansprechen.
** (gnome-cd:2610): WARNING **: ERROR: Konnte CD-Gerät nicht zum Lesen ansprechen.
** (gnome-cd:2610): WARNING **: ERROR: Konnte CD-Gerät nicht zum Lesen ansprechen.
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
sys:1: Warning: invalid unclassed pointer in cast to `GstGnomeVFSSrc'
rhythmbox: Python/ceval.c:2626: PyEval_EvalCodeEx: Zusicherung »tstate != ((void *)0)« nicht erfüllt.
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
--------------------------------------------------

Comment 1 Jonathan Matthew 2007-07-24 12:19:18 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 436456 ***