3 ms·
My experience is quite the contrary which makes me wonder, does it really behave so differently among systems?!? touchpad and bluetooth pairing (a2dp) are not w
by paines 8y ago
My experience is quite the contrary which makes me wonder, does it really behave so differently among systems?!? touchpad and bluetooth pairing (a2dp) are not working after suspend+resume. Notice: touchpad can be fixed with a script in /lib/sysetmd/system-sleep. Home encryption gone?!?! Why for fucks sake?!? This was one of the USPs for me to use it over Debian. Yeah it can be done manually, but for beginners this is a drawback...
- halkotron 8y agoYeah, BT after resume was f'ed for me too. Solved it by: - upgrading bluez to 5.49: https://launchpad.net/~bluetooth/+archive/ubuntu/bluez https://launchpad.net/~bluetooth/+archive/ubuntu/bluez - hacking a script that toggles rfkill (un)block <hci0 dev id> on resume BT applet, at least on Unity (yes, I'm one of those people) seems to be borked in that it can't enable BT after resume. I'm guessing it's because it remembers the wrong BT device ID (which gets incremented after every sleep/resume, at least on my system).