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 441165 - crash in Rhythmbox Music Player: Checking out radio stati...
crash in Rhythmbox Music Player: Checking out radio stati...
Status: RESOLVED DUPLICATE of bug 426586
Product: rhythmbox
Classification: Other
Component: general
0.10.0
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-05-25 11:29 UTC by svartiputti
Modified: 2007-05-25 13:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description svartiputti 2007-05-25 11:29:07 UTC
What were you doing when the application crashed?
Checking out radio stations in the left panel...
I'm using FC7 RC3 in a vmware virtual machine player (2.0)


Distribution: Fedora release 6.93 (Rawhide)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-1.3104.fc7 #1 SMP Sat Apr 21 22:20:43 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10299905
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 129949696 vsize: 129949696 resident: 44380160 share: 16539648 rss: 44380160 rss_rlim: 4294967295
CPU usage: start_time: 1180096006 rtime: 1553 utime: 806 stime: 747 cutime:1 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 -1208334080 (LWP 3431)]
[New Thread -1220363376 (LWP 3466)]
[New Thread -1266402416 (LWP 3446)]
[New Thread -1244685424 (LWP 3440)]
(no debugging symbols found)
0x0038a402 in __kernel_vsyscall ()

Thread 1 (Thread -1208334080 (LWP 3431))

  • #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 ??
    from /usr/lib/libpython2.5.so.1.0
  • #12 PyObject_Call
    from /usr/lib/libpython2.5.so.1.0
  • #13 PyEval_CallObjectWithKeywords
    from /usr/lib/libpython2.5.so.1.0
  • #14 PyObject_CallObject
    from /usr/lib/libpython2.5.so.1.0
  • #15 ??
    from /usr/lib/python2.5/site-packages/gtk-2.0/gobject/_gobject.so
  • #16 ??
    from /lib/libglib-2.0.so.0
  • #17 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #18 ??
    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 (36 sec old) ---------------------
(gnome-terminal:2794): Vte-WARNING **: Can not find appropiate font for character U+ac01.
(gnome-terminal:2794): Vte-WARNING **: Can not find appropiate font for character U+ac04.
(gnome-terminal:2794): Vte-WARNING **: Can not find appropiate font for character U+ac08.
(gnome-terminal:2794): Vte-WARNING **: Can not find appropiate font for character U+ac10.
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x4800021 (Music Play); these messages lack timestamps and therefore suck.
** 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.
sys:1: Warning: invalid unclassed pointer in cast to `GstGnomeVFSSrc'
--------------------------------------------------
Comment 1 James "Doc" Livingston 2007-05-25 13:12:02 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 ***