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 427076 - crash in Rhythmbox Music Player:
crash in Rhythmbox Music Player:
Status: RESOLVED DUPLICATE of bug 426586
Product: rhythmbox
Classification: Other
Component: general
0.9.8
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-04-06 21:08 UTC by pozas1956
Modified: 2007-04-21 01:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description pozas1956 2007-04-06 21:08:43 UTC
What were you doing when the application crashed?



Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.20-1.2933.fc6 #1 SMP Mon Mar 19 10:42:48 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled

Memory status: size: 277090304 vsize: 0 resident: 277090304 share: 0 rss: 113590272 rss_rlim: 0
CPU usage: start_time: 1175893181 rtime: 0 utime: 9659 stime: 0 cutime:9227 cstime: 0 timeout: 432 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 -1208981040 (LWP 9544)]
[New Thread -1300235376 (LWP 9687)]
[New Thread -1357911152 (LWP 9658)]
[New Thread -1273599088 (LWP 9551)]
(no debugging symbols found)
0x00b81402 in __kernel_vsyscall ()

Thread 1 (Thread -1208981040 (LWP 9544))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    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.4.so.1.0
  • #9 PyClassMethod_New
    from /usr/lib/libpython2.4.so.1.0
  • #10 PyObject_Call
    from /usr/lib/libpython2.4.so.1.0
  • #11 PyClass_IsSubclass
    from /usr/lib/libpython2.4.so.1.0
  • #12 PyObject_Call
    from /usr/lib/libpython2.4.so.1.0
  • #13 PyEval_CallObjectWithKeywords
    from /usr/lib/libpython2.4.so.1.0
  • #14 PyObject_CallObject
    from /usr/lib/libpython2.4.so.1.0
  • #15 ??
    from /usr/lib/python2.4/site-packages/gtk-2.0/gobject/_gobject.so
  • #16 g_source_get_current_time
    from /lib/libglib-2.0.so.0
  • #17 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #18 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #19 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #20 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (19 sec old) ---------------------
kdeinit: terminate KDE.
DCOP: unregister 'kded'
DCOP: unregister 'klauncher'
DCOPServer : slotSuicide() -> exit.
ICE default IO error handler doing an exit(), pid = 8374, errno = 0
(rhythmbox:9544): Rhythmbox-CRITICAL **: rb_player_gst_play: assertion `mp->priv->playbin != NULL' failed
** 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
rhythmbox: Python/ceval.c:2531: PyEval_EvalCodeEx: Assertion `tstate != ((void *)0)' failed.
** 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'
** (bug-buddy:9693): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-04-21 01:16:42 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 426586 ***