From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 86931] hid-generic 0005:099A:0500.0001: unknown main item tag 0x0
Date: Mon, 12 Jan 2026 10:15:19 +0000 [thread overview]
Message-ID: <bug-86931-62941-JF4ywN4Rcx@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-86931-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=86931
Bastien Nocera (bugzilla@hadess.net) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
CC| |bugzilla@hadess.net
--- Comment #14 from Bastien Nocera (bugzilla@hadess.net) ---
This should have been fixed by:
https://github.com/bluez/bluez/commit/2645d3f662ebe8e601df628432886d3712b421b3
which will be in the next bluez release after 5.85.
You might need to re-pair your device, would appreciate a test from someone
who's seen the problem.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2026-01-12 10:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-86931-62941@https.bugzilla.kernel.org/>
2016-03-30 17:53 ` [Bug 86931] hid-generic 0005:099A:0500.0001: unknown main item tag 0x0 bugzilla-daemon
2018-01-12 9:21 ` bugzilla-daemon
2018-01-12 17:26 ` bugzilla-daemon
2019-01-30 18:27 ` bugzilla-daemon
2020-10-30 10:05 ` bugzilla-daemon
2021-01-08 14:31 ` bugzilla-daemon
2021-07-18 10:47 ` bugzilla-daemon
2021-07-19 6:58 ` bugzilla-daemon
2024-02-22 12:18 ` bugzilla-daemon
2025-12-18 21:49 ` bugzilla-daemon
2025-12-19 1:28 ` bugzilla-daemon
2026-01-12 10:15 ` bugzilla-daemon [this message]
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-86931-62941-JF4ywN4Rcx@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