Public bug reported:

For a few years, I used Ubuntu 12.04. I used rhythmbox in it all these
years, it worked fine. Some library was collected.

Then I upgraded to 14.04, and to 16.04 right away.

$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS"

After I start rhythmbox, in a few seconds it crashes, even if I do
nothing. Here is the output:

(rhythmbox:22810): Gtk-WARNING **: Duplicate child name in GtkStack: Add
to Playlist


(rhythmbox:22810): Gtk-WARNING **: Duplicate child name in GtkStack: Add to 
Playlist


(rhythmbox:22810): Gtk-WARNING **: Duplicate child name in GtkStack: Add to 
Playlist


(rhythmbox:22810): Gtk-WARNING **: Duplicate child name in GtkStack: Add to 
Playlist


(rhythmbox:22810): Gtk-WARNING **: Duplicate child name in GtkStack: Add to 
Playlist


(rhythmbox:22810): Gtk-WARNING **: Duplicate child name in GtkStack: Add to 
Playlist


(rhythmbox:22810): Gtk-WARNING **: Duplicate child name in GtkStack: Add to 
Playlist


(rhythmbox:22810): Gtk-WARNING **: Duplicate child name in GtkStack: Add to 
Playlist


(rhythmbox:22810): RhythmDB-CRITICAL **: rhythmdb_entry_get_entry_type: 
assertion 'entry != NULL' failed
Ошибка сегментирования (сделан дамп памяти)


rhythmbox version is 3.3-1ubuntu7.

I'm filing this bug here by hand because aport does not see these
crashes for some reason.

** Affects: rhythmbox (Ubuntu)
     Importance: Undecided
         Status: New

-- 
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/1630455

Title:
  rhythmbox crashes soon after being start in Ubuntu 16.04.1 with
  rhythmdb_entry_get_entry_type: assertion 'entry != NULL' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1630455/+subscriptions

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

Reply via email to