Hide Forgot
Description of problem: Rhythmbox does not find any plugins that are not part of the core of rhythmbox. I have tried many different python plugins from the fedora repos and manually installed and rhythmbox never finds them or just ignores them. I have tried installing the plugins in the ~/.gnome2/rhythmbox/plugins directory as well as /usr/lib/rhythmbox/plugins directory, but, they never show up in the plugins panel to activate them. Version-Release number of selected component (if applicable): How reproducible: Everytime you attempt to install a rhythmbox plugin. Steps to Reproduce: 1. Install any rhythmbox plugin (from fedora repos or manually) 2. Open rhythmbox and go to the plugins window to activate the new plugin 3. Actual results: The plugins never show up in the plugin panel. Expected results: The plugins should show up in the plugins window after installation (manual install or from repos) and restarting rhythmbox (if its running) Additional info: I'm using the default gnome 3 shell desktop environment.
please try running RB from a console and see if it displays any errors related to the plugins. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I have, but, as I stated in the original post, rhythmbox ignores ALL plugins that are not part of the default install. And, thus, reports no problems on the command line even when enabling debug output. Rhythmbox just never even tries to load any plugins other than those that are part of the default install.
I was hoping there might be some output when it tries to parse the plugins. "ignores" is a pretty vague term. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I experience this problem, too. Only the following plugins show up: "Audio CD Recorder", "Context Pane", "Cover art", "DAAP ...", "FM Radio", "Grilo...", "IM Status", "Last.fm", "Magnatune...", "MediaServer2...", "MPRIS...", "Notification", "Portable Players..." (x2), "Python Console", "ReplayGain", "Send tracks", "Song Lyrics", "Visualization", "Zeitgeist" (NB none of the plugins installed below) carl@chaffinch:~$ rpm -qa | grep rhythmbox rhythmbox-equalizer-1.4-2.fc15.x86_64 rhythmbox-2.90.1-17.git20110927.fc16.x86_64 (rhythmbox-equalizer installed just to test if packaged 3rd-party plugins work… they do not) carl@chaffinch:~$ ls .local/share/rhythmbox/plugins/ FullscreenView pandora rhythmarty rhythmbox-grooveshark rhythmbox-youtube rhythmcurse zeitgeist-plugin (NB they also don't work if stored in .gnome2) There are two problems with getting decent debug output: 1. There's too much, and it can't be redirected to a file properly (rhythmbox -d 2>&1 > rhythmbox.log only gives a few lines in rhythmbox.log, and a lot of console output) 2. I *still* can't find anything about a failure to load plugins Any tips on getting more information to help solve this problem are appreciated.
I have the same results as Carl and have tried all these things to get debug output but there seems to be none. I have even tried to filter the output for single plugins with the "-D <plugin name filter>" option but as stated they are never even attempted to be loaded. Its as if the plugins that are part of the default rhythmbox install are hard coded to be loaded and all other plugins are just ignored. I'm not sure how else to word this.
http://mail.gnome.org/archives/rhythmbox-devel/2011-October/msg00026.html https://github.com/mzheng/rhythmbox-pandora/issues/16 http://code.google.com/p/rhythmbox-shoutcast/issues/detail?id=29 So the bug is with the development process (and documentation), not the plugin loading code. Sigh.
Why did they break the old API? Why did they not just deprecate the old API before completely removing it? Its this type of thing that really ticks people off and why there is so much dislike for gnome3 and Unity. Redhat, being a major contributor to gnome, did they even consider this? It is bad practice to break API with out warning and not giving developers time to migrate to the new APIs, as well as being an unprofessional practice. GRRRRRRRRR!
"Why did they break the old API? Why did they not just deprecate the old API before completely removing it?" Because it's part of the migration from GTK+2 to GTK+3, essentially. The GTK+2 to GTK+3 migration has been in git for I think over a year, and the change to the plugin API has been mentioned multiple times on the mailing list in that span, so effectively what you ask for *has* happened: the stable GTK+2 branch has had the old plugin API all that time, effectively 'present but deprecated', while the unstable GTK+3 branch has had the new plugin API since at least March (though it's still unstable), and the change has been mentioned and discussed on the development ML, so it's not as if plugin authors couldn't have been aware of it coming and been able to migrate their plugins to it for quite some time. The changeover is necessarily a one-time thing in Fedora; I switched Fedora's RB to the GTK+ 3 branch, simply because the GTK+ 2 one was pretty much un-buildable any more now all our other bits have been switched over to GNOME 3 / GTK+ 3. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
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
This issue affects Fedora 17 and, presumably, 18.
presumably?
Adam W., if the API changed and no one is maintaining the plugins, David's reasoning seems well-founded. This is borne out by my experience on Fedora 17, with rhythmbox-2.97-1.fc17.x86_64 and rhythmbox-equalizer-1.4-3.fc17.x86_64. According to another report, the problem persists in F18: https://bugzilla.redhat.com/show_bug.cgi?id=896322 The problem was also reported as far back as F15: https://bugzilla.redhat.com/show_bug.cgi?id=746832 Perhaps the defective plugins should simply be removed from the repository if there's no hope of fixing them.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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 change the 'version' to a later Fedora version prior to Fedora 17's end of life. 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.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.