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))

[Muelli]

Binary package hint: rhythmbox

This is probably bug 492209. FWIW: RB was stopped. Meanwhlie my external harddrive was about to fail, i.e. I couldn't really read files anymore. Trying to make RB play resulted in RB stalling for ~5secs before popping up an error about the GStreamer Pipeline not able to start. I unplugged and replugged my harddrive. After hitting Play, RB apparently crashed.

ProblemType: Crash
Architecture: amd64
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: Sat Jan 30 22:21:52 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/rhythmbox
Package: rhythmbox 0.12.5-0ubuntu5.2
ProcCmdline: rhythmbox
ProcVersionSignature: Ubuntu 2.6.32-11.15-generic
Signal: 6
SourcePackage: rhythmbox
StacktraceTop:
 *__GI_raise (sig=<value optimised out>)
 *__GI_abort () at abort.c:92
 g_assertion_message () from /lib/libglib-2.0.so.0
 g_assertion_message_expr ()
 ?? () from /usr/lib/librhythmbox-core.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.32-11-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse kvm libvirtd lpadmin netdev plugdev powerdev scanner tty vboxusers video

[Apport retracing service (apport)]

Unsetting the need retracing tag, there is no retracer left running on that version of Ubuntu, the crash will need to be manually retraced

[Victor Vargas (kamus)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.