rhythmbox assert failure: RhythmDB:ERROR:rhythmdb-property-model.c:584:rhythmdb_property_model_prop_changed_cb: assertion failed: (g_hash_table_remove (propmodel->priv->entries, entry))

[lelamal]

Binary package hint: rhythmbox

I hit play and RB crashed.

ProblemType: Crash
Architecture: i386
AssertionMessage: RhythmDB:ERROR:rhythmdb-property-model.c:584:rhythmdb_property_model_prop_changed_cb: assertion failed: (g_hash_table_remove (propmodel->priv->entries, entry))
Date: Fri Dec 4 09:57:14 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: rhythmbox 0.12.5-0ubuntu5
ProcCmdline: rhythmbox
ProcEnviron:
 LANGUAGE=en_GB.UTF-8
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-15.50-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:584:rhythmdb_property_model_prop_changed_cb: assertion failed: (g_hash_table_remove (propmodel->priv->entries, entry))
Uname: Linux 2.6.31-15-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:__kernel_vsyscall ()
*__GI_raise (sig=6)
*__GI_abort () at abort.c:92
g_assertion_message () from /lib/libglib-2.0.so.0
g_assertion_message_expr () from /lib/libglib-2.0.so.0

[Pedro Villavicencio (pedro)]

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:
 https://bugzilla.gnome.org/show_bug.cgi?id=603781

[Pedro Villavicencio (pedro)]

This has been fixed upstream now:

"commit 754a72759885d63275b1a656d8c6f3f7c29c7e9d
Author: Jonathan Matthew <email address hidden>
Date: Mon Mar 15 22:47:22 2010 +1000

    rhythmdb: merge change lists from subsequent commits (bug #527898)

    When a second commit occurs before the changes from the first are
    emitted (in an idle handler), and both commits contain changes to the
    same entry, we need to combine the changes in the change map used to
    prepare for signal emission.

    Previously, the changes from the first commit were being overwritten,
    with the result that property models could get out of sync with the
    entries in the backing model, which would eventually lead to an
    assertion failure when trying to update the property model."

[Sebastien Bacher (seb128)]

the new version is in lucid now