GNOME Bugzilla – Bug 667587
Rhythmbox does not start.
Last modified: 2012-01-09 21:02:52 UTC
ms@ms-Dimension-8200:~$ rhythmbox Gtk-WARNING **: SearchAll: missing action AutoPlaylistSearchAll Gtk-WARNING **: SearchArtists: missing action AutoPlaylistSearchArtists Gtk-WARNING **: SearchAlbums: missing action AutoPlaylistSearchAlbums Gtk-WARNING **: SearchTitles: missing action AutoPlaylistSearchTitles Gtk-WARNING **: SearchAll: missing action AutoPlaylistSearchAll Gtk-WARNING **: SearchArtists: missing action AutoPlaylistSearchArtists Gtk-WARNING **: SearchAlbums: missing action AutoPlaylistSearchAlbums Gtk-WARNING **: SearchTitles: missing action AutoPlaylistSearchTitles /usr/lib/python2.7/dist-packages/gobject/constants.py:24: Warning: g_boxed_type_register_static: assertion `g_type_from_name (name) == 0' failed import gobject._gobject TypeError: metaclass conflict: the metaclass of a derived class must be a (non-strict) subclass of the metaclasses of all its bases ** ERROR:/build/buildd/pygobject-3.0.3/gi/_gobject/pygobject.c:929:pygobject_new_full: assertion failed: (tp != NULL) Aborted (core dumped) ms@ms-Dimension-8200:~$
This looks like you have a python plugin enabled that loads some static bindings. What output do you get from 'gsettings get org.gnome.rhythmbox.plugins active-plugins'?
This is what I get: ms@ms-Dimension-8200:~$ gsettings get org.gnome.rhythmbox.plugins active-plugins ['dbus-media-server', 'mpris', 'ipod', 'magnatune', 'iradio', 'notification', 'power-manager', 'cd-recorder', 'audiocd', 'mtpdevice', 'audioscrobbler', 'generic-player', 'rb', 'mmkeys'] ms@ms-Dimension-8200:~$
By the way, I am running Ubuntu 11.10 and yesterday I applied a distro upgrade command: sudo apt-get dist-upgrade
ok, run this: gsettings set org.gnome.rhythmbox.plugins active-plugins "['dbus-media-server', 'mpris', 'ipod', 'iradio', 'notification', 'power-manager', 'cd-recorder', 'audiocd', 'mtpdevice', 'audioscrobbler', 'generic-player', 'rb', 'mmkeys']" The magnatune plugin is broken for now. *** This bug has been marked as a duplicate of bug 661957 ***
OK, issue resolved. Thank you.