Description of problem: Since upgrading to 34, my laptop screen remains off when waking from suspend. Lifting the laptop lid won't activate the screen automatically but a mouse movement or keyboard press will as expected. In 33, the screen would wake up upon waking from suspend and you'd be presented with the lock screen as a normal behaviour - Fedora 34 - Acer Swift 3, Ryzen 4700U - linux-firmware-20210315-119.fc34.noarch - kernel-5.11.12-300.fc34.x86_64 Please let me know how I can better help you
⁺¹, reproducible as well. I would also add that I infrequently have seen similar behavior on Fedora 33. Never reported though due to lack of steps to reproduce, but now it is reproducible most of the time.
Dustin, I presume though the `component` should be `mutter`?
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. 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 '34'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 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.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.