Feature request: Put the computer back to sleep from the lock screen after waking it up (KDE Plasma)

What I sometimes do is wake up the computer to check the time, or accidentally wake it up with the mouse moving. In these occassions, it would be handy to put the computer back to sleep from the lock screen, instead of having to enter the password to log in and then put it to sleep.

Computer info:

 21:18:13  jr@fm  ~  ⬡ v8.16.0 
$ inxi -Fxxx
System:    Host: fm Kernel: 5.6.16-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.1.0 Desktop: KDE Plasma 5.19.80 tk: Qt 5.15.0 
           wm: kwin_x11 dm: SDDM Distro: Manjaro Linux 
Machine:   Type: Desktop Mobo: ASUSTeK model: TUF B450M-PLUS GAMING v: Rev X.0x serial: <root required> 
           UEFI: American Megatrends v: 1002 date: 03/07/2019 
CPU:       Topology: 8-Core model: AMD Ryzen 7 2700X bits: 64 type: MT MCP arch: Zen+ rev: 2 L2 cache: 4096 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 118223 
           Speed: 3401 MHz min/max: 2200/3700 MHz boost: enabled Core speeds (MHz): 1: 2567 2: 1927 3: 4311 4: 2151 5: 2195 
           6: 2196 7: 2191 8: 2190 9: 4328 10: 2006 11: 2195 12: 2199 13: 2199 14: 2197 15: 2239 16: 2053 
Graphics:  Device-1: NVIDIA TU104 [GeForce RTX 2080] vendor: ASUSTeK driver: nvidia v: 440.82 bus ID: 07:00.0 
           chip ID: 10de:1e82 
           Display: x11 server: X.Org 1.20.8 driver: nvidia compositor: kwin_x11 resolution: 1920x1080~60Hz 
           OpenGL: renderer: GeForce RTX 2080/PCIe/SSE2 v: 4.6.0 NVIDIA 440.82 direct render: Yes 
Audio:     Device-1: NVIDIA TU104 HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 07:00.1 chip ID: 10de:10f8 
           Device-2: Advanced Micro Devices [AMD] Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 09:00.3 chip ID: 1022:1457 
           Sound Server: ALSA v: k5.6.16-1-MANJARO 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK driver: r8168 v: 8.048.03-NAPI 
           port: f000 bus ID: 05:00.0 chip ID: 10ec:8168 
           IF: enp5s0 state: up speed: 100 Mbps duplex: half mac: 40:b0:76:5c:8c:4c 
           IF-ID-1: docker0 state: down mac: 02:42:66:2d:17:4b 
Drives:    Local Storage: total: 465.76 GiB used: 201.21 GiB (43.2%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 500GB size: 465.76 GiB speed: 31.6 Gb/s lanes: 4 
           serial: S4EVNG0M116780W rev: 1B2QEXM7 scheme: GPT 
Partition: ID-1: / size: 389.04 GiB used: 201.21 GiB (51.7%) fs: ext4 dev: /dev/nvme0n1p2 
           ID-2: swap-1 size: 69.20 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p3 
Sensors:   System Temperatures: cpu: 41.9 C mobo: N/A gpu: nvidia temp: 30 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 20% 
Info:      Processes: 368 Uptime: 13h 52m Memory: 62.81 GiB used: 18.43 GiB (29.3%) Init: systemd v: 245 Compilers: 
           gcc: 10.1.0 Shell: zsh v: 5.8 running in: konsole inxi: 3.0.37 

Welcome to the forum! :beer:

What you are asking about is a feature request for the upstream KDE Plasma developers. There is very little that the Manjaro developers can do about that.

You can however file a feature request or bug report with the KDE folks at this link. :slight_smile:

1 Like

Close the lid of Laptop. It’s that easy. No need of disturbing the devs :smiley:
EDIT: Sorry I failed to notice you have desktop :astonished:

@Aragorn, thanks, reported here: 425617 – Feature request: Put the computer back to sleep from the lock screen after waking it up (KDE Plasma).

I can also turn the monitors off at the power point, and/or use a keyboard shortcut to turn the monitor off. However, it saves power to put it to sleep—although it may not be much—I haven’t measured. Turning it off saves more, and also turns off all the lights of the system, which can be distracting with meditating or sleeping in a dark room.

1 Like

Well, for a laptop, I can understand the thought process, but the truth of the matter is that the power you save is easily lost again by powering up the system the next time.

A boot process ─ and especially a cold boot, whereby the entire system must be (re-)initialized ─ sends a lot of spikes through the circuitry at the same time, which increases wear. Conversely, a system that’s always on and maintaining a constant temperature will consume less energy and experiences less wear. :slight_smile: