You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since i found that is still possible to click on the Lock button, and that leads to a strange behavior and mostly confusing for newbies, why not use: gsettings set org.gnome.desktop.lockdown disable-lock-screen true
for all distributions that use Gnome ?
Will read more how the linux-scripts are structured, so i can understand better if this is possible to implement.
The text was updated successfully, but these errors were encountered:
If the above was noticed on Fedora, this screenshot is taken from OpenSuse Leap. The button puts the system into sleep/hibernate something, and makes the shell to not respond at all, unless powered off from console and then powered up again. Might be confusing for newbies and should be handled better.
Would be safer to have it power off the system instead. I tried to use this gsettings set org.gnome.settings-daemon.plugins.power power-button-action 'nothing'
but apparently is not working, so maybe the script needs:
Continuation2 - Manjaro @Chrysostomus - maybe for the next manjaro shell we can disable the log out and lock dialog like this
The reason i'm proposing this is that, if i lock or log out then log back in, i simply notice that the shell chokes and becomes unresponsive. Restarting the shell after that is not helping as will lead to a blinking cursor on the screen, and the only solution is to stop the shell from shells console and then power it on again.
Quite possible that some clients did the lock > log out routine and they been facing a very slow shell.
Since i found that is still possible to click on the Lock button, and that leads to a strange behavior and mostly confusing for newbies, why not use:
gsettings set org.gnome.desktop.lockdown disable-lock-screen true
for all distributions that use Gnome ?
Will read more how the linux-scripts are structured, so i can understand better if this is possible to implement.
The text was updated successfully, but these errors were encountered: