[03:30] <lubot_> [matrix] <arraybolt3> Hmm... well this is interesting. Added some info to a Debian bug report on the XScreenSaver Preview button being broken... and the XScreenSaver author jumped in. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014782
[03:30] -ubot93:#lubuntu-devel- Debian bug 1014782 in xscreensaver "xscreensaver: fails to activate via 'Preview' button or via 'Blank after' setting" [Important, Open]
[03:31] <lubot_> [matrix] <arraybolt3> If anyone sees something wrong with my proposed solution, or has an idea for a better solution, please say something.
[03:33] <lubot_> [matrix] <arraybolt3> Because Jamie (the XScreenSaver author) seems to think the solution I'm proposing is *horrible*. :P
[05:05] <lubot_> [matrix] <arraybolt3> Upon further debugging, I see the problem - it turns out XScreenSaver can use a config file located at *either* /etc/X11/app-defaults/XScreenSaver *or* /usr/lib/X11/app-defaults/XScreenSaver. The file at the /etc path is, I believe, generated by the XScreenSaver build process, and is faulty out of the starting gate (it has a couple of null variables that cause breakage, and possibly other problems). I think it just needs patched
[05:11] <lubot_> [matrix] <arraybolt3> Arguably, though, this may mean that lubuntu-default-settings is placing its configuration file in the wrong spot.
[05:11] <lubot_> [matrix] <arraybolt3> *its XScreenSaver configuration file
[05:59] <lubot_> [matrix] <arraybolt3> Hah, it's even easier than patching the file. A couple of extra config options should solve it.
[07:52] <lubot_> [matrix] <arraybolt3> OK, more debugging, one of those config options is there already and is getting ignored, so I'm finding out why it's being ignored.
[20:00] <lubot_> [matrix] <arraybolt3> I think I have the XScreenSaver problem for distros other than Lubuntu figured out. Needed a change to one config option and possibly a second one added. Going to do some more testing.