From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 203643] New: [REGRESSION][BISECTED] Sixaxis gamepad no longer connects via Bluetooth
Date: Sat, 18 May 2019 17:35:57 +0000 [thread overview]
Message-ID: <bug-203643-62941@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=203643
Bug ID: 203643
Summary: [REGRESSION][BISECTED] Sixaxis gamepad no longer
connects via Bluetooth
Product: Drivers
Version: 2.5
Kernel Version: 4.14.119, 4.19.42, 5.0.16, 5.1.3
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: spaz16@wp.pl
Regression: No
Hi,
Since commit d5bb334a8e171b262e48f378bd2096c0ea458265 some devices doesn't
connect via bluetooth (like Sixaxis gamepad). 'bluetoothctl' shows that device
is connected, and soon after disconnected.
Link for commit which causes the issue:
https://github.com/torvalds/linux/commit/d5bb334a8e171b262e48f378bd2096c0ea458265
I checked the "conn->enc_key_size", it reports the value of 0 for Sixaxis
gamepad (not the value of 7, which is the minimum encryption key size).
I noticed that other people also having issue after kernel upgrade, but I'm not
sure if it exactly the same bug:
https://forum.manjaro.org/t/solved-bluetooth-fail-after-2019-05-17-stable-update/87892
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2019-05-18 17:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-18 17:35 bugzilla-daemon [this message]
2019-05-18 22:10 ` [Bug 203643] [REGRESSION][BISECTED] Sixaxis gamepad no longer connects via Bluetooth bugzilla-daemon
2019-05-18 23:42 ` bugzilla-daemon
2019-05-21 20:23 ` bugzilla-daemon
2019-05-21 20:45 ` bugzilla-daemon
2019-05-21 20:47 ` bugzilla-daemon
2019-05-21 20:49 ` bugzilla-daemon
2019-05-21 23:10 ` bugzilla-daemon
2019-05-22 0:16 ` bugzilla-daemon
2019-05-22 13:34 ` bugzilla-daemon
2019-05-22 19:11 ` bugzilla-daemon
2019-05-22 20:30 ` bugzilla-daemon
2019-05-23 7:58 ` bugzilla-daemon
2019-05-23 8:38 ` bugzilla-daemon
2019-05-29 14:04 ` bugzilla-daemon
2019-05-30 17:22 ` bugzilla-daemon
2019-06-05 4:59 ` bugzilla-daemon
2019-06-05 18:58 ` bugzilla-daemon
2019-06-07 8:33 ` bugzilla-daemon
2019-06-07 16:11 ` bugzilla-daemon
2019-06-25 16:33 ` bugzilla-daemon
2019-07-01 10:51 ` bugzilla-daemon
2019-07-01 12:26 ` 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-203643-62941@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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).