Like I mentioned, the kernel drivers seem fine. It appears to be a userspace software regression, either in bluez or in the gnome components that call bluez. the adaptor seems dead after resuming from sleep, until the gnome bluetooth settings panel is opened. this must call some sort of refresh function, and then everything works fine again. whatever this function is, it must've been called after resume previously in 20.04, and isn't being called now in 20.10, hence the regression.
i don't know anything about bluez or the gnome internals, but i'm happy to provide whatever logs would be helpful in identifying the root cause and getting it fixed, since it's making my current desktop usage a nightmare.
Like I mentioned, the kernel drivers seem fine. It appears to be a userspace software regression, either in bluez or in the gnome components that call bluez. the adaptor seems dead after resuming from sleep, until the gnome bluetooth settings panel is opened. this must call some sort of refresh function, and then everything works fine again. whatever this function is, it must've been called after resume previously in 20.04, and isn't being called now in 20.10, hence the regression.
i don't know anything about bluez or the gnome internals, but i'm happy to provide whatever logs would be helpful in identifying the root cause and getting it fixed, since it's making my current desktop usage a nightmare.