[For dual-display devices] Pin virtual keyboard to the bottom screen

[tslmy]

Summary

This configures Armada to consume a patched KWin package and use per-device configuration to pin Plasma's virtual keyboard to a specific display connector.

On dual-screen handhelds such as the AYN Thor, the intended behavior is for the on-screen keyboard to appear on the bottom display instead of following KWin's active-output heuristic. The Thor device config sets:

ARMADA_VIRTUAL_KEYBOARD_CONNECTOR=DSI-1

The Plasma session exports that device setting before starting KWin. Devices that leave the setting empty keep upstream KWin's current active-output behavior.

Tested with an AYN Thor:

Before	After

Package Dependency

Per review feedback, the KWin patch has been moved to armada-packages: armada-os/armada-packages#22 . This PR now consumes the KWin package image instead of rebuilding KWin inside the Armada base image.

Warning

The current KWIN_PKG value uses :latest until the package PR publishes a digest that can be pinned here.

Testing

bash -n build_files/build.sh build_files/10-base-packages.sh system_files/usr/libexec/armada/device-env system_files/usr/libexec/armada/start-plasma tests/thor-virtual-keyboard-test.sh
tests/thor-virtual-keyboard-test.sh

[pacoa-kdbg]

Pocket DS follow-up: #195 configures ARMADA_VIRTUAL_KEYBOARD_CONNECTOR=DSI-2, using the verified lower-display connector from #160. It requires this PR’s patched-KWin build path.

[JPyke3]

Hey all,

I do like the changes here. But I believe we should package kwin just like we package the other components in armada-packages instead of in the base repo.

Also - I feel we shouldn't be using built-time flags to manage things like if the image should ship with components specific to the thor. Ideally we would ship one image that everyone can consume and use per-device configs to manage the differences.

The expected structure would therefore be:

• an armada-packages PR that builds and publishes the patched KWin package;
• this armada PR updated to consume that package;
• the per-device ARMADA_VIRTUAL_KEYBOARD_CONNECTOR configuration retained here.

I’m requesting changes rather than closing this, since the feature itself looks useful and the existing PR can be reworked around that packaging model.

[tslmy]

Great idea @JPyke3 ! I wasn't aware of the existence of https://github.com/armada-os/armada-packages, and I love the idea of it. It honestly also makes my life easier if and when I choose to upstream this feature to KWin itself.

PR updated. Tested on real device with an image built from fe6b0ee.

[JPyke3]

Looks all good now! Thanks for splitting it up! Unfortunately I won't have time to merge this one in the next few hours (waiting for kwin to compile) but when I wake up I'll get on it tomorrow :D

[tslmy]

Thank you @JPyke3 ! This is my first merged PR to this repo. I'm elated.