Keywords :. Reported: UTC by Steve. Bug Fix. Attachments Terms of Use Add an attachment proposed patch, testcase, etc. Description Steve UTC Description of problem: screensavers does not appear in the "Screensaver Preferences" Version-Release number of selected component if applicable : xscreensaver-base How reproducible: by installing all these components the rss-glx-modules does not appear in the "Screensaver Preferences" Steps to Reproduce: 1. You need to have rss-glx-gnome-screensaver installed for them to show up in the preferences dialog.
Comment 2 Steve UTC yes, i'm using xscreensaver, i don't like the gnome-screensaver and i don't have the gnome-sreensaver installed. Comment 3 Steve UTC same ting with versions: rss-glx-xscreensaver Comment 5 Steve UTC same thing in fc6, no "really slick screensavers" in xscreensaver. Comment 8 Steve UTC is there anyone with working rss-glx-xscreensaver's? Ernzer UTC same problem as described in original bug report.
I see that the app-default file contains all of the hacks contained in the various xscreensaver subpackages but that is obviously not something we can do for external packages ;-. One idea would be to have an "update-xscreensaver-hacks" script which just grabs the definitions of the available hacks from a well known location, or even from the XML files if upstream cooperates , adds some boilerplate to top and bottom of that and writes the AD file anew.
I'll apply some of them and then do the 5. Actually the license that xscreensaver uses isn't quite the "modified BSD"; it contains says the copyright must appear "in supporting documentation", which is a requirement that GPL does not have; therefore, GPL declares itself incompatible with it, since GPL does not allow any restrictions that are not already in GPL.
So that "documentation" clause poses roughly the same problem as the "advertising" clause did. It's a historical accident that that clause is in there I don't feel strongly about it but it's too late to change it now, since doing so would require the permission of everyone who had ever sent in a patch.
Anyway, the result is that I think it's illegal to bundle xscreensaver and the "really slick" savers together. Several times I asked the author of those savers if he would change them to be dual licensed GPL and BSD, similar to what Mozilla does to make it possible to distribute them with xscreensaver, and he refused.
So, my feeling is, if he doesn't care, why should I? It's his loss. I don't think there would be a problem with just listing the names of his savers in the.
An example: flux Flux is a screensaver of rss-glx package. If i run flux from command line, a window with it is opening normal showing screensaver. Now, when i run gnome-screensaver-preference, i see Flux in my screensavers list. If i select Flux, on the right window there is no preview all black and if i try to force screensaver to start or lock , my screen goes black but after i move mouse, password box is shown and i can unlock screensaver.
I can't understand why i am the only one who find out this problem with Arch I have the same problem.
Lock on activation. Set this to TRUE to lock the screen when the screensaver goes active. Time before locking. The number of seconds after screensaver activation before locking the screen. Allow user switching. Ok I want to try this however when I tried the command sudo apt-get remove gnome-screensaver. I am told that I will be removing all of gnome. With that being the only desktop I knew better than to do that. The command, as you typed above, will only remove the gnome screensaver.
DemocritusJr, the gnome-core metapackage depends on gnome-screensaver, and the gnome metapackage depends on gnome-core. Removing gnome-screensaver forces the removal of these two metapackages. That is why I assumed a typo.
I am running Ubuntu I have had no dependency issues with gnome and have run apt-get autoclean without incident. Perhaps, lonnie is running a different os or desktop environment. What went wrong? Are you using Ubuntu?
0コメント