https://bugs.kde.org/show_bug.cgi?id=344967
--- Comment #17 from David Edmundson <k...@davidedmundson.co.uk> --- Lets say you did set it to 8 hours, you wouldn't get prompted during the day, but you'd still have to lock the screen when you left because otherwise it's unlocked for 8 hours. It hasn't saved you from actually having to perform the manual action. If you do forget you're scarcely in a better state than having autolock completely off with regards to security except in very contrived scenarios. Maybe I'm missing something, but it sounds like you have a problem isn't in the timeout but in a lack of inhibitors - and we're just working round the problem. I think many of the other options would be better suited to actually solving it: - you can wrap your scripts in a screensaver inhibitor; like a media player would - You can run kdeconnect on both PCs and set up "inhibit screensaver when connected" on the script machine so it's synced to your main machine. And there's other stuff we can explore. Maybe we need a clearer inhibitor applet UI (the battery applet does contain this, but it's not too clear on a desktop). -- You are receiving this mail because: You are watching all bug changes.
