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 583678 - crash in Rhythmbox Music Player: Had Rhythmbox running fo...
crash in Rhythmbox Music Player: Had Rhythmbox running fo...
Status: RESOLVED DUPLICATE of bug 575781
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-23 20:32 UTC by gunnar.stahl
Modified: 2009-05-23 23:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Description gunnar.stahl 2009-05-23 20:32:43 UTC 
Version: 0.12.0

What were you doing when the application crashed?
Had Rhythmbox running for some time. Clicked on the link "Magnatune". The Magnatune start page (with the informations about what Magnatune is) opened. After about 5 seconds Rhythmbox crashed.


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

System: Linux 2.6.26-2-686 #1 SMP Thu Mar 26 01:08:11 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Amaranth
Icon Theme: Amaranth

Memory status: size: 149536768 vsize: 149536768 resident: 47685632 share: 24203264 rss: 47685632 rss_rlim: 18446744073709551615
CPU usage: start_time: 1243095509 rtime: 2058 utime: 1704 stime: 354 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb538a770 (LWP 5977)]
[New Thread 0xb219eb90 (LWP 3540)]
[New Thread 0xb449eb90 (LWP 5988)]
0xb7f66424 in __kernel_vsyscall ()

+ Trace 215667

Thread 1 (Thread 0xb538a770 (LWP 5977))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /build/buildd-glib2.0_2.20.0-2-i386-rcJiVy/glib2.0-2.20.0/glib/gspawn.c line 382
  • #3 IA__g_spawn_command_line_sync
    at /build/buildd-glib2.0_2.20.0-2-i386-rcJiVy/glib2.0-2.20.0/glib/gspawn.c line 694
  • #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
    at ../Python/pythonrun.c line 1561
  • #11 PyEval_SaveThread
    at ../Python/ceval.c line 316
  • #12 ??
    from /usr/lib/pymodules/python2.5/gtk-2.0/gobject/_gobject.so
  • #13 ??
  • #14 ??
  • #15 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
(rhythmbox:5977): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
(rhythmbox:5977): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
(rhythmbox:5977): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
(rhythmbox:5977): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
(rhythmbox:5977): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
(rhythmbox:5977): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
Fatal Python error: PyEval_SaveThread: NULL tstate
warning: Lowest section in /usr/lib/libicudata.so.40 is .hash at 000000b4
--------------------------------------------------
Comment 1 Jonathan Matthew 2009-05-23 23:47:25 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 575781 ***