Input Capture not working in Plasma 6.1 about lan-mouse

[feschber]

Update: Got in contact with KDE devs. Should be fixed in 6.1.1 it was a type mismatch in dbus

[feschber]

You can now set

capture_backend = "LayerShell"

in config.toml as a workaround

[feschber]

Okay TLDR:

Plasma 6.1.0 introduced the input-capture portal, i.e. the "frontend" to libei.
Previously, the layer-shell backend was used as a fallback, which is basically a 1px wide window that grabbed the mouse on the edge of the screen.

Now with the plasma input capture portal there were two issues:

• Plasma used a wrong type in serialization, causing deserialization to fail in ashpd. This is now fixed in 6.1.1 after I reported it.

• The second issue is that plasma does not (yet?) report barrier_ids, when input capture is activated.
  This is an optional addition of the spec, however I expected it to be implemented, which is not the case.
  So keep in mind, this is not a plasma bug and please dont report bugs ;).
  The Input Capture Portal works by defining "barriers" and giving them an id. Then, when input capture is activated, The compositor reports the position and optionally a barrier id, which I can use to check which barrier was activated (i.e. which lan-mouse client).

There is several ways to go about this:

• Wait for plasma to implement barrier_ids & only support one client until this is done
• Add the option to fallback to the layer-shell capture backend (I'd still prefer this to be a fallback)
• Work around barrier_ids by calculating the activated barrier from the activation position of the cursor

Nr. 3 is probably the most favourable.

[feschber]

This log is unrelated. Did you update xdg-desktop-portal-kde as well?

[xf-]

yes - xdg-desktop-portal-kde 6.0.90-1

[feschber]

Ah I just noticed: they apparently implemented the input-capture portal. So that's interesting. I will have to test that later!

[xf-]

I'm not in a hurry, just reported the issue. It is still a beta.

[feschber]

Got around to testing this. I am getting valid barriers but not receiving any input events... Will have to see if thats a kwin bug or what else is going on here.

[xf-]

Is the second issue 6.1.1 input (mouse, keyboard) freezes as soon as I touch edge?

[DrYak]

@xf- : yup exactly. (My setup suffers the same).

[feschber]

The specific reason, why its getting stuck is actually because ashpd does not yet correctly handle the case of no barrier_id being sent.
Its already fixed but not yet in a new release.

[xf-]

The specific reason, why its getting stuck is actually because ashpd does not yet correctly handle the case of no barrier_id being sent. Its already fixed but not yet in a new release.

I build the main branch and I had the issue. You mean committed and pushed towards main or a git release?

[feschber]

No, the barrier_id is fixed in the ashpd main branch. It still requires a workaround in lan-mouse and an update of ashpd after there is a new ashpd release.

[DrYak]

(Any ETA when you could tag a new release with capture_backend ?)

[xf-]

You can now set

capture_backend = "LayerShell"

in config.toml as a workaround

Didn't work, maybe I added it in wrong spot, but via cli argument it works :)

[feschber]

It should go on the top of the file

[feschber]

This should now be fixed.
Unfortunately, there seems to be an issue with the "cursor shake" desktop effect on plasma, which results in a captured cursor appearing visible again, so please be aware of that ;)

https://bugs.kde.org/show_bug.cgi?id=490495