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 447381 - crash in Rhythmbox Music Player: trying to listen to musi...
crash in Rhythmbox Music Player: trying to listen to musi...
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-14 01:17 UTC by tomduffy
Modified: 2007-06-14 10:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description tomduffy 2007-06-14 01:17:00 UTC
What were you doing when the application crashed?
trying to listen to music


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: 147603456 vsize: 147603456 resident: 47464448 share: 18137088 rss: 47464448 rss_rlim: 4294967295
CPU usage: start_time: 1181783723 rtime: 1233 utime: 1126 stime: 107 cutime:2 cstime: 1 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 -1208161744 (LWP 2661)]
[New Thread -1341154416 (LWP 2711)]
[New Thread -1265792112 (LWP 2681)]
[New Thread -1220224112 (LWP 2676)]
[New Thread -1233245296 (LWP 2666)]
(no debugging symbols found)
0x00346402 in __kernel_vsyscall ()

Thread 1 (Thread -1208161744 (LWP 2661))

  • #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 __assert_fail
    from /lib/libc.so.6
  • #8 PyEval_EvalCodeEx
    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_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #12 PyEval_EvalCodeEx
    from /usr/lib/libpython2.5.so.1.0
  • #13 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #14 ??
    from /usr/lib/libpython2.5.so.1.0
  • #15 ??
    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 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #19 PyEval_EvalFrameEx
    from /usr/lib/libpython2.5.so.1.0
  • #20 PyEval_EvalFrameEx
    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 ??
    from /usr/lib/libpython2.5.so.1.0
  • #25 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #26 ??
    from /usr/lib/libpython2.5.so.1.0
  • #27 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #28 PyEval_CallObjectWithKeywords
    from /usr/lib/libpython2.5.so.1.0
  • #29 PyObject_CallObject
    from /usr/lib/libpython2.5.so.1.0
  • #30 ??
    from /usr/lib/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
  • #31 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #32 ??
    from /lib/libgobject-2.0.so.0
  • #33 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #34 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #35 ??
  • #36 g_cclosure_marshal_VOID__PARAM
    from /lib/libgobject-2.0.so.0
  • #37 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #38 ??
    from /lib/libgobject-2.0.so.0
  • #39 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #40 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #41 ??
    from /lib/libgobject-2.0.so.0
  • #42 ??
    from /lib/libgobject-2.0.so.0
  • #43 g_object_notify
    from /lib/libgobject-2.0.so.0
  • #44 ??
  • #45 rb_shell_player_do_next
  • #46 ??
  • #47 ??
  • #48 ??
    from /lib/libglib-2.0.so.0
  • #49 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #50 ??
    from /lib/libglib-2.0.so.0
  • #51 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #52 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #53 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (17 sec old) ---------------------
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
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
** 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'
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
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
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
rhythmbox: Python/ceval.c:2626: PyEval_EvalCodeEx: Assertion `tstate != ((void *)0)' failed.
/usr/lib/rhythmbox/plugins/artdisplay/LocalCoverArtSearch.py:56: Warning: invalid uninstantiatable type `(null)' in cast to `GstGnomeVFSSrc'
  print 'not searching for local art to', self.uri
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-06-14 10:28:48 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 ***