Bug 1200565

Summary: Backlight on KDE 5.25 is not adjustable
Product: [openSUSE] openSUSE Tumbleweed Reporter: Arlind Asip Murtezi <asadowski17>
Component: OtherAssignee: E-mail List <screening-team-bugs>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: brutus8890, dev.dorrejo, marcin.bajor
Version: Current   
Target Milestone: ---   
Hardware: 64bit   
OS: openSUSE Tumbleweed   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Arlind Asip Murtezi 2022-06-15 11:29:19 UTC
My system information:

Operating System: openSUSE Tumbleweed 20220613
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.2
Kernel Version: 5.18.2-1-default (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-1035G1 CPU @ 1.00GHz
Memory: 7.5 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics
Manufacturer: MEDION
Product Name: E15407
System Version: NONE

I want to adjust my brightness via the GUI on KDE, but it seems not to work well.

When I want to change it to 100% it automatically dims my brightness.

I only can set it up with a script for manually adjustment.

That's my script:
echo "96000" | sudo tee /sys/class/backlight/intel_backlight/brightness
Comment 1 Marcin Bajor 2022-06-15 12:43:28 UTC
(In reply to Arlind Asip Murtezi from comment #0)
> My system information:
> 
My system info:
Operating System: openSUSE Tumbleweed 20220613
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.2
Kernel Version: 5.18.2-1-default (64-bit)
Graphics Platform: X11
Processors: 12 × Intel® Core™ i7-8750H CPU @ 2.20GHz
Memory: 31.2 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1060/PCIe/SSE2
Manufacturer: Dell Inc.
Product Name: G3 3779


I observe the same issue.
During system startup, the screen dims. I am unable to change the brightness in Plasma KDE.

Screen dims during startup
systemd-backlight@backlight:intel_backlight.service


Systemd-analyze shows:
$systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @10.016s
└─display-manager.service @9.304s +711ms
  └─systemd-user-sessions.service @9.282s +16ms
    └─remote-fs.target @9.278s
      └─iscsi.service @9.239s +37ms
        └─network-online.target @9.203s
          └─NetworkManager-wait-online.service @2.252s +6.949s
            └─NetworkManager.service @2.139s +71ms
              └─network-pre.target @2.108s
                └─wpa_supplicant.service @3.251s +90ms
                  └─dbus.service @1.317s +80ms
                    └─basic.target @1.305s
                      └─sockets.target @1.304s
                        └─pcscd.socket @1.304s
                          └─sysinit.target @1.298s
                            └─systemd-backlight@backlight:intel_backlight.service @4.626s +392ms
                              └─system-systemd\x2dbacklight.slice @2.151s
                                └─system.slice
                                  └─-.slice

and dmesg shows a lot of messages like:
[   88.782590] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.PEG0.PEGP.BRT6.LCD], AE_NOT_FOUND (20211217/psargs-330)
[   88.782604] ACPI Error: Aborting method \_SB.PCI0.PEG0.PEGP.BRT6 due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
[   88.782675] ACPI Error: Aborting method \EV5 due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
[   88.782743] ACPI Error: Aborting method \SMEE due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
[   88.782814] ACPI Error: Aborting method \SMIE due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
[   88.782876] ACPI Error: Aborting method \NEVT due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
[   88.782920] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
[   89.387280] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.PEG0.PEGP.BRT6.LCD], AE_NOT_FOUND (20211217/psargs-330)
[   89.387294] ACPI Error: Aborting method \_SB.PCI0.PEG0.PEGP.BRT6 due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
[   89.387366] ACPI Error: Aborting method \EV5 due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
[   89.387440] ACPI Error: Aborting method \SMEE due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
[   89.387515] ACPI Error: Aborting method \SMIE due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
[   89.387590] ACPI Error: Aborting method \NEVT due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
[   89.387665] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_NOT_FOUND) (20211217/psparse-529)
[   89.626489] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.PEG0.PEGP.BRT6.LCD], AE_NOT_FOUND (20211217/psargs-330)
[   89.626502] ACPI Error: Aborting method \_SB.PCI0.PEG0.PEGP.BRT6 due to previous error (AE_NOT_FOUND) (20211217/psparse-529)

I'm able to change the brightness by:
echo 120000>>/sys/class/backlight/intel_backlight/brightness

but not in Plasma.
Comment 2 Marcin Bajor 2022-06-15 14:57:37 UTC
This is known upstream issue
https://bugs.kde.org/show_bug.cgi?id=454161
https://bugs.kde.org/show_bug.cgi?id=455308
https://bugs.kde.org/show_bug.cgi?id=455307

Workaround that works for me. Snapper required:
* Rollback with snapper to previous version of Plasma
* Lock powerdevil5 with zypper
sudo zypper addlock powerdevil5
* Update rest of the system

The workaround is to keep powerdevil5 in version 5.24
Comment 3 Marcin Bajor 2022-06-15 17:25:28 UTC
*** Bug 1200543 has been marked as a duplicate of this bug. ***
Comment 4 Marcin Bajor 2022-06-15 17:34:58 UTC
I meant The workaround is to keep powerdevil5 in version 5.24.5
Comment 5 Marcin Bajor 2022-06-16 15:10:47 UTC
Next workaround:
Install patched version from:
https://build.opensuse.org/package/show/home:lemmy04:branches:KDE:Frameworks5/powerdevil5
Comment 6 Brutus 2022-06-17 13:36:14 UTC
About the workaround, if I follow the link and click "Download package" I get the following error:

No data for home:lemmy04:branches:KDE:Frameworks5 / powerdevil5
Comment 7 Marcin Bajor 2022-06-17 13:50:06 UTC
(In reply to Brutus from comment #6)
> About the workaround, if I follow the link and click "Download package" I
> get the following error:
> 
> No data for home:lemmy04:branches:KDE:Frameworks5 / powerdevil5
On the right in the Build Result section click your distro, you will be redirected to the latest builds. Then you can download the rpm package.

Patched version has already been created and is awaiting approval.
https://build.opensuse.org/request/show/983420
Comment 8 Marcin Bajor 2022-06-19 20:38:44 UTC
Package powerdevil5 5.25.0-2.1 that contains the patch has been published. Update your OS.