From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 215776] New: Unable to reconnect Bluetooth keyboard after disconnection
Date: Wed, 30 Mar 2022 10:49:32 +0000 [thread overview]
Message-ID: <bug-215776-62941@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=215776
Bug ID: 215776
Summary: Unable to reconnect Bluetooth keyboard after
disconnection
Product: Drivers
Version: 2.5
Kernel Version: 5.13.0-37
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: zacmarco@gmail.com
Regression: No
Good morning,
kernel 5.13.0-37.
zacmarco@ZacBuild:~$ uname -a
Linux ZacBuild 5.13.0-37-generic #42~20.04.1-Ubuntu SMP Tue Mar 15 15:44:28 UTC
2022 x86_64 x86_64 x86_64 GNU/Linux
I have a bluetooth keyboard that goes automatically in power save mode after a
few minutes IDLE (I think 3). After this happens, a key press is enough to wake
the keyboard up again. In these conditions, I am not able to reconnect the
keyboard, I see the bluetooth subsystem trying to connect, but it keeps
disconnecting immediately, without even a chance of typing a single char.
Whenever this happens, I see the following in the kernel logs:
[ 1004.980840] Lockdown: systemd-logind: hibernation is restricted; see man
kernel_lockdown.7
[ 1009.107227] evdi: [I] (card0) Connector state: connected
[ 1009.107297] evdi: [I] (card0) Edid property set
Matter of fact, the only way I have to restore normal functionality is to pair
the keyboard again, like it was connected for the first time.
The issue appears in all the following cases:
- I don't use the keyboard for a few minutes (going to power-save mode)
- I do a keyboard power cycle
- I reboot the PC
Looking at existing issues, this seems similar to the following:
https://bugzilla.kernel.org/show_bug.cgi?id=204765
That however has been resolved a couple of years back.
I use this keyboard on a Windows PC as well, and there I don't have any issues
(so it should not be a keyboard problem).
Please let me know if you need additional debug information.
Thank you
Marco
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-03-30 10:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 10:49 bugzilla-daemon [this message]
2022-03-30 13:50 ` [Bug 215776] Unable to reconnect Bluetooth keyboard after disconnection bugzilla-daemon
2022-03-30 13:50 ` bugzilla-daemon
2022-03-30 16:11 ` bugzilla-daemon
2022-03-30 16:17 ` bugzilla-daemon
2022-04-08 5:51 ` 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-215776-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;
as well as URLs for NNTP newsgroup(s).