rhythmbox assert failure: RhythmDB:ERROR:rhythmdb-property-model.c:705:rhythmdb_property_model_delete_prop: assertion failed: ((ptr = g_hash_table_lookup (model->priv->reverse_map, propstr)))

[ignoble]

Binary package hint: rhythmbox

1) I use Ubuntu 9.10 (Karmic).
2) I use version 0.12.5-0ubuntu4 of the rhythmbox package.
3) I had added a new webradio station (http://streamingserver01.byte.fm:8000/), double clicked it and it played properly. While the programme was still playing, I wanted to change the name of the station (right-click, properties).
4) When I had entered the new name and pressed the return key to confirm the change, Rhythmbox crashed: the playback stopped, the window and the panel symbol disappeared, the apport dialogue appeared after a while.

ProblemType: Crash
Architecture: i386
AssertionMessage: RhythmDB:ERROR:rhythmdb-property-model.c:705:rhythmdb_property_model_delete_prop: assertion failed: ((ptr = g_hash_table_lookup (model->priv->reverse_map, propstr)))
CrashCounter: 1
Date: Sun Nov 8 13:47:35 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/rhythmbox
NonfreeKernelModules: nvidia
Package: rhythmbox 0.12.5-0ubuntu4
ProcCmdline: rhythmbox
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
Signal: 6
SourcePackage: rhythmbox
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libc.so.6
 abort () from /lib/tls/i686/cmov/libc.so.6
 g_assertion_message () from /lib/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/libglib-2.0.so.0
Title: rhythmbox assert failure: RhythmDB:ERROR:rhythmdb-property-model.c:705:rhythmdb_property_model_delete_prop: assertion failed: ((ptr = g_hash_table_lookup (model->priv->reverse_map, propstr)))
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #429030, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.