No keyboard input on empty sway workspace

[embik]

Version

[~] rofi -v
Version: 1.1.0

Configuration

Output of rofi -dump-xresources

Launch Command

[~] rofi -show run

Steps to reproduce

• Install sway, a i3-compatible Wayland compositor
• Configure rofi -show drun as $menu
• Reload configuration (Super+Shift+C)
• Switch to empty workspace
• Start launcher (Super+D)

What behaviour you see

• rofi does not receive any keyboard input until you switch to a workspace containing applications
• See sway#267

What behaviour you expect to see

• rofi should properly receive keyboard input on empty workspaces

[DaveDavenport]

Don't have sway, not (yet) interested. Patches are always welcome.
@sardemff7 you got thoughts on this?

[embik]

That's certainly a bummer, but thank you for leaving this issue open. Wayland support (at least I guess that's the problem?) would be pretty rad.

[sardemff7]

XWayland support of wlc is not perfect, can you try using Weston? And ideally with a recent GNOME too (selecting Wayland session)?
Weston has basic but good support for XWayland, and Mutter should support it almost perfectly (as it is the same code managing for plain X anyway). That would target the issue cause more closely.

[embik]

I will conduct some tests with GNOME and Weston and report back on any relevant findings.

[DaveDavenport]

@sardemff7 mentioned that it worked for him on weston:

SardemFF7 | afaict, rofi works correctly in Weston, so the issue really is wlc+XWayland to me

We also had a quick discussion on making rofi work on wayland (adding support for backends and add wayland), conclusion is it should be possible with reasonable amount of effort, that I won't be doing it, but if somebody wants to do it I will support the effort.

[embik]

A Wayland backend does sound more reasonable as XWayland is supposed to be a "hack-y" way of supporting legacy XOrg, not a permanent solution (at least, that's how I understand it). Would it make sense to close this bug and track backend support and a Wayland backend separately? I'm not fit to write any of this, unfortunately.

[carnager]

@embik: Long time goal is proper wayland support in rofi, which now that we got rid of most, if not all xlib dependencies is easier than ever.

[carnager]

I wonder if -normal-window works properly?

[NateBrune]

I would love Wayland support for rofi and can confirm issues with sway.

[sardemff7]

@NateBrune Thanks for the confirmation.

See #446 and the wiki page for more information on “Wayland support”.

[sardemff7]

To everyone:
We know Wayland support would be great, but do not hijack this issue for it.

[DaveDavenport]

closing. 1.5 will (hopefully ) have native wayland support.

[jparsert]

Is the newest version of rofi supposed to fix that?

[DaveDavenport]

@FourtyTwo that will be fixed once we have native wayland support. See linked wiki page.