From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 86931] hid-generic 0005:099A:0500.0001: unknown main item tag 0x0
Date: Wed, 30 Mar 2016 17:53:32 +0000 [thread overview]
Message-ID: <bug-86931-62941-JPM4P7Z2yj@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-86931-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=86931
jbMacAZ <jbmacbrodie@yahoo.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jbmacbrodie@yahoo.com
--- Comment #3 from jbMacAZ <jbmacbrodie@yahoo.com> ---
Bluetooth behavior was good in ubuntu 15.10 - bluez5.35, blueman device manager
and kernel 4.3.6. I use a bt mouse and OEM bt keydock (Asus T100-CHI)
Starting with 4.4 thru 4.6-rc1-next*, I have to open blueman's device manager
to search for devices after idle timeouts. I also need to leave the device
manager dialogue open/minimized to prevent rapid loss of connection. Device
pairing is remembered, but manually searching is difficult when the pointing
devices stop working. My test setup has a usb mouse as a workaround.
dmesg has "unknown main item tag 0x0" after each idle timeout". If I move
mouse during boot, it will auto-connect, but it then suffers a rapid timeout
soon after booting. See dmesg posted at #114561. It looks like something is
incrementing the bluetooth input assignment # when anything times out.
--
You are receiving this mail because:
You are the assignee for the bug.
next parent reply other threads:[~2016-03-30 17:53 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 ` bugzilla-daemon [this message]
2018-01-12 9:21 ` [Bug 86931] hid-generic 0005:099A:0500.0001: unknown main item tag 0x0 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
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-JPM4P7Z2yj@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