Hi,

I have a very weird issue I can't quite trace, and I have no idea where to start looking. Maybe someone has a decent hint where to start debugging. It looks like some keyboard handling issues in Wayland apps.

I have switched from bookworm+kde5+wayland to trixie+kde6+wayland a few
months ago and it has been a very smooth experience. I have had a few
issues with Firefox that could have started back then, but I can't
really tell because they are so minor I immediately shrugged them off.

Issue #1
I cannot login to Paypal because I can only enter five digits of the 6-digit TOTP 2FA code. The field for the 6th digit just stays empty. I shrugged this off to Paypal not caring about Firefox users or Firefox having intruced a new bug (I usually use Firefox upstream binaries)

These are not random drops like in #3, I have not found a way to enter this digit

Issue #2:
We have an internal app for our inventory where there are some fields showing suggestions based on a backend query when you start typing. Recently I noticed that the query did not start until I entered at least two digits _and_ then pressed backspace. The entered text is displayed just fine, but the suggestions don't even start to get loaded up until I press backspace.

I reported an internal bug and they said it was working fine for them on Firefox. And it does, on other systems.

Issue #3:
When connecting to a Proxmox system you have the option to open a shell on the host, a container or a VM. In the console for text mode (host and container) about 20-30% of the keypresses get lost, making it hard to work and impossible to login. It does not happen in the console for graphical mode (an ordinary VM)

I tried to pinpoint issues and came up empty

- it happens in both Debian-provided Firefox ESR (128.10.0esr-1) and the
Firefox upstream binaries (138.0.1 right now, but has been for a while)
- it happens with a fresh firefox profile
- it does NOT happen if firefox is started with MOZ_ENABLE_WAYLAND=0
- it does NOT happen on a fresh user profile (new user)
- I cannot see this on my work device (bookworm+kde5+wayland), although that's
another user profile of course

I can not figure out how Wayland (seems to be related to Wayland,
because running Firefox without Wayland fixes all of these issues) could
cause issues #1 and #2, so I have no idea where to start. Especially
since it seems to depend on something in my user profile, but not the
Firefox profile.

Bernhard

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Bernhard Schmidt <berni@birkenwald.de> wrote:

Hi,

I have a very weird issue I can't quite trace, and I have no idea where to start looking. Maybe someone has a decent hint where to start debugging. It looks like some keyboard handling issues in Wayland apps.

[...]

I tried to pinpoint issues and came up empty

- it happens in both Debian-provided Firefox ESR (128.10.0esr-1) and the
Firefox upstream binaries (138.0.1 right now, but has been for a while)
- it happens with a fresh firefox profile
- it does NOT happen if firefox is started with MOZ_ENABLE_WAYLAND=0
- it does NOT happen on a fresh user profile (new user)
- I cannot see this on my work device (bookworm+kde5+wayland), although that's
another user profile of course

I can not figure out how Wayland (seems to be related to Wayland,
because running Firefox without Wayland fixes all of these issues) could cause issues #1 and #2, so I have no idea where to start. Especially
since it seems to depend on something in my user profile, but not the
Firefox profile.

Update, removing ibus (which is a hard dependency of the closed source
zoom client, so that had to go) fixes the issue.

Bernhard

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)