On 01/02/17 18:05, Patrick O'Callaghan wrote: > I've mentioned in the past my troubles getting consistent behaviour > from Bluetooth, especially after resuming from suspend or hibernate. It > randomly works or doesn't, depending on the phase of the moon. > > This morning it came up with a new wrinkle. After resuming from > hibernate, the BT task bar icon is absent, the BT widget says it's > Offline, but the BT mouse is working. First time I've seen this. > > Seriously? > > (I don't expect an answer, I'm really just logging this for future > reference). Well, you may not expect an answer but here we go.... First off, there is an online marketplace here in Taiwan called PChome24. They guarantee delivery on orders within 24hrs, in the metro Taipei area, and at times have 24hr sales. It just so happened they had a 24hr sale (20% off, free shipping) on a LogiTech BT Mouse, so I bought one. I've been wanting to ditch my wired mouse anyway as the scroll wheel had been getting a bit jumpy. I can pretty much confirm your observations. The system I have isn't configured such that I can hibernate but I can suspend to RAM. On resuming from suspend the mouse sometimes comes back and sometimes not. When it hasn't resumed properly I see the blue LED on the mouse flashing from time to time attempting a connection. So, I left the pointer within a konsole so that I could enter some commands. I also configured the "systray" to always show the BT icon. When the system resumes but the mouse isn't working the BT icon is dim. I tried various "rfkill" commands to no avail. I then used bluetoothctl and did a "power off" followed by a "power on" and the BT icon switched to fully on. After a little bit the mouse would reconnect. I found that, I could make the try to reconnect quicker if I moved it. I guess it senses movement, finds it isn't connected and tries to reconnect as opposed to a periodic check. So, I wrote a simple script.... #!/bin/sh bluetoothctl <<EOF power off EOF sleep 5 bluetoothctl <<EOF power on EOF to cycle the power. I found the sleep was needed, maybe it could be shorter, as if I tried the power command too quickly it didn't work. Again, since I left my cursor within a konsole I could call the script. The next thing to do, of course, is to make a keyboard shortcut to call the script. Which I leave up to you to try? :-) This "workaround" works for me. Not a true "fix" but at least I don't need to grab a wired mouse at anytime. -- You're Welcome Zachary Quinto _______________________________________________ kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx
