GNOME Bugzilla – Bug 582041
At every start "Unable to activate plugin Audio CD Recorder" but it is not listed in plugins...
Last modified: 2010-01-08 01:25:51 UTC
Please describe the problem: I try to use Rhythmbox on a computer that does not have a CD drive, and at every start it comes up with the message: Plugin Error: Unable to activate plugin Audio CD Recorder The error itself is clear, sure I don't have anything to record CD with, but when I check it in the Edit/Plugin list, I cannot find it anywhere to disable it... Steps to reproduce: 1. Install rhythmbox without brasero but with cd-recorder plugin included 2. Run program Actual results: Plugin Error: Unable to activate plugin Audio CD Recorder Expected results: No error, and Audio CD recorder disabled Does this happen every time? yes Other information: If I install Brasero, the error message goes away, but the plugin is still not shown in the list. As I checked, libcd-recorder.so is missing the libbrasero-media.so.0 dependency in my version (packaged for Arch Linux) and that's why it crashes at the start. This also suggest that if someone does not want brasero for any reason (like I usually use xfburn on my other machines that do have CD drive), they would have the same error as well, without any change to getting rid of it... So, is cd-recorder a proper plugin? If so, why does it not show in the list of plugins? If not, is it possible to disable it without recompiling the program?
If you can install rhythmbox without installing a shared library that one of its plugins depends on, the package dependencies (or whatever arch uses) are wrong. The CD burning plugin is a real plugin, it just doesn't appear in the plugin list because there's no real reason to disable it. If you don't have a CD burner, the plugin is completely invisible. If you really want to disable it, you can set the gconf key /apps/rhythmbox/plugins/cd-recorder/active to false.
(In reply to comment #1) > If you can install rhythmbox without installing a shared library that one of > its plugins depends on, the package dependencies (or whatever arch uses) are > wrong. I have to check that one with the package maintainers. brasero is listed as an optional dependency in this case. > The CD burning plugin is a real plugin, it just doesn't appear in the plugin > list because there's no real reason to disable it. If you don't have a CD > burner, the plugin is completely invisible. If you really want to disable it, > you can set the gconf key /apps/rhythmbox/plugins/cd-recorder/active to false. If there's a way to disable it, why not do the same thing as any other plugin? It is very confusing that it is indeed a real plugin but not listed among the others, and that you can disable it but have to jump hoops instead of doing what the other "real" plugins do... What really makes this one an exception?
(In reply to comment #2) > > The CD burning plugin is a real plugin, it just doesn't appear in the plugin > > list because there's no real reason to disable it. If you don't have a CD > > burner, the plugin is completely invisible. If you really want to disable it, > > you can set the gconf key /apps/rhythmbox/plugins/cd-recorder/active to false. > > If there's a way to disable it, why not do the same thing as any other plugin? > It is very confusing that it is indeed a real plugin but not listed among the > others, and that you can disable it but have to jump hoops instead of doing > what the other "real" plugins do... > What really makes this one an exception? The plugin list is too cluttered, so we hide plugins that we don't consider it useful to be able to disable. If you don't want to use it, just don't use it.
(In reply to comment #3) > (In reply to comment #2) > > > The CD burning plugin is a real plugin, it just doesn't appear in the plugin > > > list because there's no real reason to disable it. If you don't have a CD > > > burner, the plugin is completely invisible. If you really want to disable it, > > > you can set the gconf key /apps/rhythmbox/plugins/cd-recorder/active to false. > > > > If there's a way to disable it, why not do the same thing as any other plugin? > > It is very confusing that it is indeed a real plugin but not listed among the > > others, and that you can disable it but have to jump hoops instead of doing > > what the other "real" plugins do... > > What really makes this one an exception? > > The plugin list is too cluttered, so we hide plugins that we don't consider it > useful to be able to disable. If you don't want to use it, just don't use it. > That is just a list, with a scrollbar. As simple as possible. I cannot see how one extra line is causing more "clutter", or for that matter, even 20 extra line would cause that. "Plugins" are by definition _many_, and I'd certainly vote for treating them all equal, as something that for you us "not useful to control", there are plenty of other people for whom it will be. And i'm using xfce, so in general it integrates differently. cannot see why people should dig around in gconf to get a simple click done, that they can do with two dozen or so other plugins. This is just my opinion: if it's a plugin, should be in the plugin list. If you guys don't see the logic of this, just close this bug....
The fact that it's a plugin is an implementation detail. It allowed us to replace the nautilus-cd-burner plugin with a brasero based one easily. This is a distribution problem, as the brasero libraries are required to have that plugin working.
I just don't believe you offer users to use gconf to disable this plugin! You are saying that if I don't want to use this plugin I must: 1. Install brasero to stop the annoying message?!? Or 2. Make use of gconf to disable the plugin?!? Why this have to be so weird?! This application have nothing to do with burning cd's! The plugin was to be just an extension for the application! I think this application must come with this plugin disabled or without it, and *if* the user want it, he enables it.