From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 209745] Bluetooth connection to Logitech MX Master 2S lost after each reboot
Date: Fri, 10 Jun 2022 16:37:05 +0000 [thread overview]
Message-ID: <bug-209745-62941-yfteIfFRoJ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209745-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=209745
Luiz Von Dentz (luiz.dentz@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |luiz.dentz@gmail.com
--- Comment #23 from Luiz Von Dentz (luiz.dentz@gmail.com) ---
(In reply to Massimo Burcheri from comment #22)
> Somehow I got it solved without removing IdentityResolvingKey with these
> settings in /etc/bluetooth/main.conf:
> AutoEnable=true
> Experimental = false
> I guess the Experimental flag is important. However after restarting the
> machine, the pointer device was just connected and working.
It seems the problem is LL Privacy (aka. Address Resolution), when that is
enabled certain controller seem to be unable to resolve addresses so the host
stack is unable to reconnect. I guess we should be splitting the kernel
experimental features from userspace experimental features, anyway Experimental
is never meant to be enabled by default so if anyone is shipping with it
enabled on main.conf please reconsider.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2022-06-10 16:37 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 12:00 [Bug 209745] New: Bluetooth connection to Logitech MX Master 2S lost after each reboot bugzilla-daemon
2020-10-19 13:44 ` [Bug 209745] " bugzilla-daemon
2020-10-19 15:18 ` bugzilla-daemon
2020-10-19 22:39 ` bugzilla-daemon
2020-10-27 8:38 ` bugzilla-daemon
2020-10-27 15:34 ` bugzilla-daemon
2020-10-27 15:38 ` bugzilla-daemon
2020-10-28 8:59 ` bugzilla-daemon
2020-10-28 12:55 ` bugzilla-daemon
2020-11-13 16:21 ` bugzilla-daemon
2020-11-15 2:55 ` bugzilla-daemon
2020-11-15 8:01 ` bugzilla-daemon
2020-11-19 20:08 ` bugzilla-daemon
2020-12-15 5:38 ` bugzilla-daemon
2020-12-16 3:09 ` bugzilla-daemon
2020-12-16 13:33 ` bugzilla-daemon
2020-12-16 14:42 ` bugzilla-daemon
2020-12-28 16:36 ` bugzilla-daemon
2020-12-30 13:21 ` bugzilla-daemon
2022-02-09 6:30 ` bugzilla-daemon
2022-06-07 14:35 ` bugzilla-daemon
2022-06-08 8:45 ` bugzilla-daemon
2022-06-08 9:46 ` [Bug,209745] " bluez.test.bot
2022-06-10 9:58 ` [Bug 209745] " bugzilla-daemon
2022-06-10 16:37 ` bugzilla-daemon [this message]
2022-06-13 8:36 ` bugzilla-daemon
2022-06-15 22:00 ` bugzilla-daemon
2022-06-21 7:28 ` bugzilla-daemon
2022-06-21 9:05 ` bugzilla-daemon
2022-06-21 9:09 ` bugzilla-daemon
2022-06-21 9:10 ` bugzilla-daemon
2022-06-21 10:08 ` bugzilla-daemon
2022-07-14 17:42 ` bugzilla-daemon
2022-10-13 12:28 ` bugzilla-daemon
2022-10-17 2:36 ` bugzilla-daemon
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=bug-209745-62941-yfteIfFRoJ@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-bluetooth@vger.kernel.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).