public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Laurence Perkins <lperkins@openeye.net>
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Re: escape from i3lock
Date: Fri, 12 Jul 2019 01:17:45 +0000	[thread overview]
Message-ID: <61326d4f3fecf8ba2efcdb662cdc83e8713b37dd.camel@openeye.net> (raw)
In-Reply-To: <20190712001135.g7ziilwhkxoo7slx@grusum.endjinn.de>

[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]


> So the solution is to just use "xscreensaver" by jwz. Which can be
> configured to just blank the screen etc. as wanted by the op. See
> also
> the FAQ: https://www.jwz.org/xscreensaver/faq.html
> 
> HTH,
> -dnh
> 

Except I use xscreensaver myself and it in no way prevents VT switch,
which is what the OP was hoping to find a way to do if and only if the
screen is locked.  Programs that grab input still don't get to block
combos that are processed by the X server before they even get to the
program's input queue any more than grabbing input will block the alt-
sysrq kernel-level interrupt keys.

Disabling VT switch by the X server and then setting up some other way
to trigger a switch that will be blocked by whatever screen locking
program the OP wishes to use is the best solution I can think of.  chvt
would be the program to call.  Whether he wants it to be a keyboard
shortcut handled by his DE or some other trigger method is a matter of
taste.

LMP

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2019-07-12  1:17 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-10 17:03 [gentoo-user] escape from i3lock Ian Zimmerman
2019-07-10 18:44 ` François-Xavier CARTON
2019-07-10 22:48   ` [gentoo-user] " Ian Zimmerman
2019-07-10 23:21     ` artur.tamm.85
2019-07-10 23:46     ` artur.tamm.85
2019-07-11 16:57       ` Ian Zimmerman
2019-07-11 20:47         ` Ian Zimmerman
2019-07-11 21:01           ` artur.tamm.85
2019-07-11 21:10             ` Laurence Perkins
2019-07-12  0:11               ` David Haller
2019-07-12  1:17                 ` Laurence Perkins [this message]
2019-07-12  8:48                   ` Michele Alzetta
2019-07-11  0:43     ` Adam Carter
2019-07-11 16:49       ` Ian Zimmerman
2019-07-11 20:28   ` Nuno Silva
2019-07-12 16:01     ` Ian Zimmerman
2019-07-12 16:05       ` Michele Alzetta
2019-07-12 16:09       ` Laurence Perkins
2019-07-13 19:11       ` Nuno Silva
2019-07-10 19:23 ` [gentoo-user] " Alec Ten Harmsel
2019-07-10 20:52   ` Neil Bothwick
2019-07-10 21:00     ` Alec Ten Harmsel
2019-07-10 22:45   ` [gentoo-user] " Ian Zimmerman
2019-07-10 21:18 ` [gentoo-user] " Francesco Turco

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=61326d4f3fecf8ba2efcdb662cdc83e8713b37dd.camel@openeye.net \
    --to=lperkins@openeye.net \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox