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 582135 - crash in Rhythmbox Music Player: Selected the magnatune p...
crash in Rhythmbox Music Player: Selected the magnatune p...
Status: RESOLVED DUPLICATE of bug 581928
Product: rhythmbox
Classification: Other
Component: general
0.12.x
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-05-11 08:25 UTC by p.vandereems
Modified: 2009-05-11 08:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Description p.vandereems 2009-05-11 08:25:25 UTC 
Version: 0.12.0

What were you doing when the application crashed?
Selected the magnatune plugin.


Distribution: Debian squeeze/sid
Gnome Release: 2.26.1 2009-04-14 (Debian)
BugBuddy Version: 2.24.2

System: Linux 2.6.29-1-686 #1 SMP Fri Apr 17 14:35:16 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10601000
Selinux: No
Accessibility: Disabled
GTK+ Theme: MurrinaVerdeOlivo
Icon Theme: Human

Memory status: size: 120672256 vsize: 120672256 resident: 37822464 share: 21217280 rss: 37822464 rss_rlim: 18446744073709551615
CPU usage: start_time: 1242029976 rtime: 298 utime: 266 stime: 32 cutime:3 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/rhythmbox'

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb55c6ac0 (LWP 19115)]
[New Thread 0xb21ffb90 (LWP 19203)]
[New Thread 0xb4726b90 (LWP 19132)]
[New Thread 0xb345fb90 (LWP 19122)]
(no debugging symbols found)
0xb80d3424 in __kernel_vsyscall ()

+ Trace 215319

Thread 1 (Thread 0xb55c6ac0 (LWP 19115))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 <signal handler called>
  • #7 __kernel_vsyscall
  • #8 raise
    from /lib/i686/cmov/libc.so.6
  • #9 abort
    from /lib/i686/cmov/libc.so.6
  • #10 Py_FatalError
    from /usr/lib/libpython2.5.so.1.0
  • #11 PyEval_SaveThread
    from /usr/lib/libpython2.5.so.1.0
  • #12 ??
    from /usr/lib/pymodules/python2.5/gtk-2.0/gobject/_gobject.so
  • #13 ??
  • #14 ??
  • #15 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
(filezilla:18895): Gtk-WARNING **: /build/buildd-gtk+2.0_2.16.1-2-i386-NWxSfb/gtk+2.0-2.16.1/gtk/gtkwidget.c:9103: widget class `GtkPizza' has no property named `row-ending-details'
(filezilla:18895): Gtk-WARNING **: /build/buildd-gtk+2.0_2.16.1-2-i386-NWxSfb/gtk+2.0-2.16.1/gtk/gtkwidget.c:9103: widget class `GtkPizza' has no property named `row-ending-details'
(filezilla:18895): Gtk-WARNING **: /build/buildd-gtk+2.0_2.16.1-2-i386-NWxSfb/gtk+2.0-2.16.1/gtk/gtkwidget.c:9103: widget class `GtkPizza' has no property named `row-ending-details'
(filezilla:18895): Gtk-WARNING **: /build/buildd-gtk+2.0_2.16.1-2-i386-NWxSfb/gtk+2.0-2.16.1/gtk/gtkwidget.c:9103: widget class `GtkPizza' has no property named `row-ending-details'
(filezilla:18895): Gtk-WARNING **: /build/buildd-gtk+2.0_2.16.1-2-i386-NWxSfb/gtk+2.0-2.16.1/gtk/gtkwidget.c:9103: widget class `GtkPizza' has no property named `row-ending-details'
(filezilla:18895): Gtk-WARNING **: /build/buildd-gtk+2.0_2.16.1-2-i386-NWxSfb/gtk+2.0-2.16.1/gtk/gtkwidget.c:9103: widget class `GtkPizza' has no property named `row-ending-details'
Fatal Python error: PyEval_SaveThread: NULL tstate
warning: Lowest section in /usr/lib/libicudata.so.40 is .hash at 000000b4
--------------------------------------------------
Comment 1 Gianluca Borello 2009-05-11 08:52:37 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 581928 ***