Kernel 6.12.5 - display brightness issue at resume

Ask Fedora
1

Hi.
I recently updated my FC41 running on a Lenovo X13 Gen 2 to kernel 6.12.5. Since, when it resumes from standby, while I am unlocking my session, the display brightness starts to increase until reaching maximum value, then the display switches off.
If I close the lid again, wait for it to suspend again, and open the lid again, it does the same.
After hard rebooting (pressing power button), no issue with brightness until suspend.

I rebooted on kernel 6.12.4, ran through 2 suspend/resume in a raw, no brightness issue.

With Kernel 6.11.3-200.fc40 unable to resume from suspend when bluetooth enabled, it accumulates…

6 Likes
3

I can confirm that running on a Lenovo V15 G3 ABA as well. Downgrading to 6.12.4 fixed that issue for me.

4

Also related to resuming from suspend or hibernate, and also only occurring after upgrading to kernel-6.12.5-200.fc41.x86_64, screen brightness locks to 100% after resuming and brightness controls are ignored until a reboot.

Huawei Matebook 13 AMD with Radeon Vega 8.

Downgrading to 6.12.4 restores normal functionality.

1 Like
5

I have the same issue on an HP255 G8. As others have mentioned, rolling back to a previous kernel version restores normal behaviour.

6

Same issue reported also here:
F41 - Kernel 6.12.5 weird issue (with a video showing the issue).
It seems at least 1 bug report exists now: 2333543 – Lenovo Ideapad 1 14ALC7 monitor flickers and dies after suspend with kernel 6.12.5.

1 Like
7

I also have the same issue. I just booted with 6.11.4 from the grub, thanks to Fedora’s reserving the previous kernel.

8

I can experience the brightness issue on 6.12.4-100.fc40.x86_64 as well.

9

Same problem here (Lenovo ThinkPad E16 Gen 1) since kernel 6.12.5-200.

10

there’s a correction for Bug 2333543 in 6.12.9-200 you might want to try

comment 33 on fix

That kernel is already in the Fedora updates-testing repo, I’m running it right now.

1 Like
11

Yes, since 6.12.9-200 has become stable, the issue is gone for now. Already running it on my laptop.