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 enough for the wake.
I noticed also that I can't stop bluetoothd: $ ps aux | grep bluetoothd root 8305 0.0 0.0 36520 4388 ? Ss 11:35 0:00 /usr/lib/bluetooth/bluetoothd -d bbogart 8598 0.0 0.0 22000 1040 pts/2 R+ 11:40 0:00 grep --color=auto bluetoothd $ sudo service bluetooth stop $ ps aux | grep bluetoothd root 8662 2.5 0.0 36520 4324 ? Ss 11:41 0:00 /usr/lib/bluetooth/bluetoothd -d bbogart 8670 0.0 0.0 22000 1088 pts/2 S+ 11:41 0:00 grep --color=auto bluetoothd Why would bluetoothd restart after I've explicitly told it to stop? Now, if I put the stop and start service script in /lib/systemd/system- sleep/, then the NUC does not wake up after hours. The problem persists when: Mouse is switched off (before entering suspend) Mouse is changed to USB (not BT) mode Bluetooth is turned "off" (via blueman applet) Removing bluez may also solve the problem, I'm testing that now. -- 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 (8I3BEH1) wakes up immediately after suspend if Bluetooth is still enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1823076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
