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 461530 - crash in Rhythmbox Music Player: nothing
crash in Rhythmbox Music Player: nothing
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-29 16:35 UTC by qthyyp
Modified: 2007-08-02 10:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description qthyyp 2007-07-29 16:35:41 UTC
What were you doing when the application crashed?
nothing


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.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 245231616 vsize: 245231616 resident: 57253888 share: 25620480 rss: 57253888 rss_rlim: 4294967295
CPU usage: start_time: 1185755696 rtime: 953 utime: 914 stime: 39 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 -1208514000 (LWP 5290)]
[New Thread -1374258288 (LWP 5340)]
[New Thread -1384748144 (LWP 5331)]
[New Thread -1342788720 (LWP 5327)]
[New Thread -1321809008 (LWP 5325)]
[New Thread -1363768432 (LWP 5320)]
[New Thread -1290339440 (LWP 5316)]
[New Thread -1311319152 (LWP 5311)]
[New Thread -1266943088 (LWP 5308)]
[New Thread -1279042672 (LWP 5302)]
[New Thread -1242502256 (LWP 5300)]
[New Thread -1255830640 (LWP 5295)]
(no debugging symbols found)
0x00baf402 in __kernel_vsyscall ()

Thread 1 (Thread -1208514000 (LWP 5290))

  • #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_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #6 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #7 ??
    from /usr/lib/libpython2.5.so.1.0
  • #8 PyObject_Call
    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 PyEval_CallObjectWithKeywords
    from /usr/lib/libpython2.5.so.1.0
  • #12 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #13 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #14 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #15 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #16 ??
    from /lib/libexpat.so.0
  • #17 ??
    from /lib/libexpat.so.0
  • #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_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #26 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #27 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #28 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #29 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #30 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #31 ??
    from /usr/lib/libpython2.5.so.1.0
  • #32 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #33 ??
    from /usr/lib/libpython2.5.so.1.0
  • #34 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #35 PyEval_CallObjectWithKeywords
    from /usr/lib/libpython2.5.so.1.0
  • #36 PyObject_CallObject
    from /usr/lib/libpython2.5.so.1.0
  • #37 ??
    from /usr/lib/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
  • #38 ??
    from /lib/libglib-2.0.so.0
  • #39 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #40 ??
    from /lib/libglib-2.0.so.0
  • #41 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #42 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #43 main
  • #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
/usr/lib/python2.5/site-packages/_xmlplus/dom/expatbuilder.py:294: Warning: invalid uninstantiatable type `(null)' in cast to `GstGnomeVFSSrc'
  _append_child(self.curNode, node)
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
/usr/lib/python2.5/site-packages/_xmlplus/dom/expatbuilder.py:294: Warning: invalid unclassed pointer in cast to `GstGnomeVFSSrc'
  _append_child(self.curNode, node)
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-08-02 10:10:57 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 ***