openSUSE logout/sleep issue

[DanielOaks]

On openSUSE KDE/Plasma, you can click the 'sleep' button in the start menu. It breaks the GUI in a bad way that means you need to adjust your browser size (it ends up looking like you've zoomed into a 15x15px square somewhere on the screen, until you change screen size a few times). I haven't been able to find a way to disable that button - 'sleep' doesn't turn up anything in https://develop.kde.org/deploy/kiosk/keys/
Maybe there's something useful in the Plasma documentation?

On openSUSE Gnome, pressing the logout button takes you to a login screen that you can't get back from unless you reboot the machine.

[DimStar77]

for the openSUSE GNOME Part:
#69

=> logout should actually have been disabled

[DimStar77]

@Vogtinator any idea about the KDE related part of this bug?

[Vogtinator]

There's indeed no Plasma-specific setting for sleep. What I suggest instead (and also deals with GNOME, other DEs and the CLI) is to disable all kinds of sleeping through sleep.conf (see man 5 systemd-sleep.conf).

Plasma picks that up and as a result hides all relevant buttons.

[DanielOaks]

We rebuilt some images yesterday.

Newest GNOME image no longer shows the logout button, but does show just the Suspend button in its place. Pressing it locks the machine up. If I run sudo systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target and reboot the machine, the button disappears from OpenSUSE GNOME Tumbleweed, but doesn't disappear from GNOME Leap. However, then the button on Leap no longer locks the machine up entirely (just takes them to a login prompt which they need to reboot to get back into the machine from), which is still an improvement over silently locking up.

Tested doing the same systemctl mask call on a built KDE/Plasma Tumbleweed image and it hid the sleep button as well, so maybe we could just add that to the desktop build scripts?

[Vogtinator]

Why not use sleep.conf, which is the intended way to configure this?

[DanielOaks]

I don't have any preference, that command's just what worked for me while testing. If they both end up doing the same thing, doing it via sleep.conf would be great!