Bug 2153647 - Keyboard/Gnome Brightness Controls Non-Functioning on Lenovo Legion 5 (2020) Laptop
Summary: Keyboard/Gnome Brightness Controls Non-Functioning on Lenovo Legion 5 (2020) ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-settings-daemon
Version: 37
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kalev Lember
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-15 02:49 UTC by 02coopbloop
Modified: 2024-04-05 04:25 UTC (History)
12 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2023-12-06 11:43:55 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description 02coopbloop 2022-12-15 02:49:15 UTC
Description of problem:
Multiple users of the Lenovo Legion 5 (2020) laptop (15arh05h) have noticed brightness controls being completely broken for the built-in display. The laptop supports hybrid and discrete graphics mode, and in either case, moving the brightness slider with designated keys or in software to not cause the built-in display to dim/brighten.

Attempted Fixes:
Adding "acpi_osi=linux acpi_backlight=vendor" to the GRUB kernel parameters
- Brightness control doesn't change with or without these.

Version-Release number of selected component (if applicable):
Fedora 37 (Workstation)
GNOME 43.2
Wayland windowing system

How reproducible:
Works 100% of the time for mine and another Legion 5 user's machines.

Steps to Reproduce:
1. Run/install Fedora 37 on a Lenovo Legion 5 (2020) laptop
2. Install proprietary NVIDIA drivers and reboot
3. Attempt to use gnome software brightness controls or brightness keys

Actual results:
Display backlight is locked to maximum brightness.

Expected results:
Built-in display should change illumination level in accordance with the brightness slider when it is moved.

Additional info:

Comment 1 DeMus 2023-07-08 19:35:11 UTC
I can confirm this. I also own a Lenovo Legion5 Pro laptop and brightness control doesn't work for me as well.I use the KDE spin, btw. 
I tried both in X11 and in Wayland, this doesn't make a difference: the notification slider in the center of the screen moves from 0 to 100% when using the mouse-wheel over the battery symbol in the panel, or by using the function keys on the built in keyboard, but brightness does not change.
I have just tried KDE Neon in a live version on a USB drive and there it works, also when using openSUSE I have no problems with that.
It is just in Fedora that things work differently.

Version-Release number of selected component (if applicable):
Fedora 38 (KDE spin)
KDE Plasma 5.27.6
Kernel 6.3.11-200.fc38.x86_64
Wayland and X11 windowing system

How reproducible:
Works 100% of the time for my Legion 5 user's machines.

Steps to Reproduce:
1. Run/install Fedora 38 on a Lenovo Legion 5 (2023) laptop
2. Install proprietary NVIDIA drivers and reboot
2a Using the AMD GPU gives the same result
3. Attempt to use KDE software brightness controls or brightness keys

Actual results:
Display backlight is locked to maximum brightness.

Expected results:
Built-in display should change illumination level in accordance with the brightness slider when it is moved.

Comment 2 Niels De Graef 2023-09-19 16:24:37 UTC
This isn't really something the wayland protocol handles, so moving this to gnome-settings-daemon for now as a next good candidate. For KDE users, they might want to file a bug for the appropriate KDE component.

In any case, would you mind trying to see if this still reproduces on Fedora 38? And the Fedora 39 Beta?

If it doesn't work on the Fedora 39 beta, one thing that would be good to check is whether the new "Keyboard backlight" quick toggle does actually change the value or not.

If that also doesn't do the track, it would be good to get some logs when this is happening

Comment 3 Aoife Moloney 2023-11-23 00:46:20 UTC
This message is a reminder that Fedora Linux 37 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '37'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 37 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 Persona non grata 2023-11-23 06:41:20 UTC
Hi, I am now on Fedora 39 KDE and, just as on Fedora 38 KDE, it works. After installation of the OS it doesn't work, but after some reboots it suddenly works and I can't say why. It just works.
Now when I move my mouse over the battery symbol and I use my scroll wheel the brightness can be controlled very well.

Comment 5 Aoife Moloney 2023-12-06 11:43:55 UTC
Fedora Linux 37 entered end-of-life (EOL) status on None.

Fedora Linux 37 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 6 Red Hat Bugzilla 2024-04-05 04:25:08 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


Note You need to log in before you can comment on or make changes to this bug.