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 443740 - crash in Rhythmbox Music Player: I don't know exactly .. ...
crash in Rhythmbox Music Player: I don't know exactly .. ...
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-03 23:00 UTC by tokegee
Modified: 2007-06-03 23:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description tokegee 2007-06-03 23:00:30 UTC
What were you doing when the application crashed?
I don't know exactly .. I just opened some files.


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: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 135147520 vsize: 135147520 resident: 44072960 share: 17186816 rss: 44072960 rss_rlim: 4294967295
CPU usage: start_time: 1180911448 rtime: 1642 utime: 1555 stime: 87 cutime:4 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 -1208317392 (LWP 5210)]
[New Thread -1233876080 (LWP 5235)]
[New Thread -1220043888 (LWP 5226)]
[New Thread -1244365936 (LWP 5217)]
(no debugging symbols found)
0x002f0402 in __kernel_vsyscall ()

Thread 1 (Thread -1208317392 (LWP 5210))

  • #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 PyInstance_New
    from /usr/lib/libpython2.5.so.1.0
  • #12 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #13 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #14 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #15 ??
    from /usr/lib/libpython2.5.so.1.0
  • #16 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #17 ??
    from /usr/lib/libpython2.5.so.1.0
  • #18 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #19 PyEval_CallObjectWithKeywords
    from /usr/lib/libpython2.5.so.1.0
  • #20 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #21 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #22 ??
    from /lib/libexpat.so.0
  • #23 ??
    from /lib/libexpat.so.0
  • #24 ??
    from /lib/libexpat.so.0
  • #25 ??
    from /lib/libexpat.so.0
  • #26 XML_ParseBuffer
    from /lib/libexpat.so.0
  • #27 XML_Parse
    from /lib/libexpat.so.0
  • #28 ??
    from /usr/lib/python2.5/site-packages/_xmlplus/parsers/pyexpat.so
  • #29 PyCFunction_Call
    from /usr/lib/libpython2.5.so.1.0
  • #30 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #31 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #32 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #33 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #34 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #35 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #36 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #37 ??
    from /usr/lib/libpython2.5.so.1.0
  • #38 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #39 ??
    from /usr/lib/libpython2.5.so.1.0
  • #40 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #41 PyEval_CallObjectWithKeywords
    from /usr/lib/libpython2.5.so.1.0
  • #42 PyObject_CallObject
    from /usr/lib/libpython2.5.so.1.0
  • #43 ??
    from /usr/lib/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
  • #44 ??
    from /lib/libglib-2.0.so.0
  • #45 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #46 ??
    from /lib/libglib-2.0.so.0
  • #47 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #48 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #49 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (13 sec old) ---------------------
(evolution:4835): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:4835): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:4835): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:4835): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:4835): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
** 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 unclassed pointer in cast to `GstGnomeVFSSrc'
sys:1: Warning: invalid uninstantiatable type `<invalid>' in cast to `GstGnomeVFSSrc'
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
sys:1: Warning: invalid uninstantiatable type `(null)' in cast to `GstGnomeVFSSrc'
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
/usr/lib/python2.5/site-packages/_xmlplus/dom/minidom.py:663: Warning: invalid uninstantiatable type `(null)' in cast to `GstGnomeVFSSrc'
  self._attrsNS = {} #    tagName -> Attribute
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-06-03 23:05:36 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 ***