Well, thanks for doing all that digging. I assure you a simple Google search yielded nothing for me.
Kudos!
Well, thanks for doing all that digging. I assure you a simple Google search yielded nothing for me.
Kudos!
The layout of using gsettings seems much simpler & logical to me vs. gconf. Though over the last several months it has grown so much that the schemas list has gotten imposing, seen in
gsettings list-schemas
But the layout of using is quite straightforward
gsettings <command> <schemas> <key> <value>
Man gsettings is quite imformative to get some of the useful commands -
gsettings list-recursively <schemas> is very useful as is
gsettings get <schemas> <key> and
gsettings range <schemas> <key>
It all flows pretty nicely after a bit
This is correct so for those wanting to lock the screen without suspending this is not a viable option.
As a workaround, I'm sure an enterprising forumite could write a suspend script. It would 'sed' this command to 'true' when a 'suspend' script was activated and then 'sed' it back to 'false' after the system has returned from suspend. Or you could probably more easily incorporate a script to run when the "Lock Screen" option is run, since it wouldn't have to deal with resuming from suspend issues.
It shouldn't be necessary, but it could be done in this manner.
New to Wayland.
Retired.
In the ideal world, you would want the ability to keep those two things separate. Truthfully, it'd be rare to find someone so annoyed by having the screen locked upon resuming from suspend but who would want to lock the screen manually.
@ cRoMo,
Not that you or anyone else was anxiously waiting for this, but...This will also disable the possibility to manually lock the screen either by using the CTRL-ALT-L shortcut or through the Lock Screen option in "power menu".
Still searching for the solution to be able to only disable the post-resume screen lock.
- Blanking the screen is invoked with "gnome-screensaver-command -l"
- The command uses the dconf value set in the "disable lock screen" at the time of execution
- You can enable and use the Compiz Config Settings manager to set a key binding command to a script which will would temporarily change the lock value immediately before the command is invoked, and change it back immediately thereafter. I used CTRL-ALT-. (period)
- You will now have the lock on a manually blanked screen invoked by CTRL ALT . , but no lock for a suspended screen. (As aysiu stated, I'm not sure under what circumstances you might desire this action, but here it is.)
The script to bind:
With that, as Forrest Gump says, "That's all I have to say about that".#!/bin/bash
gsettings set org.gnome.desktop.lockdown disable-lock-screen 'false'
gnome-screensaver-command -l
gsettings set org.gnome.desktop.lockdown disable-lock-screen 'true'
exit
Or does, "Stupid is as stupid does" more likely apply to me?...
New to Wayland.
Retired.
Another satisfied customer. Thanks a lot.
Thanks a million! That was really annoying me.
And yes....I found it through a Google search! Viola!
I spent 90% of my money on women and drink. The rest I wasted.
Bookmarks