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 453565 - crash in Rhythmbox Music Player: Where browsing Magnatune...
crash in Rhythmbox Music Player: Where browsing Magnatune...
Status: RESOLVED DUPLICATE of bug 436456
Product: rhythmbox
Classification: Other
Component: general
0.10.0
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-07-04 02:15 UTC by jcqb
Modified: 2007-07-04 10:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description jcqb 2007-07-04 02:15:26 UTC
What were you doing when the application crashed?
Where browsing Magnatune from MUSIC PLAYER application.


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: 151834624 vsize: 151834624 resident: 65077248 share: 24588288 rss: 65077248 rss_rlim: 4294967295
CPU usage: start_time: 1183515145 rtime: 1437 utime: 1376 stime: 61 cutime:1 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 -1208542672 (LWP 6917)]
[New Thread -1334854768 (LWP 7008)]
[New Thread -1303385200 (LWP 6950)]
[New Thread -1269695600 (LWP 6934)]
[New Thread -1244755056 (LWP 6924)]
(no debugging symbols found)
0x0041b402 in __kernel_vsyscall ()

Thread 1 (Thread -1208542672 (LWP 6917))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 PyObject_RichCompare
    from /usr/lib/libpython2.5.so.1.0
  • #5 PyObject_RichCompareBool
    from /usr/lib/libpython2.5.so.1.0
  • #6 ??
    from /usr/lib/libpython2.5.so.1.0
  • #7 PySequence_Contains
    from /usr/lib/libpython2.5.so.1.0
  • #8 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #9 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #10 PyEval_EvalCodeEx
    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 ??
    from /usr/lib/libpython2.5.so.1.0
  • #14 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #15 PyEval_CallObjectWithKeywords
    from /usr/lib/libpython2.5.so.1.0
  • #16 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #17 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #18 ??
    from /lib/libexpat.so.0
  • #19 ??
    from /lib/libexpat.so.0
  • #20 XML_ParseBuffer
    from /lib/libexpat.so.0
  • #21 XML_Parse
    from /lib/libexpat.so.0
  • #22 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #23 PyCFunction_Call
    from /usr/lib/libpython2.5.so.1.0
  • #24 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #25 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #26 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #27 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #28 ??
    from /usr/lib/libpython2.5.so.1.0
  • #29 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #30 ??
    from /usr/lib/libpython2.5.so.1.0
  • #31 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #32 PyEval_CallObjectWithKeywords
    from /usr/lib/libpython2.5.so.1.0
  • #33 PyEval_CallFunction
    from /usr/lib/libpython2.5.so.1.0
  • #34 ??
    from /usr/lib/python2.5/site-packages/gtk-2.0/gnomevfs/_gnomevfs.so
  • #35 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #36 ??
  • #37 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
** 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
** 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
** 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
** 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
sys:1: Warning: invalid uninstantiatable type `<invalid>' in cast to `GstGnomeVFSSrc'
/usr/lib/rhythmbox/plugins/jamendo/JamendoSaxHandler.py:34: Warning: invalid uninstantiatable type `<invalid>' in cast to `GstGnomeVFSSrc'
  if name in markups:
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-07-04 10:10:03 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 ***