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 455423 - crash in Rhythmbox Music Player: I went to Magnatune, c...
crash in Rhythmbox Music Player: I went to Magnatune, c...
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-10 06:02 UTC by ShawnS427
Modified: 2007-07-10 09:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description ShawnS427 2007-07-10 06:02:46 UTC
What were you doing when the application crashed?
I went to Magnatune,   chose the first song and pressed play,   it gave an X next to it then went on scrolling throgh the list giving Xs next to each song then finaly giving me this prompt


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 724914176 vsize: 724914176 resident: 71024640 share: 22593536 rss: 71024640 rss_rlim: 18446744073709551615
CPU usage: start_time: 1184046738 rtime: 2628 utime: 2367 stime: 261 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912709306560 (LWP 3265)]
[New Thread 1199618384 (LWP 3477)]
[New Thread 1126189392 (LWP 3317)]
[New Thread 1084229968 (LWP 3270)]
(no debugging symbols found)
0x00002aaab188089f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912709306560 (LWP 3265))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 PyObject_RichCompare
    from /usr/lib64/libpython2.5.so.1.0
  • #4 PyEval_EvalFrameEx
    from /usr/lib64/libpython2.5.so.1.0
  • #5 PyEval_EvalCodeEx
    from /usr/lib64/libpython2.5.so.1.0
  • #6 ??
    from /usr/lib64/libpython2.5.so.1.0
  • #7 PyObject_Call
    from /usr/lib64/libpython2.5.so.1.0
  • #8 ??
    from /usr/lib64/libpython2.5.so.1.0
  • #9 PyObject_Call
    from /usr/lib64/libpython2.5.so.1.0
  • #10 PyEval_CallObjectWithKeywords
    from /usr/lib64/libpython2.5.so.1.0
  • #11 ??
    from /usr/lib64/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #12 ??
    from /usr/lib64/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #13 ??
    from /lib64/libexpat.so.0
  • #14 ??
    from /lib64/libexpat.so.0
  • #15 ??
    from /lib64/libexpat.so.0
  • #16 ??
    from /lib64/libexpat.so.0
  • #17 XML_ParseBuffer
    from /lib64/libexpat.so.0
  • #18 ??
    from /usr/lib64/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #19 PyEval_EvalFrameEx
    from /usr/lib64/libpython2.5.so.1.0
  • #20 PyEval_EvalFrameEx
    from /usr/lib64/libpython2.5.so.1.0
  • #21 PyEval_EvalCodeEx
    from /usr/lib64/libpython2.5.so.1.0
  • #22 PyEval_EvalFrameEx
    from /usr/lib64/libpython2.5.so.1.0
  • #23 PyEval_EvalCodeEx
    from /usr/lib64/libpython2.5.so.1.0
  • #24 PyEval_EvalFrameEx
    from /usr/lib64/libpython2.5.so.1.0
  • #25 PyEval_EvalCodeEx
    from /usr/lib64/libpython2.5.so.1.0
  • #26 ??
    from /usr/lib64/libpython2.5.so.1.0
  • #27 PyObject_Call
    from /usr/lib64/libpython2.5.so.1.0
  • #28 ??
    from /usr/lib64/libpython2.5.so.1.0
  • #29 PyObject_Call
    from /usr/lib64/libpython2.5.so.1.0
  • #30 PyEval_CallObjectWithKeywords
    from /usr/lib64/libpython2.5.so.1.0
  • #31 ??
    from /usr/lib64/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
  • #32 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #33 ??
    from /lib64/libglib-2.0.so.0
  • #34 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #35 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #36 main
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors ---------------------
TypeError: Cannot build a gnomevfs.URI
** 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
/usr/lib64/python2.5/site-packages/_xmlplus/dom/expatbuilder.py:805: Warning: invalid uninstantiatable type `<invalid>' in cast to `GstGnomeVFSSrc'
  if ' ' in name:
/usr/lib64/python2.5/site-packages/_xmlplus/dom/expatbuilder.py:812: Warning: invalid unclassed pointer in cast to `GstGnomeVFSSrc'
  assert curNode.nodeName == name, \
/usr/lib64/python2.5/site-packages/_xmlplus/dom/expatbuilder.py:812: Warning: invalid uninstantiatable type `<invalid>' in cast to `GstGnomeVFSSrc'
  assert curNode.nodeName == name, \
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-07-10 09:09:25 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 ***