Bug 450194 – crash in Rhythmbox Music Player: Wollte eine Musikdatei a...

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 450194 - crash in Rhythmbox Music Player: Wollte eine Musikdatei a...


Summary:	crash in Rhythmbox Music Player: Wollte eine Musikdatei a...


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-06-22 20:48 UTC by Fabian
Modified:	2007-06-23 00:20 UTC

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

Description Fabian 2007-06-22 20:48:27 UTC

What were you doing when the application crashed?
Wollte eine Musikdatei abspielen ;)


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 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: 126390272 vsize: 126390272 resident: 53760000 share: 24576000 rss: 53760000 rss_rlim: 4294967295
CPU usage: start_time: 1182545161 rtime: 2478 utime: 2391 stime: 87 cutime:9 cstime: 1 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 -1208284624 (LWP 2975)]
[New Thread -1286489200 (LWP 3005)]
[New Thread -1234011248 (LWP 2981)]
(no debugging symbols found)
0x009bc402 in __kernel_vsyscall ()

+ Trace 142993

Thread 1 (Thread -1208284624 (LWP 2975))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#5 PyEval_EvalCodeEx
from /usr/lib/libpython2.5.so.1.0
#6 ??
from /usr/lib/libpython2.5.so.1.0
#7 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#8 ??
from /usr/lib/libpython2.5.so.1.0
#9 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#10 PyEval_CallObjectWithKeywords
from /usr/lib/libpython2.5.so.1.0
#11 PyInstance_New
from /usr/lib/libpython2.5.so.1.0
#12 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#13 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#14 PyEval_EvalCodeEx
from /usr/lib/libpython2.5.so.1.0
#15 ??
from /usr/lib/libpython2.5.so.1.0
#16 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#17 ??
from /usr/lib/libpython2.5.so.1.0
#18 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#19 PyEval_CallObjectWithKeywords
from /usr/lib/libpython2.5.so.1.0
#20 ??
from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
#21 ??
from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
#22 ??
from /lib/libexpat.so.0
#23 ??
from /lib/libexpat.so.0
#24 ??
from /lib/libexpat.so.0
#25 ??
from /lib/libexpat.so.0
#26 XML_ParseBuffer
from /lib/libexpat.so.0
#27 XML_Parse
from /lib/libexpat.so.0
#28 ??
from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
#29 PyCFunction_Call
from /usr/lib/libpython2.5.so.1.0
#30 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#31 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#32 PyEval_EvalCodeEx
from /usr/lib/libpython2.5.so.1.0
#33 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#34 PyEval_EvalCodeEx
from /usr/lib/libpython2.5.so.1.0
#35 PyEval_EvalFrameEx
from /usr/lib/libpython2.5.so.1.0
#36 PyEval_EvalCodeEx
from /usr/lib/libpython2.5.so.1.0
#37 ??
from /usr/lib/libpython2.5.so.1.0
#38 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#39 ??
from /usr/lib/libpython2.5.so.1.0
#40 PyObject_Call
from /usr/lib/libpython2.5.so.1.0
#41 PyEval_CallObjectWithKeywords
from /usr/lib/libpython2.5.so.1.0
#42 PyObject_CallObject
from /usr/lib/libpython2.5.so.1.0
#43 ??
from /usr/lib/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
#44 ??
from /lib/libglib-2.0.so.0
#45 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#46 ??
from /lib/libglib-2.0.so.0
#47 g_main_loop_run
from /lib/libglib-2.0.so.0
#48 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#49 main
#0 __kernel_vsyscall



----------- .xsession-errors (23 sec old) ---------------------
--> file:///home/Fabian
(nautilus:2872): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
Fenstermanager-Warnung:Ungültiges WM_TRANSIENT_FOR-Fenster 0x45 festgelegt für 0x10064b4 ().
** 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'
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
sys:1: Warning: invalid uninstantiatable type `<invalid>' in cast to `GstGnomeVFSSrc'
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
sys:1: Warning: invalid uninstantiatable type `(null)' in cast to `GstGnomeVFSSrc'
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
/usr/lib/python2.5/site-packages/_xmlplus/dom/minidom.py:663: Warning: invalid uninstantiatable type `<invalid>' in cast to `GstGnomeVFSSrc'
  self._attrsNS = {} #    tagName -> Attribute
--------------------------------------------------

Comment 1 Jonathan Matthew 2007-06-23 00:20:19 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 ***