Hide Forgot
Created attachment 526548 [details] dump of the output from rhythmbox -d Description of problem: Rhythmbox crashes on startup Version-Release number of selected component (if applicable): Version : 2.90.1 Release : 17.git20110927.fc16 Architecture: x86_64 How reproducible: Always Steps to Reproduce: 1. start rhythmbox 2. 3. Actual results: rhythmbox crashes Expected results: rhythmbox works Additional info: [aneil2@island ~]$ rhythmbox /usr/lib64/python2.7/site-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:pygobject.c:929:pygobject_new_full: assertion failed: (tp != NULL) Aborted (core dumped)
Turns out it is the magnatune plugin that is the problem. removing /usr/lib64/rhythmbox/magnatune allows rhythmbox to start .
According to developer Owen Taylor: "Problem seems to be that Rhythmbox is using pygobject3 and gobject-introspection, but the Magnatune plugin imports gnome-keyring which is using pygobject2, and pygobejct2 and pygobject3 aren't playing nice in the same process." This bug is now being tracked upstream in the Gnome bug tracker: https://bugzilla.gnome.org/show_bug.cgi?id=661957
*** Bug 753330 has been marked as a duplicate of this bug. ***
Can the magnatune plugin be stripped out of fedora rhythmbox package until this is resolved? As the issue has stood for the last two months, there is an easy to access checkbox in rhythmbox (enable magnatune plugin) that will permanently disable rhythmbox for a novice user. The scenario: a novice looks at the list of plugins, says "huh, a music store - I'll give that a try," clicks enable, and the rhythmbox window disappears. Try to start rhythmbox again: nothing. It will not start. To fix it, the user has to edit dconf keys. It's even more confounding that in an upgraded system, the gconf settings are still there but have no effect in rhythmbox. This is such a mess. Just don't ship the plugin, or don't allow it to be enabled until it's fixed.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
It looks like that all bug reports for Fedora stay unsolved until they can be closed because the version they are reported to is end of life...