My programs were also still in place but they stopped processing until I
logged back in via the light-locker screen. After that, the processing
re-started (evidenced by the printer continuing merrily on it's way) and
then I continued to log into the full desktop through the
mate-screensaver lock. From the stuff I read the intent of the
light-locker was security based so as not to allow switching into
another terminal for whatever reason if you had physical access to the
machine. I have no idea how that's done, or maybe we're not configuring
it correctly. Like I indicated earlier, the source appears to have a
facility for a light-locker.conf file but I found none on my system and
I can't read the code well enough to figure out what parameters can be
used, much less what they do.
tony
On 07/02/2017 06:01 PM, Mike Kupfer wrote:
<to...@tuxteam.de> wrote:
On Sat, Jul 01, 2017 at 10:20:13AM -0700, Mike Kupfer wrote:
This doesn't sound to me like you're being logged out. Rather it sounds
like light-locker is locking your screen, which is does by bringing up a
new lightdm instance.
But what happens then to the current X session?
When I experimented with this some time back, the current X session
appeared to be unaffected. I could go to lunch, and when I came back,
all my outbound ssh sessions were still in place.
A new lightdm instance
would bring with it a new session?
I'm afraid I don't know the answer to that.
mike