Just gave my laptop a good scrub, some rebases to other Ublue-based images, a fresh install, rebase to signed Bluefin latest, and now the one frustrating thing is back: instantaneous wakeups from suspends.
I first experienced this about a month ago, when I put Bluefin on my laptop for the very first time. At that time the only fix was going back to Fedora Workstation and one echo XHC > /proc/acpi/wakeup. I basically dug around the net for some time, figured out that XHC was waking my laptop immediately after suspend kicks in. Checked using cat /proc/acpi/wakeup | grep enabled. The earlier echo XHC command basically disables it from requesting wakeups. After that, no more baffling wakeups until I wiped Workstation off my machine.
The second time I installed Bluefin, the weird behavior didn’t return. I made sure to not plug my wireless USB receiver (Logitech M185), as it seems to be the root of this evil, during the clean ISO install. Lovely few weeks. But now… it’s back. echo XHC > /proc/acpi/wakeup does work… until I shut down or reboot my computer. Then I’ll have to remember to fire the same command again. I sure can start a systemd unit to fire it after booting, but it’s really not ideal.
FWIW, this seems to have been documented in Arch BBS: here and another here, also on Arch Wiki, but personally I’ve never ever experienced this problem outside of Bluefin - not in Arch-, Debian-, or Fedora-based. Not even in Silverblue. Are there Bluefin-specific configurations that might have caused this behaviour? And again, this did not happen last time - I had a good few weeks run without this behaviour.
As I’m writing this I’m backing up stuff and downloading latest ISO. Thinking of installing again without the USB receiver plugged to my laptop. Maybe I really can’t have it plugged during Bluefin install or rebase to Bluefin.
Any help or suggestion will be appreciated. Will also report back after the reinstall.