-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Rofi does not work in KDE Plasma 6 (Wayland) #121
Comments
Works fine for me on arch 1.7.5.wayland3.r3.g47ae31eb-1, did you try to build it in a clean chroot? Any warnings about libnkutils during the build ? |
I tried rebuilding it from scratch after clearing yay cache and it now works! |
Actually it's still broken for me (Fedora 40 / Plasma 6). I've tried the system package that Fedora ships, as well as building myself from git (head of wayland branch), and I have temporarily removed my config so it's using builtin defaults. Observed behavior is that no keys work. I can double-click things, but that's it. When run from a console, it spams a bunch of lines like this:
|
Interestingly, on a brand new VM (Fedora 40 + Plasma, fully updated) everything works with the system rofi-wayland package. But my other ("real") system doesn't work, even when the config is removed or it is run with |
@abatkin I have the same issue Fedora 40 and no config. Doesn't take any input |
is this also the same issue?? rofi -show run
(process:10717): Wayland-ERROR **: 22:21:18.309: Rofi on wayland requires support for the layer shell protocol
fish: Job 1, 'rofi -show run' terminated by signal SIGTRAP (Trace or breakpoint trap)
|
@kaushiksahu18 gnome wayland is not supported as they have their do not expose a public protocol in the like of layer shell afaik. This is a separate issue |
Same in nixpkgs-24.05, but in nixpkgs-23.11 (1.7.5+wayland2) can work. |
Same on Fedora 40 as well. |
Same issue on COSMIC on nixos |
For the NixOS people, I upgraded to latest nixos-24.05 and rofi keyboard input started working again. Give it a shot. No idea what caused the assert to trigger in the first place, something about library versions I guess. |
It seems keyboard input fails on linux kernel v6.6 and works on v6.10, for me. Using niri, wayland. |
With quick googling, this may be related: https://bugs.kde.org/show_bug.cgi?id=477251 Maybe someone can make a try with the changes there: #158 I remember playing with on_demand on other DMs and the behavior was slightly different, it would need re-testing there as well. |
Rofi version (rofi -v or git commit in case of build issue)
Version: 1.7.5+wayland3-3-g47ae31eb (makepkg)
Configuration
https://gist.github.com/LorenzoBettini/c80a1f9909f10ad7c7aead165c99d33f
Theme
https://gist.github.com/LorenzoBettini/9d245000f3242fab327c97fc6c3609fc
Timing report
No response
Launch command
rofi -show drun
Step to reproduce
Expected behavior
rofi should react to typing and scrolling and clicking
Actual behavior
rofi does not react to typing and scrolling and clicking
Additional information
When trying to interact with rofi the console from where I launched it shows:
Using wayland display server protocol
I've checked if the issue exists in the latest stable release
The text was updated successfully, but these errors were encountered: