$ rhythmbox

(rhythmbox:18405): GLib-CRITICAL **: g_sequence_get: assertion `!is_end
(iter)' failed

(rhythmbox:18405): RhythmDB-CRITICAL **: rhythmdb_entry_get_string:
assertion `entry != NULL' failed

(rhythmbox:18405): RhythmDB-CRITICAL **: rhythmdb_entry_unref: assertion
`entry != NULL' failed

(rhythmbox:18405): GLib-CRITICAL **: g_sequence_get: assertion `!is_end
(iter)' failed

(rhythmbox:18405): RhythmDB-CRITICAL **: rhythmdb_entry_get_string:
assertion `entry != NULL' failed

(rhythmbox:18405): RhythmDB-CRITICAL **: rhythmdb_entry_unref: assertion
`entry != NULL' failed

(rhythmbox:18405): GLib-CRITICAL **: g_sequence_get: assertion `!is_end
(iter)' failed

(rhythmbox:18405): RhythmDB-CRITICAL **: rhythmdb_entry_get_ulong:
assertion `entry != NULL' failed

(rhythmbox:18405): RhythmDB-CRITICAL **: rhythmdb_entry_unref: assertion
`entry != NULL' failed

(rhythmbox:18405): GLib-CRITICAL **: g_sequence_get: assertion `!is_end
(iter)' failed

(rhythmbox:18405): RhythmDB-CRITICAL **: rhythmdb_entry_get_ulong:
assertion `entry != NULL' failed

(rhythmbox:18405): RhythmDB-CRITICAL **: rhythmdb_entry_get_ulong:
assertion `entry != NULL' failed

(rhythmbox:18405): RhythmDB-CRITICAL **: rhythmdb_entry_get_ulong:
assertion `entry != NULL' failed

(rhythmbox:18405): RhythmDB-CRITICAL **: rhythmdb_entry_unref: assertion
`entry != NULL' failed

(rhythmbox:18405): Gtk-CRITICAL **: file 
/build/buildd/gtk+2.0-2.12.0/gtk/gtktreeview.c: line 4890 
(gtk_tree_view_bin_expose): assertion `has_next' failed.
There is a disparity between the internal view of the GtkTreeView,
and the GtkTreeModel.  This generally means that the model has changed
without letting the view know.  Any display from now on is likely to
be incorrect.

-- 
Locks up when podcast download finishes
https://bugs.launchpad.net/bugs/140036
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Reply via email to