Bug#961129: xscreensaver should not search for screensaver executables in PATH
It has been another 5 months with no response. I am once again *begging* you to stop making it possible to install only *part* of XScreenSaver. It causes a constant stream of problems for no benefit. Please, please, please, install the dependencies so that installing any part of XScreenSaver installs *the entire program* as I have designed and tested it. This requires only a one line change to your dependency list. Your continued refusal to do this keeps causing problems for everybody, including me. -- Jamie Zawinski https://www.jwz.org/ https://www.dnalounge.com/
Bug#961129: xscreensaver should not search for screensaver executables in PATH
You could solve this problem with a one-line change: simply make "xscreensaver" depend upon "xscreensaver-data", "xscreensaver-data-extra", "xscreensaver-gl", "xscreensaver-gl-extra", "xscreensaver-screensaver-bsod" and "xscreensaver-screensaver-webcollage". I can see the argument for allowing the hacks to be installed without the XScreenSaver daemon, in case some other screen saver framework wanted to run them (do any of the other frameworks still support that? I don't think so?) However, if the XScreenSaver daemon is installed, then *all* of XScreenSaver must be installed, or else you get the "zoom" problem and related. That is how it was designed, and that is how it was tested. Trying to install bits and pieces of it and hoping it still holds together demonstrably does not work. -- Jamie Zawinski https://www.jwz.org/ https://www.dnalounge.com/
Bug#961129: xscreensaver should not search for screensaver executables in PATH
On Oct 13, 2021, at 4:36 AM, Tormod Volden wrote: > > I was obviously talking about what to do in the Debian package, not > upstream. So was I. I was discussing *your* decisions that make *my* program malfunction for *my* users, and cause more work for *me*, the author and maintainer. > I think it makes sense for us to not blindly pick whatever is in the user's > PATH. You are absolutely 100% wrong. Do not make this change. Many things will malfunction. Do not make the mistake of forking my program even more than you already have. That does not go well for any of us. -- Jamie Zawinski https://www.jwz.org/ https://www.dnalounge.com/
Bug#961129: xscreensaver should not search for screensaver executables in PATH
Please behave when using the Debian forums. I was obviously talking about what to do in the Debian package, not upstream. I think it makes sense for us to not blindly pick whatever is in the user's PATH. And we will eventually get to reunifying the packages, it is a bit more work though due to assuring all kinds of version upgrade paths will work smoothly and coordination with other packages that might use and depend on these packages.
Bug#961129: xscreensaver should not search for screensaver executables in PATH
On Oct 12, 2021, at 4:53 AM, Tormod Volden wrote: > > I agree to "xscreensaver SHOULD search for screensavers only in > /usr/lib/xscreensaver, Well, you're wrong, and I'm not going to do that. The fix is *simple and obvious*, make there be ONE xscreensaver installer package instead of FIVE -- one that installs *all* of XScreenSaver instead of only bits and pieces and expecting that to still work. I cannot comprehend why you continue to refuse to implement this trivial fucking fix. -- Jamie Zawinski https://www.jwz.org/ https://www.dnalounge.com/
Bug#961129: xscreensaver should not search for screensaver executables in PATH
I agree to "xscreensaver SHOULD search for screensavers only in /usr/lib/xscreensaver, where other packages are expected to install them", with the exception to allow users to specify a full path in their xscreensaver config, in case they want to use something installed elsewhere. There were objections to this also though, but I guess one cannot please them all. Tormod
Bug#961129: xscreensaver should not search for screensaver executables in PATH
On Thu, 7 Oct 2021 00:35:18 +0300 Dmitry Semyonov wrote: > On Wed, 20 May 2020 13:46:02 +0100 Andrew Gallagher wrote: > > > Beware for example that `zoom` is the name of a known screensaver. I am > > glad that I do not have xscreensaver and zoom.us installed on the same > > machine. :-) > > Well, my kid does, and since he didn't notice the XScreenSaver error > about the missing binary Actually, the proprietary zoom silently ignores all(?) unrecognized options, so I'm not even sure there were any visible indicators of the issue besides the unexpected zoom icon in systray. -- ...Bye..Dmitry.
Bug#961129: xscreensaver should not search for screensaver executables in PATH
On Wed, 20 May 2020 13:46:02 +0100 Andrew Gallagher wrote: > Beware for example that `zoom` is the name of a known screensaver. I am glad > that I do not have xscreensaver and zoom.us installed on the same machine. :-) Well, my kid does, and since he didn't notice the XScreenSaver error about the missing binary, I had an interesting experience of tracking down the root cause of malware-like behavior manifested by the above bundle. -- ...Bye..Dmitry.
Bug#961129: xscreensaver should not search for screensaver executables in PATH
Thanks for the report, this has been discussed in bug #816722 as well. Tormod
Bug#961129: xscreensaver should not search for screensaver executables in PATH
Package: xscreensaver Version: 5.42+dfsg1-1 Severity: important Dear Maintainer, Ever since I installed the magic-wormhole package, I have noticed that xscreensaver occasionally throws an error on the screen as follows: ``` Usage: wormhole [OPTIONS] COMMAND [ARGS]... Try "wormhole --help" for help. Error: no such option: -r ``` Luckily, invoking magic-wormhole with invalid options does not result in anything dangerous happening, but it raises the question whether potentially dangerous unintended behaviour is possible. I believe this happens because xscreensaver is searching for known screensaver binaries, and finding `wormhole` in the PATH it blindly assumes that this is the `wormhole` from xscreensaver-data-extra, but it is not installed. xscreensaver SHOULD search for screensavers only in /usr/lib/xscreensaver, where other packages are expected to install them. Any other executable on the PATH which may happen to have the same name as a known screensaver MUST NOT be invoked, as this may result in unintended behaviour. Beware for example that `zoom` is the name of a known screensaver. I am glad that I do not have xscreensaver and zoom.us installed on the same machine. :-) Andrew. -- System Information: Debian Release: 10.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'oldoldstable'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-0.bpo.2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xscreensaver depends on: ii libatk1.0-0 2.30.0-2 ii libc62.28-10 ii libcairo21.16.0-4 ii libfontconfig1 2.13.1-2 ii libfreetype6 2.9.1-3+deb10u1 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libglade2-0 1:2.6.4-2+b1 ii libglib2.0-0 2.58.3-2+deb10u2 ii libgtk2.0-0 2.24.32-3 ii libice6 2:1.0.9-2 ii libpam0g 1.3.1-5 ii libpango-1.0-0 1.42.4-8~deb10u1 ii libpangocairo-1.0-0 1.42.4-8~deb10u1 ii libpangoft2-1.0-01.42.4-8~deb10u1 ii libsm6 2:1.2.3-1 ii libx11-6 2:1.6.7-1 ii libxext6 2:1.3.3-1+b2 ii libxi6 2:1.7.9-1 ii libxinerama1 2:1.1.4-2 ii libxml2 2.9.4+dfsg1-7+b3 ii libxmu6 2:1.1.2-2+b3 ii libxrandr2 2:1.5.1-1 ii libxrender1 1:0.9.10-1 ii libxt6 1:1.1.5-1+b3 ii libxxf86vm1 1:1.1.4-1+b2 ii xscreensaver-data5.42+dfsg1-1 Versions of packages xscreensaver recommends: ii libjpeg-turbo-progs 1:1.5.2-2+b1 ii perl 5.28.1-6 ii wamerican [wordlist] 2018.04.16-1 Versions of packages xscreensaver suggests: ii firefox-esr [www-browser] 68.8.0esr-1~deb10u1 pn fortune ii gdm3 3.30.2-3 ii links [www-browser]2.18-2 ii lynx [www-browser] 2.8.9rel.1-3 pn qcam | streamer ii w3m [www-browser] 0.5.3-37 pn xdaliclock pn xfishtank pn xscreensaver-data-extra pn xscreensaver-gl pn xscreensaver-gl-extra -- no debconf information
