public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <bug-216845-62941@https.bugzilla.kernel.org/> (raw)

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

            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=303469&action=edit
`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’s showing up. Please find the
btmon trace attached.

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

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

             reply	other threads:[~2022-12-24 22:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-24 22:01 bugzilla-daemon [this message]
2022-12-24 22:03 ` [Bug 216845] JBL GO 2 only recognized after restarting `bluetoothd` 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-216845-62941@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