Classic Linux/open-source issue… Live with it or use Windows…
Further more, simplest solution just choose the old kernel in grub.
Hi, can confirm it happening in a ROG Zephyrus G14 GA401II and both 6.12.5 and 6.12.6 
No issues when going back to 6.12.4.
There’s another thread here on this bug. My guess is that it won’t be long before this is fixed.
In the meantime, just set your power mode to “Performance”, and you’ll be good to go until it is.
Well, there are a bunch of intermediate options between silently accepting issues or giving up and migrating to windows.
Particularly improving the rollback of changes that introduce regressions, the ease of tracking issues for users, and also more automation when a fix is packaged.
Rebooting to previous kernel is possible. However, if you have to wait for a while for a fix to be packaged, as kernels are being bumped “ASAP” / “blindly”, you may have to use dnf versionlock add on multiple packages, and then forget about it. Being able to lock a package version until the status of a bug is fixed and updated packages are available would be a great feature for a distro.
That’s not really a solution because when the laptop hits 20% the Power Save mode activates and the issues instantly strikes you and you need to hard reboot in the middle of your work…
https://bodhi.fedoraproject.org/updates/FEDORA-2024-0b5b0e0527
sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-0b5b0e0527
6.12.7 is in updates-testing, it would be good for folks with issues to provide feedback.
Thanks.
1 Like
After the screen flickered and switched off, instead of hard-rebooting, I just plugged the power back, and the screen switched on. This is a better workaround for me. However, I choosed to reboot on kernel 6.12.4 to simply avoid the issue.
1 Like
Except that (1) you can temporarily turn off the option for “Automatic Power Save” mode under the Settings Power menu, and (2) this bug does not trigger the need for a hard reboot, since it’s just a screen blank and not a system freeze; there is a way to recover from this without rebooting.
I think what I’m suggesting is a temporary workaround, not a solution.
The tone in this thread seems to me like a “Rome is burning!” when, really, “Someone just lit a match somewhere in Rome.”
1 Like
You can also suspend the system by closing the lid, then opening it to resume and immediately choosing the “Performance” power mode from the menu in the upper right hand side of your screen.
The effect we’re all seeing is not a system freeze. It’s a screen blank.
For me it’s not “just a screen blank.” I can’t do anything when the screen goes black… whatever I press it won’t come back… so I have to hard reboot, unfortunately. Also, the issue can occur on screen lock, so I don’t have time to unlock the system and immediately choose the Performance mode over Power Save because the screen goes blank too fast…
Since f41 replaced power-profiles-daemon with the tuned-ppd service, it could be those packages having a issue with 6.12.5 and later.
I’ll test here in a bit.
It’s possible to manipulate the menu with the screen locked, at least I’ve done it with my system. I’m a little surprised to learn that you cannot.
1 Like
Oh, my bad… I completely forgot that I can access the quick settings menu from the lock screen. Thanks for that!
I confirm the issue is fixed after installing latest updates from Discovery.
What updates? From testing?
A no go with 6.12.5-6.12.6; testing kernel 6.12.7 fixed the issue in my machine.
Thanks
This kernel didn’t fix the issue for me.
I did the install using your suggest command line, then turned on “Power Saver” power mode via the Quick Menu and rebooted.
I started a handful of processes and suspended manually and, afterwards, closing the lid on my laptop. Once I returned from suspend, I encountered identical behavior to that of 6.12.5 and 6.12.6: Blinking to a screen off mode.
This is for a Lenovo Yoga 6 laptop with CPU/iGPU, AMD Ryzen 5 PRO 4650U/AMD Radeon Vega Series.
My bad, I forgot to set the default boot to the new test kernel 6.12.7, was still booting to 6.12.4 that has no issues. Test kernel 6.12.7 still has the same problem.
Sorry.
1 Like
I experienced this issue in the kernel 6.12.6, I just booted with 6.11.4 instead