This is a problem with VLC or VLC's configuration, not xscreensaver:
https://www.jwz.org/xscreensaver/faq.html#dvd
--
Jamie Zawinski https://www.jwz.org/ https://www.dnalounge.com/
So, you know the X and Linux kernel devs have a policy of ensuring that you can
never actually secure your desktop, right?
https://www.jwz.org/xscreensaver/faq.html#no-ctl-alt-bs
I'm not going to change anything here. Xscreensaver is working as designed. The
problem being experienced is because the system it is running on is
misconfigured.
Specifically, xscreensaver is only halfway installed; and it is configured to
run modes that the half-install does not include.
creensaver sub-packages.
It would also work to make every entry in the .ad file be an absolute path
instead of relative.
But I don't like the idea of forcing entries in the .ad file that are not
absolute paths to only run from a hardcoded directory.
--
Jamie Zawinski https://www.jwz.org/
but with full (unmodified) PATH?
Sorry, I don't understand what you're proposing. Can you give some examples?
Why do you object to "just set $PATH in whatever script launched xscreensaver"?
That seems simple to me.
--
Jamie Zawinski https://www.jwz.org/ https://www.dnalounge.com/
> This bug does _NOT_ happen when "xscreensaver-data-extra"
> which provides /usr/lib/xscreensaver/zoom is also installed.
Hey guess what, this is a problem that only exhibits itself because you took
the code that I had tested and distributed, ripped half of it out, and expected
the other half
pen if HACKDIR is wrong or if the "zoom" saver is A) enabled but B) not
installed.
--
Jamie Zawinski https://www.jwz.org/ https://www.dnalounge.com/
Having xscreensaver override and ignore the $PATH that the user passed in is a
terrible idea.
But if init scripts are involved, perhaps those scripts should launch
xscreensaver without /usr/games/ on $PATH.
--
Jamie Zawinski https://www.jwz.org/ https://www.dnalounge.com/
oftware industry these days.
I guess you want Debian to be the kind of operation that uses the work of
others while blatantly and explicitly ignoring the wishes of the person who
*did the actual creative work*.
Nice.
--
Jamie Zawinski https://www.jwz.org/ https://www.dnalounge.com/
Please remove XScreenSaver from Debian.
Peter Nowee, please take your sanctimony and go fuck yourself with it.
For those of you who can't be bothered to read the code, here's what the
comment says.
I stand by my words here: If you are considering removing this warning, then I
ask that instead, you remove the XScreenSaver software from Debian entirely. I
believe Gnome-Screensaver will be more to your
and I wish to not have read it, but sadly
we don't always get what we want.
--
Jamie Zawinski https://www.jwz.org/ https://www.dnalounge.com/
as decided to sort ASCII text in some
insane way.
--
Jamie Zawinski https://www.jwz.org/ https://www.dnalounge.com/
But shell wildcards return sorted results. How does this change anything?
The proper fix to this is for there to be only *one* xscreeensaver package,
instead of having the savers be divided up into, what, six different packages
at random? I have no idea why anyone ever thought that was a good idea.
--
Jamie Zawinski http://www.jwz.org/ http
As you have already figured out, this is not a bug in xscreensaver.
You have something else grabbing the mouse.
If something else is grabbing the mouse it is IMPOSSIBLE to lock your screen.
There is no way xscreensaver can be altered to work around this bug in
some-other-program.
--
Jamie
workaround, of course, is to lock your screen before closing the lid.
--
Jamie Zawinski http://www.jwz.org/ http://www.dnalounge.com/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
xscreensaver does not use the MIT SCREEN-SAVER server extension because it is a
flaky, unreliable piece of shit that tends to cause the sever to crash.
which is ugly.
Does it work? Yes? Then it's not ugly.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject
Well, there's nothing in there that looks obvious to me, though all of those
screen change and screen resize event are suspicious. That may be
unrelated, though.
Is there anything in the logs complaining about DPMS?
From the log you sent, it appears that the X server is, all by itself,
(and Netscape, and XEmace, while I'm at it.)
Thanks, glad you like it!
--
Jamie Zawinski http://www.jwz.org/ http://www.dnalounge.com/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
. It halted the CPU with the screen not-yet-blanked,
from xscreensaver's perspective. Likewise, there is no way to fix this, because
Linux sucks.
--
Jamie Zawinski http://www.jwz.org/ http://www.dnalounge.com/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
I think you're being silly, but if you want to do that you can just set the
default for grabDesktopImages to false. No need to disable hacks.
If you do that you'd better make sure chooseRandomImages is true and
imageDirectory has a sensible default. configure.in line 3561.
--
To UNSUBSCRIBE,
It's all fair use, and you're a pinhead.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Not an xscreensaver bug. RTFAQ.
http://www.jwz.org/xscreensaver/faq.html#popup-windows
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RTFAQ.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Under what circumstances would xscreensaver be launched with no $PATH?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Feb 18, 2014, at 8:01 PM, Adrian Immanuel Kieß adr...@immanuelk.net wrote:
That's very clumsy and not the solution I would prefer.
We don't always get what we want.
See FAQ: http://www.jwz.org/xscreensaver/faq.html#which-one
--
To UNSUBSCRIBE, email to
Weird. Running with -log may be helpful...
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Dec 28, 2013, at 4:36 AM, Michal Suchanek hramr...@gmail.com wrote:
Is it resetting screensaver or frobbing dpms what causes the flicker?
I don't know.
And what drivers do cause it?
I don't remember.
Are they even in Debian?
I don't care.
It is a thing that happens, and therefore it a
the screen
black instead of powering off the monitor. If you're using an LCD and not a CRT
the difference in power consumption will probably be negligible anyway.
--
Jamie Zawinski http://www.jwz.org/ http://www.dnalounge.com/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ
It is true that using Xss requires a fork to get a sane semantics but
since xscreensaver-command is a short-lived process that should not be
a problem if the extension is used.
No, that's not how xscreensaver-command works.
I'm glad that your driver does not flicker. But others do. So like
On Dec 26, 2013, at 11:41 AM, Michal Suchanek hramr...@gmail.com wrote:
How I am supposed to disable the screensaver when the -deactivate
command is ineffective?
If what you are trying to say is, xscreensaver-command -deactivate doesn't
work, you're wrong, and this is easy to demonstrate by
If you have a *tested* patch, please send it.
I don't have any systems that exhibit the kind of broken behavior you describe,
and can't test it myself. This is very security-sensitive code so I am hesitant
to make any changes at all without them being very obviously correct.
It's also
This has been fixed for more than a year, 5 releases ago.
I can't help you if you people refuse to ever upgrade.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Jamie Zawinski wrote:
That's a completely reasonable place to put it.
No, it's annoying and it violates the FHS. Dot-files have to be created
in ~/ , not in ~/somewhere/ .
You're welcome to your opinion, but my opinion differs, so I'm not going to
change it.
--
To UNSUBSCRIBE, email
Use kill.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
That's on purpose. Without that, deactivating the saver via mouse motion would
never do a fade-in at all.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Your line numbers don't match up with reality, and also what you're saying
doesn't make sense to me, which makes me think you're talking about some
ancient version of sonar.
Oh wait, Debian. Yeah, you guys are the ones who insist on shipping
many-years-obsolete versions of my software and
That's a completely reasonable place to put it.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Actually xscreensaver-text already does something very similar with LWP.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Jan 12, 2013, at 9:26 PM, Trek tre...@inbox.ru wrote:
That was my first guess, but xscreensaver-text (in the version included by
Debian)
I have no idea what ancient version Debian has seen fit to include, but if your
distro is giving you a version of xscreensaver-text that's more than
I don't think there's any rhyme or reason as to which savers various distros
have chosen to put in data versus data-extra. In my opinion there should
only be three packages: the driver, the X11 savers, and the GL savers.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
You don't have to do anything.
You're making your own personal decision to go against the design of the author
of the software.
Don't act like you've got some boss telling you this, and that it's out of your
hands. You chose it.
--
To UNSUBSCRIBE, email to
.
--
Jamie Zawinski http://www.jwz.org/ http://www.dnalounge.com/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
more.
This is of course a non-problem on MacOS, where non-privileged datagram sockets
actually work. Maybe you could get that fixed in the kernel instead. (Ha ha,
only serious.)
--
Jamie Zawinski http://www.jwz.org/ http://www.dnalounge.com/
--
To UNSUBSCRIBE, email to debian-bugs
There is no way to make anything work sensibly for typical users without
overwriting the whole file. The morass of places that one can set X resources,
some of which haven't been commonly used for decades but that still work, makes
this problem intractable. The X configuration mechanism is
Looks reasonable, thanks!
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On May 17, 2012, at 6:17 PM, Renato Andrade Galvão wrote:
The problem is that my X session is restarted when xscreensaver switch to
'Gleidoscope' option. This doesn't happen with the others options.
Your X server is crashing. Not an xscreensaver bug.
--
Jamie Zawinski http://www.jwz.org
This is a large-ish patch to a sensitive piece of code and I honestly can't
tell what it's trying to do. So without a better explanation (and hopefully
better commented code) I'm not going to apply this upstream.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
As the entire function of the xscreensaver-demo program is to edit your
.xscreensaver file...
Yes. Yes, it does.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Mar 6, 2012, at 4:36 PM, Andrew Shadura wrote:
Also, it'd be good to have ability to edit time-related options with
the same precision as they're specified in the configuration file.
Believe it or not, it used to do that, but the Gnome UI team decided people
should not be allowed to edit
On Mar 6, 2012, at 4:41 PM, Andrew Shadura wrote:
What do you mean when you say 'hard'? Just don't change settings user
hasn't changed, what's so hard in this?
You can prove me wrong by sending me a patch.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
Sorry, I think this is only going to confuse people. Applications should not
have UI elements that just magically get ignored if some forgotten text-only
preference is set.
I'm not going to install this patch upstream.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
I'm not asking to use both xset and a GUI; I'm asking to to use only
xset, and have the GUI leave DPMS well alone. At present, there's a
./configure option to do so, but no run-time equivalent.
I understand what you're asking for. You want this, but more people want the
opposite. Sorry, but
Intended behavior. Won't fix.
It's impossible to allow use of both xset and a GUI and know which setting
should take priority, since changes to settings don't have timestamps on them.
Therefore, xscreensaver has to be 100% in charge of these settings for it to
work at all.
--
To
It's documented in the man page... If you think it's unclear send me a change.
I guess you could just regenerate the programs section of the app-defaults file
from the existing XML files if you wanted. Then postinst could run the
rebuild script you've added to the xscreensaver package.
I
Now, as a maintainer, how I am supposed to add a hack to the list?
Surely not editing a conffile from other package in postinst, as that
is not permitted by the Debian Policy. Is there any other way to do
this?
Policy aside, that is how you do it. I don't see another way.
If
On Nov 8, 2011, at 11:34 AM, yellow wrote:
I would like that xscreensaver allow the xf86 keys even while -locked
Unfortunately X11 makes that kind of thing impossible:
http://www.jwz.org/xscreensaver/faq.html#change-hacks-key
http://www.jwz.org/xscreensaver/faq.html#no-ctl-alt-bs
--
To
It will be good if Xscreensaver will show current layout at password prompt
window.
I'm not going to do that. It would clutter up the window, and it's probably
hard to even know what layout is in use in any sensible, portable way.
It also be good to show Capslock indicator for same reason.
I would like to lock with boing from xscreensaver-command
That's what -select N does. You have to know the number, though.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Ok, so it sounds like 14 should be the max in the GUI?
On my machine, a 2.93 gHz iMac i7, I get these rates with -fps -delay 0:
detail 3: invisible
detail 4: barely visible
detail 5: 1000+ fps, looks like noise at -delay 0, ok at -delay 2
detail 8: ~700+ fps
detail 9:
On Sep 5, 2011, at 4:07 PM, Josselin Mouette wrote:
Package: xscreensaver
Version: 5.14-1
Severity: normal
The “USING GNOME” and “USING KDE” sections of the xscreensaver manual
page contain, among offensive and inappropriate text, instructions that
will, with recent versions, fail to
I suspect your stack trace is nonsense since that looks like it's crashing
inside of forkpty.
Or, possibly /dev/pty* has gotten screwed up on your box.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Driver bug, not xscreensaver.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
apple2, xanalogtv and phosphor can all do this. See the man pages.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Sure, that sounds reasonable. I'll change it to power down the monitor when
blanking and mode is Blank Only. (I think it makes the most sense to do this
at blank and not lock.)
--
Jamie Zawinski http://www.jwz.org/ http://www.dnalounge.com/
--
To UNSUBSCRIBE, email to debian
I really was running that screenhack called biof.
I've never heard of this, what is it?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Dec 20, 2010, at 5:30 AM, Juhapekka Tolvanen wrote:
I really don't know, if any of those problematic OpenGL-screenhacks
belong to XScreenSaver-distribution.
Regardless of where they come from, the symptoms you describe are absolutely
not a bug in those screen savers. The bug is in your
I don't think it's a good idea is not a justification for this change, which
would cripple that screen saver.
If you have an actual reason that it is a problem in the real world in any way,
please present it.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject
Sorry, I thought you were suggesting that it should not be installed setuid by
default.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I didn't realize that sonar was not installed setuid by default.
That's a mistake and I believe that should be corrected.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
savers out with the bathwater...
--
Jamie Zawinski j...@jwz.org http://www.jwz.org/
j...@dnalounge.com http://www.dnalounge.com/
http://jwz.livejournal.com/
--
To UNSUBSCRIBE, email to debian-bugs-dist
Package: xscreensaver
Version: 5.05-3
In summary:
The Debian package of xscreensaver currently excludes many savers from the
default install, on the basis of them using too much CPU. This is no longer
the case. As those savers no longer use too much CPU, the justification for
excluding
On Sep 2, 2010, at 9:22 AM, Yves Lambert wrote:
It looks like when xscreensaver child dies, xscreensaver does not
launch another child and the keyboard is locked, only magic keys still
works, no way to switch to another VT.
This statement makes no sense to me at all.
--
To UNSUBSCRIBE,
That's a new one... Yes, -sync will probably help, as will a core file stack
trace. I suspect we will discover that some sub-process launched by your PAM
stack is crashing and taking libpam with it. That line about an unknown process
dying means that we got a SIGCHLD for a pid that
This looks good, thanks! But I think you do need to go around the loop
multiple times, because there's technically no guarantee that the response
event we're polling for in XCheckIfEvent will be the first event to come in.
There might be some event we don't care about that causes select() to
I can't imagine why you would want the unlock dialog to appear on a screen that
does not have the mouse on it. You have to move the mouse over there to click
OK anyway.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
X server crashes are not xscreensaver bugs. Report it against X.
http://www.jwz.org/xscreensaver/faq.html#server-crash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I've been down this path before, and the only sensible solution here is to
rename this screensaver called unicode to have a non-conflicting name.
Unicode is not a part of the xscreensaver distribution.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
I believe this was fixed in xscreensaver 5.06 in July 2008.
The problem was a single character typo in yarandom.c: it said 024 (octal)
where it should have said 24 (decimal), causing the two lags to not be
co-prime.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
If run as 'xjack -font fixed', xjack runs normally and the crash does
not occur.
What font is it trying to use? Is there something goofy about the fonts on
your system? Try this:
xlsfonts -fn -*-*-medium-r-*-*-*-240-*-*-m-*-*-*
xlsfonts -fn -*-courier-medium-r-*-*-*-180-*-*-m-*-*-*
xlsfonts
It tries each of those patterns in order until it gets one, and if it doesn't,
it bails. See xjack.c line 88.
So probably it's actually using
alee-guseul-medium-r-normal--33-240-100-100-m-0-iso10646-1
I assume there's something stupid about that font that makes it blow up. No
idea what,
The configuration dialog only shows screenhacks that are either hardcoded
inside the xscreensaver binary, or manually entered into ~/.xscreensaver.
This means there is no easy way to make packages that provide additional
screenhacks.
No, that's what the /usr/lib/X11/app-defaults/XScreenSaver
If the problem here is that you launched xscreensaver-demo while
gnome-screensaver was running but xscreensaver was not, then you should have
gotten a dialog box saying exactly that, and offering to shut down
gnome-screensaver, instead of simply saying that xscreensaver was not running.
See
Apparently the Debian maintainers feel that your inconvenience is a small price
to pay to protect the functionally retarded from themselves.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I don't have the slightest idea what that means.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Nov 29, 2009, at 11:05 PM, Yves-Alexis Perez wrote:
And I beg to differ.
Well, you're welcome to your opinion. You might conceivably be of the opinion
that any number of other features should be removed from xscreensaver, like
locking, and you're welcome to those opinions as well. It's
Your only proposal that would actually *work* is adding an option to disable an
important feature of xscreensaver. I explained why the right fix is adding
battery-awareness to xscreensaver, rather than ham-handedly kludging in an
option to turn off power management entirely.
I'm in no hurry.
Just because adding the kludgy option you keep asking for might not be hard
does not mean it's the right fix.
Having been maintaining this software for 18 years, I am more interested in
having xscreensaver be consistent and non-kludgy than in fixing your problem
*today*. Waiting for the
You cannot use xset if you are also using xscreensaver. RTFM:
http://www.jwz.org/xscreensaver/man1.html#7
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
My point is, I *dont* want xscreensaver to manage them. afair, it was
working before, power management is disabled in xscreensaver, which
means it shouldn't mess it.
We can't always get what we want.
It's impossible to allow use of both xset and a GUI and know which setting
should take
Like it or not, xscreensaver is an app that manages power settings based on
parameters in the .xscreensaver file, and xscreensaver-demo is a GUI for
editing that file.
Your complaint is that xscreensaver and various other programs that *also* try
to manage power settings step on each others'
Unfixable using X11. http://www.jwz.org/xscreensaver/faq.html#mouse-idle
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Nov 10, 2009, at 3:50 PM, Yitzchak Gale wrote:
We offer the xscreensaver as a substitute, for those who do not like
gnome-screensaver for some reason.
No, that's not why we offer it. xscreensaver daemon is not
designed to run in a desktop environment. It is not a substitute
for
hypercube is polytopes -wireframe -8-cell -perspective-3d -
perspective-4d.
hyperball is polytopes -wireframe -120-cell -perspective-3d -
orthographic-4d.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
But there is no README.hacking in the /usr/share/doc/xscreensaver
directory.
It is included in the source distribution.
There is no reason to distribute this file in a context where the
source code is not also included. It is not runtime documentation.
--
To UNSUBSCRIBE, email to
note that i am using the ati-proprietary fglrx driver for gl support
right now, which may very well be the problem.
Without question.
thanks for looking into this.
There' s nothing to look in to, unfortunately. My only advice is that
you find a driver that works, or get a different video
Surely there is no sensible reason for Debian and Ubuntu to have
different lists of which hacks go in which packages. I think you are
falling into the age-old trap of adding customizability as a cop-out
to avoid the harder, but more sensible, work of just finding consensus.
--
To
I think Debian and Ubuntu have different goals and style and for sure
different release cycles. So maybe one particular 3D hack can be
whitelisted in one release and held back in another.
That's nonsense. Either the hack in a particular release of
xscreensaver works properly, or it doesn't.
The recent behavior change in xscreensaver was in the case where it
could not grab the mouse or keyboard or both.
The old behavior was that it would lock anyway, possibly resulting in
a screen that could not be unlocked.
The new behavior is that if it can't get both grabs, it does not lock
101 - 200 of 344 matches
Mail list logo
