Bug#510319: workaround, requires root.
bear at sonic.net
Wed Aug 3 02:53:06 UTC 2011
-----BEGIN PGP SIGNED MESSAGE-----
Just by the way, this bug is annoying as hell. xscreensaver allowed
setting individual options for different screensavers. Replacing it
with gnome-screensaver when gnome-screensaver does not, AND
gnome-screensaver still had bugs in power management on laptops, was a
loss of user functionality in both functions. gnome-screensaver
was not (and still is not) ready for prime time and should not
have been made the default until it is fixed.
That said, here's a hamfisted workaround.
If you type
pkg-config --variable=themesdir gnome-screensaver
at a prompt, it will tell you the directory where the screensaver
desktop files are stored.
These files contain the .desktop files used to start the screensavers
The settings you're interested in get passed to the individual
screensavers via the command lines stored in these files.
You can edit the settings of individual screensavers by editing the
command line options in the respective desktop files.
This workaround is hamfisted in the following ways.
you have to be root to edit these files.
you can 'break' screensavers if you get it wrong, so be sure you
can revert your changes in case you mess it up.
The changes you make will affect *ALL* user accounts (so you
probably don't want to set a slideshow on your private
photos if anyone else has an account on the machine).
This workaround allows interesting functionality in the following ways:
a different .desktop file will show up as a different screensaver
in gnome-screensaver -- so you can invoke existing
screensaver programs with different sets of arguments as
though they were several different screensavers.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
More information about the pkg-gnome-maintainers