Yet more information on this particular issue.I let the xscreensaver run overnight and it appears that after some time, whatever amount of time that is, the system still falls back to the lightdm greeter for logging in. However, after logging in again I now get the xscreensaver unlock input window, so it appears that even though it now falls back to the lightdm login it doesn't kill the xscreensaver. Previously the mate-screensaver unlock was evidently bypassed when the lightdm greeter was enabled.
The question is still 'where is the auto logoff taking place and where is the config for that"?
Next question is 'with no screensavers enabled, how long will it take for the system to automatically log me out to the lightdm greeter'?
tony On 06/30/2017 11:31 AM, tony mollica wrote:
Concerning this issue, I removed the mate-screensaver and installed xscreensaver and while it certainly doesn't have as polished an appearance as the mate version, it works. It does the same thing, locks the screen and does not drop back to the lightdm greeter logon and doesn't suspend in-progress apps, namely, my 3D printing apps. I'll try and contact the author or package management folks to see if anything can be re-configged in mate-screensaver to eliminate the original problem. Tony On 06/30/2017 08:35 AM, tony mollica wrote:This bug report sounds familiar but I find no evidence of anything that appears to be related to this in any of the logs. The only screensaver loaded is the mate-screensaver. If I disable the screensaver via the idle time and lock options and then lock the screen manually, it stays at the mate-screensaver lock normally and never falls back to the lightdm logon screen. Even so, it's odd that if the screensaver idle time and lock options are chosen, and the screen is locked after the timeout, or locked manually then the screensaver activates like it should but after a time it falls back to the lightdm greeter screen. BUT, the programs that were running at the time are not killed but just appear to be suspended so when the logon takes place the programs start processing again. I would think that if the system drops back to the lightdm greeter that it would kill all the processes for the user but that doesn't happen. I can't find the documentation for the mate-screensaver configuration anywhere. tony On 06/29/2017 12:27 PM, tomas@tuxteam.de wrote:-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, Jun 29, 2017 at 08:43:26AM -0700, tony mollica wrote:Hello, yet again, and dropping the html. Here's the problem. I use this computer, previously v8, now v9, for 3D printing. The old system worked perfectly in that the screensaver did it's job BUT kept me logged in forever. The new system doesn't do this. The screensaver set off and after some period of time I get logged off automatically. The BIG problem is that when this happens printing stops but the extruder and build plate stay at operating temperature, which is good to restart but not good if I'm not there to catch it. Basically, if I can't prevent the auto logout this system is useless for 3D printing. How do I do it, disable the auto logoff? Searched a lot yesterday but none of that appears to be in effect here.Difficult to say. Your desktop environment is Gnome? After such a forced logout, can you spot anything in the X server log (typically in your home directory, somewhere in .local/share/xorg, unless you have an uncommon setup, and then you would know ;-) Perhaps in /var/log/daemon.log? Here is an old bug where a crashing screensaver would force an X server restart: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=569933 Any similarities? Does it happen when you disable the lock screen feature in the screen saver? When you disable the screen saver altogether? Hope there's a useful hint in there. Cheers - -- tomás -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAllVVLwACgkQBcgs9XrR2kaUfACfUOwtEq5UOEug1JuJ4fydFz6v disAni9622kcKbcX6NCCCU6DxWD7tMhE =ApJD -----END PGP SIGNATURE-----