public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ian Zimmerman <itz@very.loosely.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: escape from i3lock
Date: Wed, 10 Jul 2019 15:45:01 -0700	[thread overview]
Message-ID: <20190710224501.5rmolpozbxspjh4a@matica.foolinux.mooo.com> (raw)
In-Reply-To: <20190710192250.GA30620@greenbeast>

On 2019-07-10 15:23, Alec Ten Harmsel wrote:

> On Wed, Jul 10, 2019 at 10:03:42AM -0700, Ian Zimmerman wrote:
> > Here is my next "low information" question, haha.
> > 
> > I use i3lock which is like Xscreensaver but much much simpler; it plays
> > no movies or games, just blanks the screen with a configured color or
> > image.  To unlock it you have to type your password.
> > It bothers me that even when i3lock has locked the X session, I can
> > still switch to other Linux virtual consoles with Alt-Control-F<n> ,
> > without typing the password.  It so happens that on one of the other
> > virtual consoles there is often an interactive root shell :-P
> > 
> > So, is it possible to prevent virtual console switching while the X
> > screen is locked, but still allow it at other times?  Looks like
> > something the locker program would have to do, not the X server; but
> > again I don't know much about this stuff.
> 
> Which init are you using, what display manager, and how are you
> launching it? I'm using systemd and sddm, and when I run `i3lock', I
> cannot switch to different virtual consoles.
> 
> Not sure whether any of that stuff matters, but that was the first thing
> I thought of.

It does matter.  Sysvinit, xdm via an initscript.  Not so long ago, no
DM at all, just startx/xinit.

This is probably a function of consolekit or some of the other awful
*kits.  Not installing one of those.  I'll find a workaround.

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet and on broken lists
which rewrite From, fetch the TXT record for no-use.mooo.com.


  parent reply	other threads:[~2019-07-10 22:45 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
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   ` Ian Zimmerman [this message]
2019-07-10 21:18 ` 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=20190710224501.5rmolpozbxspjh4a@matica.foolinux.mooo.com \
    --to=itz@very.loosely.org \
    --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