Closed kwiesmueller closed 2 years ago
According to your config, you are not using this fork but upstream rofi which does not support wayland officially.
However we also don't support the -m
options in wayland mode at the moment, so you are out of luck.
I built from this repo, but let me check. Also I only used the -m option to see if I can fix the default behavior.
The version string in your logs is definitely from upstream (actually, current tip of the next branch). And because you have "monitor layout" in your logs, it means that rofi is starting in x11 mode.
Thanks, my bad. I followed https://github.com/lbonn/rofi/blob/wayland/INSTALL.md and seems like I took the wrong GitHub URL to pull from :-/
Ah I see, good point...
Actually we have started modifying these instructions, so we could fix these links as well.
Version
Version: 1.7.0-41-g1520a4a5 (next)
Configuration
swaymsg -t get_outputs
Launch Command
set $menu "~/.local/bin/rofi -i -combi-modi run,drun -modi drun,run -show run -terminal foot -m -5 | xargs swaymsg exec --"
Steps to reproduce
What behaviour you see
Depending on the value for
-m
rofi shows on the wrong screen. When on-5
(default) it always shows on theHDMI-A-1
. When on-4
it always shows on the opposite screen of the focused window.It seems like the monitors detected by Rofi are kind of wrong or at least don't match sway. I'm fairly certain the 4k screen is running in 4k and the other one in 1440p. Don't know why they identify so differently in rofi. And why their IDs and Names in Rofi are mixed up.
What behaviour you expect to see
Rofi to consistently show on the right screen.