If I remove the bluez package there are no issues with suspend.
** Changed in: bluez (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823076
Title:
Intel NUC
So after some more investigation it's clear that the problem is
inconsistent. Sometimes wake immediately follows suspend, sometimes not.
Sometimes it takes a while to wake up, up to a few minutes, other times
it's immediate. Occasionally, it seems to suspend fine; or maybe I'm not
waiting long enou
Scratch that; the first couple suspend operations did work, and then
they stopped again. I'll do more testing and report back. I did rule out
mouse movement by using the hardware power switch on the mouse.
** Changed in: bluez (Ubuntu)
Status: Invalid => Incomplete
--
You received this bu
I believe this issue was due to "legacy suspend" rather than "modern
suspend" selected in UEFI. After a couple suspends I am no longer seeing
the problem, but will reopen if it happens again.
** Changed in: bluez (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification
Also, are you able to change any settings in your BIOS to prevent wakeup
from Bluetooth?
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18
It sounds like you've found a good workaround but I am curious about the
root cause here.
It seems the Bluetooth mouse might be emitting events even when you
don't touch it..? Are you able to try a different model of Bluetooth
mouse?
** Summary changed:
- Intel NUC (8I3BEH1) wakes up immediately