Public bug reported:
## Description
After upgrading to `at-spi2-core 2.60.4-0ubuntu0.1` from `resolute-updates`,
**lxterminal
windows render correctly but accept no keyboard or mouse input at all**. The
window is
drawn, terminal output continues to appear, but keystrokes do nothing and the
window
cannot be focused or moved by dragging its titlebar.
The application is not hung: the process sits normally in `poll()` in its GTK
main loop
and continues to accrue CPU time. Output written directly to the terminal's pty
(`printf "x" > /dev/pts/N`) renders immediately, so the rendering path is
healthy — only
input is affected.
Downgrading the at-spi2 stack to `2.60.0-1` (the version in the `resolute`
release pocket)
restores input immediately. Setting `NO_AT_BRIDGE=1` also works around it on
2.60.4.
### Bisect
All three trials were run in the **same WSLg/RDP session** (same `msrdc.exe`
PID), with an
lxterminal window at positive screen coordinates, and with rendering confirmed
working by
writing a marker string to the terminal's pty:
| at-spi2 stack version | ATK bridge | Can type? |
|---|---|---|
| `2.60.4-0ubuntu0.1` | enabled (as shipped) | **No** |
| `2.60.4-0ubuntu0.1` | disabled via `NO_AT_BRIDGE=1` | Yes |
| `2.60.0-1` | enabled (as shipped) | Yes |
The five packages downgraded together: `at-spi2-core`, `at-spi2-common`,
`libatspi2.0-0t64`, `libatk1.0-0t64`, `libatk-bridge2.0-0t64`.
### Scope — other GTK3 applications are NOT affected
This appears specific to lxterminal. Tested on 2.60.4 with the bridge
enabled:
* `lxterminal` 0.4.1-1 (GTK3 + VTE) — **input dead**
* `sakura` 3.8.9-1build1 (GTK3 + VTE) — works normally
* `gtk3-demo` (GTK3, no VTE) — works normally
So it is neither "all GTK3 apps" nor "all VTE terminals". sakura links the same
`libvte-2.91.so.0`, `libatk-1.0.so.0`, `libatk-bridge-2.0.so.0` and
`libatspi.so.0` as
lxterminal and is unaffected, so something specific to how lxterminal builds
its widget
hierarchy or its accessible tree appears to be the trigger.
I have not isolated the exact code path, so this may ultimately belong against
`lxterminal` rather than `at-spi2-core` — but since the change that broke it
shipped in an
at-spi2-core SRU, filing here for triage.
### Possibly relevant upstream changes
The 2.60.4 upstream release notes list two changes, both in the
input/event area:
* "Device manager: make use of process identification data when available
through
`queryPointer`"
* "Correct deregistration of application-specific event listeners"
and upstream 2.60.5 then contains:
* "Attempt to fix event listeners still being wrongly deregistered in
some cases"
which suggests the 2.60.4 event-listener change was incomplete. A backport of
2.60.5 (or
2.60.6) may be the fix. I have not been able to test 2.60.5 as it is not
packaged for
resolute.
## Steps to reproduce
1. On Ubuntu 26.04 under WSL2/WSLg, `sudo apt install lxterminal`
2. Ensure `at-spi2-core` is at `2.60.4-0ubuntu0.1` (from `resolute-updates`)
3. Launch it from Windows:
`"C:\Program Files\WSL\wslg.exe" -d <distro> --cd "~" -- lxterminal`
4. Try to type in the window, or drag its titlebar.
**Expected:** keystrokes reach the shell; the window can be focused and moved.
**Actual:** the window renders and shows the shell prompt, but ignores all
input.
Workaround:
wslg.exe -d <distro> --cd "~" -- env NO_AT_BRIDGE=1 lxterminal
## Environment
* Ubuntu 26.04 LTS (resolute), WSL2
* Kernel: `6.18.33.2-microsoft-standard-WSL2`
* WSL 2.7.11.0 / WSLg 1.0.73.2 / MSRDC 1.2.7214, on Windows 11 26200.9168
* `at-spi2-core` 2.60.4-0ubuntu0.1 (broken) vs 2.60.0-1 (works)
* `lxterminal` 0.4.1-1
* `libgtk-3-0t64` 3.24.52-0ubuntu1, `libvte-2.91-0`
* GTK is using the **Wayland** backend (`WAYLAND_DISPLAY=wayland-0`); the apps
are Wayland
clients of WSLg's weston, not X11 clients (confirmed: `xdotool` sees no
client windows).
* AppArmor is disabled on this system
(`/sys/module/apparmor/parameters/enabled` = `N`), so
it is not a confinement issue.
## Note for triagers
This system also has an unrelated, intermittent WSLg **rendering** fault
(weston's RDP
backend dropping to its software copy path, flagged by a `[WARN:COPY MODE]`
prefix in the
window title, correlating with `dxgkio_query_adapter_info: Ioctl failed: -22`
from
`dxgkrnl` and `Failed to initialize glamor, falling back to sw`). In that state
*no* WSLg
window presents at all and the whole desktop appears frozen.
That fault is **independent of this bug** and was explicitly controlled for:
every trial
above was run in a session with a clean window title and with rendering
positively
verified before judging input. Please don't let it distract from the input
regression —
they are two separate problems that happened to coincide.
** Affects: at-spi2-core (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2163632
Title:
at-spi2-core 2.60.4-0ubuntu0.1 (SRU) breaks all keyboard/mouse input
in lxterminal under WSLg
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/2163632/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
