From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 203643] [REGRESSION][BISECTED] Sixaxis gamepad no longer connects via Bluetooth
Date: Tue, 25 Jun 2019 16:33:41 +0000 [thread overview]
Message-ID: <bug-203643-62941-XlLj0iNUY3@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203643-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203643
Scall (bluesun654@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bluesun654@gmail.com
--- Comment #20 from Scall (bluesun654@gmail.com) ---
(In reply to Andriy Perevortkin from comment #10)
> Sadly the RFC patch above does not fix it for me, the revert does
> The device is edifier w330nb headset.
It also did not fix it for my two Sony DualShock 4 Wave Blue CUH-ZCT1 (the
issue was reproducible with both), although it did for the following devices:
* Sony DualShock 4 Glacier White CUH-ZCT1 (same generation as the Wave Blue
ones);
* Microsoft Bluetooth Mobile Keyboard 6000;
* Memteq Bluetooth Optical Mouse.
The only way to solve the issue for my two DualShock 4 Wave Blue was to revert
the culprit commit, just like it has been done recently ->
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.1.10&id=b528880e8b0167c34cb36c1b4e6165192f76267c
Just to confirm that patch does not work for all devices.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2019-06-25 16:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-18 17:35 [Bug 203643] New: [REGRESSION][BISECTED] Sixaxis gamepad no longer connects via Bluetooth bugzilla-daemon
2019-05-18 22:10 ` [Bug 203643] " 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 [this message]
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-XlLj0iNUY3@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.