Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will help us to find and resolve the problem.
** Changed in: rhythmbox (Ubuntu)
Importance: Medium => Low
** Changed in: rhythmbox (Ubuntu)
Status: Confirmed => Incomplete
** Information type changed from Private to Public
** Summary changed:
- rhythmbox crashed with SIGABRT in g_assertion_message()
+ rhythmbox crashed with SIGABRT in g_assertion_message()
(hash_table->ref_count > 0)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/1444580
Title:
rhythmbox crashed with SIGABRT in g_assertion_message()
(hash_table->ref_count > 0)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1444580/+subscriptions
--
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
