On 2/14/23 05:25, Jonathan Dowland wrote:
On Sat, Jan 21, 2023 at 09:26:03PM -0600, Aaron Rainbolt wrote:
If the XScreenSaver configuration file is included as a part of the
core xscreensaver package itself, as a file that is simply unpacked,
the following situation will result:
…
If the
On Sat, Jan 21, 2023 at 09:26:03PM -0600, Aaron Rainbolt wrote:
If the XScreenSaver configuration file is included as a part of the
core xscreensaver package itself, as a file that is simply unpacked,
the following situation will result:
…
If the configuration file is split out into its own
Note that Debian hasn't installed any
/usr/lib/X11/app-defaults/XScreenSaver at least since 2000
(xscreensaver 3.26). The installation (postinst) would also for a long
time remove any stale fiiles from that location. The app defaults file
is shipped in /etc/X11/app-defaults. If Lubuntu has been
You are making this all needlessly complicated. Each distro should have exactly
one xscreensaver package which contains exactly one app-defaults file, with
whatever patches are necessary to that. Which should be "just about none", as
configure should have figured out the correct settings for
(When am I going to start using the right email address? For crying out
loud, Thunderbird.)
On 1/21/23 21:11, Jamie Zawinski wrote:
No. There should be exactly one XScreenSaver package. So, so many problems have
stemmed from this incomplete, broken installations as a result of this
No. There should be exactly one XScreenSaver package. So, so many problems have
stemmed from this incomplete, broken installations as a result of this
ridiculous extras-data-extras-gl-extras-extras nonsense. I am decades weary of
hearing about them.
On 1/21/23 19:36, Jamie Zawinski wrote:
Yes, it is critical that the version of /usr/lib/X11/app-defaults/XScreenSaver
actually correspond to the version of XScreenSaver that is installed. I would
have thought this to be obvious.
If the file does not exist at all, things *should* work ok, but
Yes, it is critical that the version of /usr/lib/X11/app-defaults/XScreenSaver
actually correspond to the version of XScreenSaver that is installed. I would
have thought this to be obvious.
If the file does not exist at all, things *should* work ok, but having an old
version there is
Actually, it dawns on me that the whole "virtual package" thing is
overly complicated - just making an xscreensaver-config package should
be good enough, and anything that needs to replace it can use a
Conflicts/Provides to replace it.
Package: xscreensaver
Version: 6.02+dfsg1-2+b1
Followup-For: Bug #1014782
X-Debbugs-Cc: arraybo...@ubuntu.com
I can verify that this is still happening with a fully updated Debian Sid VM
running IceWM.
Myself and the Lubuntu Development team encountered this bug in Lubuntu, and it
was
Package: xscreensaver
Version: 6.02+dfsg1-2
Severity: important
I have been using xscreensaver for years. Recently (a few weeks or
months ago), it has stopped activating when the "Preview" button is
clicked and (rather more importantly) as per the delay specified via the
"Blank after" setting. It
11 matches
Mail list logo
