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 581373 - crash in Rhythmbox Music Player: rhythmbox crashed at the...
crash in Rhythmbox Music Player: rhythmbox crashed at the...
Status: RESOLVED DUPLICATE of bug 576031
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-04 20:57 UTC by Johannes Rohr
Modified: 2009-05-04 21:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Description Johannes Rohr 2009-05-04 20:57:14 UTC 
Version: 0.12.0

What were you doing when the application crashed?
rhythmbox crashed at the end of a track


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: Clearlooks
Icon Theme: Tango

Memory status: size: 194310144 vsize: 194310144 resident: 41791488 share: 14508032 rss: 41791488 rss_rlim: 18446744073709551615
CPU usage: start_time: 1241469583 rtime: 4318 utime: 3841 stime: 477 cutime:2 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb5584ac0 (LWP 22239)]
[New Thread 0xaf7d4b90 (LWP 22285)]
[New Thread 0xaffd5b90 (LWP 22284)]
[New Thread 0xb07d6b90 (LWP 22283)]
[New Thread 0xb1b05b90 (LWP 22280)]
[New Thread 0xb23ffb90 (LWP 22256)]
0xb8091424 in __kernel_vsyscall ()

+ Trace 215111

Thread 1 (Thread 0xb5584ac0 (LWP 22239))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /build/buildd-glib2.0_2.20.1-2-i386-hGzT8z/glib2.0-2.20.1/glib/gspawn.c line 382
  • #3 IA__g_spawn_command_line_sync
    at /build/buildd-glib2.0_2.20.1-2-i386-hGzT8z/glib2.0-2.20.1/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 unlink_blocked_cb
    at rb-player-gst-xfade.c line 1304
  • #8 rb_player_gst_xfade_bus_cb
    at rb-player-gst-xfade.c line 1758
  • #9 gst_bus_source_dispatch
    at gstbus.c line 831
  • #10 IA__g_main_context_dispatch
    at /build/buildd-glib2.0_2.20.1-2-i386-hGzT8z/glib2.0-2.20.1/glib/gmain.c line 1814
  • #11 g_main_context_iterate
    at /build/buildd-glib2.0_2.20.1-2-i386-hGzT8z/glib2.0-2.20.1/glib/gmain.c line 2448
  • #12 IA__g_main_loop_run
    at /build/buildd-glib2.0_2.20.1-2-i386-hGzT8z/glib2.0-2.20.1/glib/gmain.c line 2656
  • #13 IA__gtk_main
    at /build/buildd-gtk+2.0_2.16.1-2-i386-NWxSfb/gtk+2.0-2.16.1/gtk/gtkmain.c line 1205
  • #14 main
    at main.c line 336
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
Got Event! 100, -1
Got Event! 100, -1
Got Event! 100, -1
Got Event! 100, -1
Got Event! 100, -1
Got Event! 100, -1
Got Event! 100, -1
(rhythmbox:22239): GStreamer-CRITICAL **: gst_pad_unlink: assertion `GST_IS_PAD (sinkpad)' failed
(rhythmbox:22239): Rhythmbox-WARNING **: Couldn't unlink stream file:///home/data/music/%D0%9C%D0%B5%D0%BB%D1%8C%D0%BD%D0%B8%D1%86%D0%B0/%D0%97%D0%BE%D0%B2_%D0%BA%D1%80%D0%BE%D0%B2%D0%B8/12_-_%D0%9B%D
warning: Lowest section in /usr/lib/libicudata.so.40 is .hash at 000000b4
Cannot access memory at address 0x0
Cannot access memory at address 0x0
--------------------------------------------------
Comment 1 Gianluca Borello 2009-05-04 21:26:22 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 576031 ***