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 443755 - crash in Rhythmbox Music Player: I just got done importin...
crash in Rhythmbox Music Player: I just got done importin...
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-04 00:14 UTC by mijokijo
Modified: 2007-06-04 09:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description mijokijo 2007-06-04 00:14:14 UTC
What were you doing when the application crashed?
I just got done importing what files I was able to from my music folder (could do the MP3s), and after that went to the Magnatune folder and tried playing the first song in the list, got an error, but then Rhythmbox went on to the next song, which also had an error, and so on for a few dozen songs, then it crashed.


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:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Murrina-Black
Icon Theme: Fedora

Memory status: size: 144474112 vsize: 144474112 resident: 57651200 share: 20217856 rss: 57651200 rss_rlim: 4294967295
CPU usage: start_time: 1180915582 rtime: 1893 utime: 1754 stime: 139 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 -1208473040 (LWP 4846)]
[New Thread -1310721136 (LWP 5021)]
[New Thread -1234605168 (LWP 4851)]
(no debugging symbols found)
0x00d91402 in __kernel_vsyscall ()

Thread 1 (Thread -1208473040 (LWP 4846))

  • #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 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #12 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #13 ??
    from /lib/libexpat.so.0
  • #14 ??
    from /lib/libexpat.so.0
  • #15 ??
    from /lib/libexpat.so.0
  • #16 ??
    from /lib/libexpat.so.0
  • #17 XML_ParseBuffer
    from /lib/libexpat.so.0
  • #18 XML_Parse
    from /lib/libexpat.so.0
  • #19 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #20 PyCFunction_Call
    from /usr/lib/libpython2.5.so.1.0
  • #21 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #22 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #23 PyEval_EvalCodeEx
    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 PyObject_CallObject
    from /usr/lib/libpython2.5.so.1.0
  • #34 ??
    from /usr/lib/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
  • #35 ??
    from /lib/libglib-2.0.so.0
  • #36 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #37 ??
    from /lib/libglib-2.0.so.0
  • #38 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #39 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #40 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
/usr/lib/python2.5/site-packages/_xmlplus/dom/expatbuilder.py:795: Warning: invalid uninstantiatable type `(null)' in cast to `GstGnomeVFSSrc'
  d['ownerElement'] = node
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-06-04 09:29:28 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 ***