rhythmbox crashed with SIGSEGV in rb_play_order_has_next()

[Dereck Wonnacott]

Binary package hint: rhythmbox

I try to play any song, it crashes just like this.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/rhythmbox
NonfreeKernelModules: nvidia
Package: rhythmbox 0.11.6svn20080916-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: rhythmbox
ProcEnviron:
 SHELL=/bin/bash
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 rb_play_order_has_next ()
 ?? ()
 ?? ()
 rb_shell_player_set_playing_source ()
 ?? ()
Title: rhythmbox crashed with SIGSEGV in rb_play_order_has_next()
Uname: Linux 2.6.27-4-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy leachers lpadmin netdev plugdev powerdev sambashare scanner video

[Apport retracing service (apport)]

StacktraceTop:rb_play_order_has_next (porder=0x7f54216d218d) at rb-play-order.c:756
rb_shell_player_play_order_update_cb (porder=<value optimized out>,
actually_set_playing_source (player=0x23b2000, source=0x25ce000, sync_entry_view=1)
rb_shell_player_set_playing_source (player=0x23b2000, source=0x25ce000)
rb_shell_player_property_row_activated_cb (view=<value optimized out>,

[Pedro Villavicencio (pedro)]

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=554288

[Omer Akram (om26er)]

Could you please confirm if this bug is still happening at your end ? Please try with Rhythmbox 0.12.8 or 0.13.2 and report back, thanks.

[Omer Akram (om26er)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

[Victor Vargas (kamus)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!