I can confirm above behaviour. Hardware switching off of bluetooth led to a successful resume at short notice but a return to GDM login screen if left for a while (in my case an hour). This was with UXA enabled. Bluetooth gave no errors in the pm-suspend.log. .. the bug is far from resolved.
I can confirm above behaviour. Hardware switching off of bluetooth led to a successful resume at short notice but a return to GDM login screen if left for a while (in my case an hour). This was with UXA enabled. Bluetooth gave no errors in the pm-suspend.log. .. the bug is far from resolved.