SUMMARY The KDE Plasma Energy Saving System Setting for "Screen Energy Saving" is set to "Switch off after 6 minutes". * Provided that, the Screen isn't locked, this works as expected. But, if the Screen is locked, the Screen doesn't switch off -- ever … STEPS TO REPRODUCE 1. Lock the session - <Alt-L> 2. Wait for more than 6 minutes. 3. Wait until the end of time … OBSERVED RESULT The Screen isn't switched off. * Even the energy saving built into X11 doesn't kick in … EXPECTED RESULT The Screen switches off. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.71.0 Qt Version: 5.12.7 ADDITIONAL INFORMATION The kscreenlocker version is the one which was delivered with Plasma version 5.18.5. The severity is set to major because, we should all be careful with respect to energy saving -- it's important for this planet …
System information - new Hardware - complete re-install was needed due to UEFI (which the previous system didn't have … ): System: Kernel: 5.3.18-lp152.33-default x86_64 bits: 64 compiler: gcc v: 7.5.0 parameters: BOOT_IMAGE=/boot/vmlinuz-5.3.18-lp152.33-default root=UUID=c59a64bf-b464-4ea2-bf3a-d3fd9dded03f splash=silent resume=/dev/disk/by-id/ata-Intenso_SSD_Sata_III_AA000000000000035990-part3 mitigations=auto quiet elevator=cfq Console: tty 4 wm: kwin_x11 dm: SDDM Distro: openSUSE Leap 15.2 Machine: Type: Desktop Mobo: ASUSTeK model: PRIME B450-PLUS v: Rev X.0x serial: <filter> UEFI: American Megatrends v: 2008 date: 12/06/2019 CPU: Topology: Quad Core model: AMD Ryzen 5 3400G with Radeon Vega Graphics bits: 64 type: MT MCP arch: Zen+ family: 17 (23) model-id: 18 (24) stepping: 1 microcode: 8108109 L1 cache: 384 KiB L2 cache: 2048 KiB L3 cache: 4096 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 65602 Speed: 1260 MHz min/max: 1400/4100 MHz boost: enabled Core speeds (MHz): 1: 1258 2: 1258 3: 1258 4: 1260 5: 1260 6: 1260 7: 1260 8: 1259 Vulnerabilities: Type: itlb_multihit status: Not affected Type: l1tf status: Not affected Type: mds status: Not affected Type: meltdown status: Not affected Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Picasso vendor: ASUSTeK driver: amdgpu v: kernel bus ID: 08:00.0 chip ID: 1002:15d8 Display: server: X.Org 1.20.3 compositor: kwin_x11 driver: amdgpu display ID: :0 screens: 1 Screen-1: 0 s-res: 3840x2160 s-dpi: 96 s-size: 1016x571mm (40.0x22.5") s-diag: 1165mm (45.9") Monitor-1: HDMI-A-0 res: 3840x2160 hz: 60 dpi: 140 size: 698x393mm (27.5x15.5") diag: 801mm (31.5") OpenGL: renderer: AMD RAVEN (DRM 3.33.0 5.3.18-lp152.33-default LLVM 9.0.1) v: 4.5 Mesa 19.3.4 direct render: Yes Info: Processes: 309 Uptime: 6h 19m Memory: 13.59 GiB used: 2.18 GiB (16.0%) Init: systemd v: 234 runlevel: 5 target: graphical.target Compilers: gcc: N/A Shell: bash (su) v: 4.4.23 running in: konsole inxi: 3.1.00
As of 2021-02-03, having setup the Audio to use both the Analogue and HDMI outputs in parallel and, changed the Monitor settings to no longer automatically choose which Input - HDMI-1, HDMI-2, Display Port - shall be used - it's now set to use the HDMI-1 input only - * The issue has disappeared . . . ---------------------------------------------------------------------- Whether or not, a recent or, not so recent, patch played a role in the behaviour change, is something I can not prove . . . ---------------------------------------------------------------------- I'm closing this Bug Report.