On Tue, 2017-01-03 at 17:55 +0800, Ed Greshko wrote:
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.
> (I don't expect an answer, I'm really just logging this for future
Well, you may not expect an answer but here we go....
Again, since I left my cursor within a konsole I could call the
The next thing to do, of course, is to make a keyboard shortcut to call the script.
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.
Actually my spare mouse is wireless (it came with my wireless
keyboard). I know for a fact that it's really BT as well, but it
manages to hide itself as a USB device and is thus 100% reliable.
I have done similar things to your script, but using hciconfig. I even
tried adding an action to /usr/lib/systemd/system-sleep/ so it would
activate automatically on resume:
$ cat /usr/lib/systemd/system-sleep/enablebt
# Enable Bluetooth mouse on resuming from suspend/hibernate
# Lives in /usr/lib/systemd/system-sleep
# See systemd-hibernate.service(8)
case $1 in
post) hciconfig $MOUSEDEV up ;;
but again it's not reliable. I haven't tried adding the delay so that
might be something to look at.
Thanks for the feedback.
BTW, I noticed this morning that when the system resumes with BT
working, but KDE thinks it isn't, you can't click on the BT enable tick
box in the widget. Definitely some wires crossed there.