Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

For Gnome desktops Lock Screen proper disable/hide from System Menu. #75

Open
bogdancovaciu opened this issue Jul 27, 2021 · 2 comments

Comments

@bogdancovaciu
Copy link

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.

@bogdancovaciu
Copy link
Author

Continuation:

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.

image

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:

[org/gnome/settings-daemon/plugins/power]
power-button-action='noting'

to be set it in /etc/dconf/db/gdm.d/05-power - will investigate more.

@bogdancovaciu
Copy link
Author

Continuation2 - Manjaro
@Chrysostomus - maybe for the next manjaro shell we can disable the log out and lock dialog like this

image

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant