Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   bugzilla-daemon@kernel.org
To:     linux-bluetooth@vger.kernel.org
Subject: [Bug 216845] New: JBL GO 2 only recognized after restarting
 `bluetoothd`
Date:   Sat, 24 Dec 2022 22:01:59 +0000
Message-ID: <bug-216845-62941@https.bugzilla.kernel.org/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Auto-Submitted: auto-generated
MIME-Version: 1.0
Precedence: bulk

https://bugzilla.kernel.org/show_bug.cgi?id=3D216845

            Bug ID: 216845
           Summary: JBL GO 2 only recognized after restarting `bluetoothd`
           Product: Drivers
           Version: 2.5
    Kernel Version: 6.1-rc8
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: pmenzel+bugzilla.kernel.org@molgen.mpg.de
        Regression: No

Created attachment 303469
  --> https://bugzilla.kernel.org/attachment.cgi?id=3D303469&action=3Dedit
`sudo btmon -w /dev/shm/linux-6.1-rc8-btmon.txt`

Using Debian sid/unstable with Linux 6.1-rc8, *bluez* 5.66-1 and
gnome-control-center *1:43.1-2*, going into the Bluetooth section of
*gnome-control-center* and starting bluetoothd with `sudo systemctl start
bluetooth.service` the *JBL GO 2* is not shown (pairing mode is activated).
Only stopping bluetooth and starting it again, it=E2=80=99s showing up. Ple=
ase find the
btmon trace attached.

--=20
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.=