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 450371 - crash in Rhythmbox Music Player: In rhythmbox, trying to ...
crash in Rhythmbox Music Player: In rhythmbox, trying to ...
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-06-23 15:13 UTC by sirius56
Modified: 2007-06-23 23:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description sirius56 2007-06-23 15:13:40 UTC
What were you doing when the application crashed?
In rhythmbox, trying to run Magnatune


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: 139067392 vsize: 139067392 resident: 60137472 share: 26542080 rss: 60137472 rss_rlim: 4294967295
CPU usage: start_time: 1182611191 rtime: 1409 utime: 1343 stime: 66 cutime:2 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 -1208399312 (LWP 2881)]
[New Thread -1225720944 (LWP 2890)]
[New Thread -1262302320 (LWP 2889)]
[New Thread -1251153008 (LWP 2887)]
(no debugging symbols found)
0x00e9c402 in __kernel_vsyscall ()

Thread 1 (Thread -1208399312 (LWP 2881))

  • #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 Py_FatalError
    from /usr/lib/libpython2.5.so.1.0
  • #8 PyCFunction_NewEx
    from /usr/lib/libpython2.5.so.1.0
  • #9 ??
    from /usr/lib/libpython2.5.so.1.0
  • #10 ??
    from /usr/lib/libpython2.5.so.1.0
  • #11 ??
    from /usr/lib/libpython2.5.so.1.0
  • #12 ??
    from /usr/lib/libpython2.5.so.1.0
  • #13 PyObject_GetItem
    from /usr/lib/libpython2.5.so.1.0
  • #14 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #15 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #16 ??
    from /usr/lib/libpython2.5.so.1.0
  • #17 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #18 ??
    from /usr/lib/libpython2.5.so.1.0
  • #19 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #20 PyEval_CallObjectWithKeywords
    from /usr/lib/libpython2.5.so.1.0
  • #21 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #22 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #23 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #24 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #25 ??
    from /lib/libexpat.so.0
  • #26 ??
    from /lib/libexpat.so.0
  • #27 ??
    from /lib/libexpat.so.0
  • #28 ??
    from /lib/libexpat.so.0
  • #29 XML_ParseBuffer
    from /lib/libexpat.so.0
  • #30 XML_Parse
    from /lib/libexpat.so.0
  • #31 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #32 PyCFunction_Call
    from /usr/lib/libpython2.5.so.1.0
  • #33 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #34 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #35 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #36 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #37 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #38 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #39 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #40 ??
    from /usr/lib/libpython2.5.so.1.0
  • #41 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #42 ??
    from /usr/lib/libpython2.5.so.1.0
  • #43 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #44 PyEval_CallObjectWithKeywords
    from /usr/lib/libpython2.5.so.1.0
  • #45 PyObject_CallObject
    from /usr/lib/libpython2.5.so.1.0
  • #46 ??
    from /usr/lib/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
  • #47 ??
    from /lib/libglib-2.0.so.0
  • #48 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #49 ??
    from /lib/libglib-2.0.so.0
  • #50 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #51 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #52 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
** 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
Fatal Python error: GC object already tracked
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-06-23 23:41:49 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 ***