KDE energy saving dim stuck on

justmere · 29 July 2023 13:30

Last night my energy saving dim in KDE activated, and I shut down my computer through a command shutdown now on KDE Connect on my phone. When i booted my computer this morning, dim was still active. I've gone into KDE settings and deactivated "dim screen" and played with the brightness slider which does nothing. This level of brightness is fine if i'm up past midnight like an insomniac, but during the day i won't be able to read my screen.

Anyone ever experienced this? How was it fixed?

System:
Kernel: 6.4.7-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.1.1
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=f6cccf9c-8580-435e-8f33-927e3e31bb2d rw rootflags=subvol=@
rd.driver.pre=vfio-pci amd_iommu=on quiet rd.udev.log_priority=3
vt.global_cursor_default=0
resume=UUID=2e9cba84-8fd3-4884-995e-6ac1c54716ad loglevel=3
vfio-pci.ids=10de:17c8,10de:0fb0 nvidia-drm.modeset=1 ibt=off
Desktop: KDE Plasma v: 5.27.6 tk: Qt v: 5.15.10 wm: kwin_x11 vt: 2
dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop System: Gigabyte product: X570 AORUS ELITE v: -CF
serial: <superuser required>
Mobo: Gigabyte model: X570 AORUS ELITE v: x.x serial: <superuser required>
UEFI: American Megatrends LLC. v: F34 date: 06/10/2021
Battery:
ID-1: hidpp_battery_0 charge: 89% condition: N/A volts: 4.1 min: N/A
model: Logitech G502 LIGHTSPEED Wireless Gaming Mouse type: N/A
serial: <filter> status: discharging
CPU:
Info: model: AMD Ryzen 9 3950X bits: 64 type: MT MCP arch: Zen 2 gen: 3
level: v3 note: check built: 2020-22 process: TSMC n7 (7nm)
family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701021
Topology: cpus: 1x cores: 16 tpc: 2 threads: 32 smt: enabled cache:
L1: 1024 KiB desc: d-16x32 KiB; i-16x32 KiB L2: 8 MiB desc: 16x512 KiB
L3: 64 MiB desc: 4x16 MiB
Speed (MHz): avg: 4147 high: 4265 min/max: 2200/4761 boost: enabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 4210 2: 4175
3: 4018 4: 4242 5: 4242 6: 4242 7: 4241 8: 4239 9: 4243 10: 4241 11: 4249
12: 4241 13: 4124 14: 4241 15: 4242 16: 4242 17: 4044 18: 4243 19: 4244
20: 3500 21: 4210 22: 4147 23: 4239 24: 4265 25: 3500 26: 4241 27: 3500
28: 4227 29: 4241 30: 4239 31: 4237 32: 4223 bogomips: 223570
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA GM200 [GeForce GTX 980 Ti] vendor: Micro-Star MSI
driver: vfio-pci v: N/A alternate: nouveau,nvidia_drm,nvidia
non-free: 535.xx+ status: current (as of 2023-07) arch: Maxwell
code: GMxxx process: TSMC 28nm built: 2014-19 pcie: gen: 3 speed: 8 GT/s
lanes: 4 link-max: lanes: 16 bus-ID: 05:00.0 chip-ID: 10de:17c8
class-ID: 0300
Device-2: NVIDIA TU104 [GeForce RTX 2070 SUPER] vendor: Micro-Star MSI
driver: nvidia v: 535.86.05 alternate: nouveau,nvidia_drm non-free: 535.xx+
status: current (as of 2023-07) arch: Turing code: TUxxx
process: TSMC 12nm FF built: 2018-22 pcie: gen: 3 speed: 8 GT/s lanes: 16
ports: active: none off: DP-1,DP-2 empty: DP-3,HDMI-A-1 bus-ID: 0b:00.0
chip-ID: 10de:1e84 class-ID: 0300
Device-3: Logitech C922 Pro Stream Webcam driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-3.1.3:9
chip-ID: 046d:085c class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.2
compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nvidia,nvidia-nvswitch
display-ID: :0 screens: 1
Screen-1: 0 s-res: 5119x1440 s-dpi: 96 s-size: 1354x381mm (53.31x15.00")
s-diag: 1407mm (55.38")
Monitor-1: DP-1 mapped: DP-0 note: disabled pos: left model: Dell S2716DG
serial: <filter> built: 2016 res: 2560x1440 dpi: 109 gamma: 1.2
size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes:
max: 2560x1440 min: 640x480
Monitor-2: DP-2 note: disabled pos: primary,right model: VG27A
serial: <filter> built: 2020 res: 2560x1440 dpi: 109 gamma: 1.2
size: 597x336mm (23.5x13.23") diag: 685mm (27") ratio: 16:9 modes:
max: 2560x1440 min: 640x480
API: OpenGL v: 4.6.0 NVIDIA 535.86.05 renderer: NVIDIA GeForce RTX 2070
SUPER/PCIe/SSE2 direct-render: Yes
Audio:
Device-1: NVIDIA GM200 High Definition Audio vendor: Micro-Star MSI
driver: vfio-pci alternate: snd_hda_intel pcie: speed: Unknown lanes: 63
link-max: gen: 6 speed: 64 GT/s bus-ID: 05:00.1 chip-ID: 10de:0fb0
class-ID: 0403
Device-2: NVIDIA TU104 HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 0b:00.1 chip-ID: 10de:10f8 class-ID: 0403
Device-3: AMD Starship/Matisse HD Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0d:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-4: Logitech C922 Pro Stream Webcam driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-3.1.3:9
chip-ID: 046d:085c class-ID: 0102 serial: <filter>
Device-5: Texas Instruments ATH-G1WL
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 1-3.1.4:10 chip-ID: 0451:16ba class-ID: 0300
serial: <filter>
Device-6: Focusrite-Novation Scarlett 2i2 3rd Gen driver: snd-usb-audio
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 7-1:2
chip-ID: 1235:8210 class-ID: 0102 serial: <filter>
API: ALSA v: k6.4.7-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: PipeWire v: 0.3.76 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel I211 Gigabit Network vendor: Gigabyte driver: igb v: kernel
pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 06:00.0
chip-ID: 8086:1539 class-ID: 0200
IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Intel 82575EB Gigabit Network driver: igb v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 link-max: lanes: 4 port: c020 bus-ID: 07:00.0
chip-ID: 8086:10a7 class-ID: 0200
IF: enp7s0f0 state: down mac: <filter>
Device-3: Intel 82575EB Gigabit Network driver: igb v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 link-max: lanes: 4 port: c000 bus-ID: 07:00.1
chip-ID: 8086:10a7 class-ID: 0200
IF: enp7s0f1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
Device-1: TP-Link UB500 Adapter driver: btusb v: 0.8 type: USB rev: 1.1
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 7-2:3 chip-ID: 2357:0604
class-ID: e001 serial: <filter>
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
Local Storage: total: 4.57 TiB used: 1.14 TiB (25.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:2 vendor: SanDisk model: ADATA SX6000PNP
size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: V9002s85 temp: 39.9 C
scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Western Digital
model: WDS100T1XHE-00AFY0 size: 931.51 GiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 614600WD temp: 30.9 C scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 4B6Q scheme: GPT
ID-4: /dev/sdb maj-min: 8:16 vendor: Western Digital
model: WD20EARX-00ZUDB0 size: 1.82 TiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 5400 serial: <filter>
fw-rev: 0A80 scheme: GPT
Partition:
ID-1: / raw-size: 896.73 GiB size: 896.73 GiB (100.00%)
used: 672.48 GiB (75.0%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 576 KiB (0.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 896.73 GiB size: 896.73 GiB (100.00%)
used: 672.48 GiB (75.0%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 896.73 GiB size: 896.73 GiB (100.00%)
used: 672.48 GiB (75.0%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-5: /var/tmp raw-size: 896.73 GiB size: 896.73 GiB (100.00%)
used: 672.48 GiB (75.0%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 31.28 GiB used: 934 MiB (2.9%) priority: 100
dev: /dev/zram0
ID-2: swap-2 type: partition size: 34.49 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/sda3 maj-min: 8:3
Sensors:
System Temperatures: cpu: 56.6 C mobo: 34.0 C gpu: nvidia temp: 50 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 24%
Info:
Processes: 576 Uptime: 27m wakeups: 6 Memory: total: 32 GiB
available: 31.28 GiB used: 12.98 GiB (41.5%) Init: systemd v: 253
default: graphical tool: systemctl Compilers: gcc: 13.1.1 alt: 11/12
clang: 15.0.7 Packages: pm: pacman pkgs: 2665 libs: 595
tools: octopi,pamac,paru Shell: fish v: 3.6.1 default: Bash v: 5.1.16
running-in: konsole inxi: 3.3.28
Garuda (2.6.16-1):
System install date:     2022-01-22
Last full system update: 2023-07-29
Is partially upgraded:   No
Relevant software:       snapper NetworkManager mkinitcpio nvidia-dkms
Windows dual boot:       Probably (Run as root to verify)
Failed units:            systemd-networkd-wait-online.service

RodneyCK · 29 July 2023 17:25

I have posted elsewhere I think there is an issue/bug with KDE + 2 monitors + dim/brightness. I had to deselect the 'Dim' option in Energy settings because it was driving me crazy.

On my laptop which I don't use a second monitor, it works perfectly.

justmere · 29 July 2023 22:08

Fixed it by:

crank brightness to 100% hit apply (did nothing)
turn dim screen on, set it to 1 minute, hit apply, and walk away to do something else
move the mouse

Bingo.

system · 31 July 2023 22:09

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.

RodneyCK · 1 August 2023 20:43

The original topic was closed, but not solved.

Did as instructed in the original post, and it does work if you are away from your computer for a few minutes. However, I went away for like 20 minutes and it was dimmed, but also stuck in dim mode. I had to open up a brightness app and manually get it back to full brightness. I still think there is a bug.

SGS · 14 August 2023 06:01

This topic was automatically opened after 12 days.

system · 28 August 2023 06:01

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.