Skip to content

v1.0.1 — Legion Go 1 keyboard recovery

Choose a tag to compare

View all tags
@github-actions github-actions released this 05 Aug 19:14
v1.0.1
5ae8259
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

If you installed v1.0.0 on a Legion Go 1 — or on a Steam Deck or ROG Ally running Bazzite
or ChimeraOS — and lost your on-screen keyboard entirely, this release fixes it. Sorry
about that.

Recover an affected install

Double-click Recover My Keyboard.desktop, or run:

handheld-kbd-recover

Re-running ./install.sh repairs the same thing. Either route restores Steam's keyboard and
switches this one to mirror mode. handheld-kbd-recover --stock-only stands everything down
and hands the desktop back to Steam's keyboard.

What was broken

The installer chose its "seamless" trigger by grepping InputPlumber's default profile for
button: Keyboard. That profile is generic — it carries the mapping on every device — so
seamless mode was selected on hardware where no button can ever emit the event. The Legion
Go 1's InputPlumber driver declares Gamepad:Button:Keyboard but nothing physical sends it;
the Steam Deck and ROG Ally drivers don't reference it at all. The remapped button did
nothing, and because the KWin script still forced Steam's on-screen keyboard to
opacity = 0.0, both keyboards were gone.

Stock SteamOS on a Steam Deck was unaffected — it doesn't ship InputPlumber — as was the
Legion Go 2, which has a real keyboard button.

Fixed

  • Seamless mode is selected by DMI product name (Legion Go 2) rather than by the generic
    InputPlumber profile; every other device defaults to mirror mode, which needs no hardware
    button
  • Steam's keyboard is only made transparent once this one is known to appear — mirror mode
    qualifies inherently, seamless mode waits for proof the trigger fired. A dead trigger now
    leaves you with the stock keyboard instead of nothing
  • The daemon falls back to mirror mode for the session if the InputPlumber remap fails
  • handheld-kbd-ip-remap verifies the profile actually loaded, warns when a device reports
    no keyboard button, and fails loudly instead of silently
  • Home and End dropped from the full layout — the arrow cluster and PgUp/PgDn already
    cover that navigation

Added

  • handheld-kbd-recover and a double-clickable Recover My Keyboard.desktop, because typing
    is not an option when you have no keyboard
  • This changelog, and a tag-driven release workflow

Thanks to the Legion Go 1 user who reported it and confirmed the fix.

Assets 4
Loading