From: Tore Anderson <tore@fud.no>
To: Johan Hedberg <johan.hedberg@gmail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
Gustavo Padovan <gustavo@padovan.org>,
linux-bluetooth@vger.kernel.org
Subject: PROBLEM: Bluetooth mouse not working after resume since commit 2ff1389
Date: Sat, 20 Feb 2016 18:12:59 +0100 [thread overview]
Message-ID: <20160220181259.1e28f8da@envy.w5.y.home> (raw)
Starting with commit 2ff1389, =C2=ABPerform HCI update for power on
synchronously=C2=BB, my Logitech M555b bluetooth mouse no longer works after
resuming the system from suspend. The devices is handled by Blueman, and
after resuming from suspend the white lines/triangles inside the
systray icon doesn't turn green even though I move the mouse around.
(The lines turning green normally indicates that a device is active.)
In order to revive it, I need to manually disable and then re-enable
bluetooth, at which point it will re-connects fine.
I've also noticed that I need to press Blueman's =C2=ABTurn Bluetooth Off=
=C2=BB
menu selection twice for it to take effect (so that Blueman's systray
icon gets overlayed with a little red X symbol). This only happens once
after each resume from suspend - after having been through one
off-off-on cycle, bluetooth will turn off normally on the first attempt
(until the next suspend/resume cycle). It also turns off normally on
the first attempt after the initial boot-up. This "double-off after
resume" behaviour also first occurred with commit 2ff1389.
Let me know if there's any other information I can provide.
Tore
next reply other threads:[~2016-02-20 17:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 17:12 Tore Anderson [this message]
2016-02-20 18:23 ` PROBLEM: Bluetooth mouse not working after resume since commit 2ff1389 Johan Hedberg
2016-02-20 18:29 ` Johan Hedberg
2016-02-20 20:30 ` Tore Anderson
2016-02-21 7:02 ` Johan Hedberg
2016-02-21 11:13 ` Tore Anderson
2016-03-03 7:51 ` Tore Anderson
2016-03-03 8:42 ` Johan Hedberg
2016-03-03 20:44 ` Tore Anderson
2016-03-04 6:54 ` Johan Hedberg
2016-03-05 9:09 ` Tore Anderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160220181259.1e28f8da@envy.w5.y.home \
--to=tore@fud.no \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).