-
Notifications
You must be signed in to change notification settings - Fork 78
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
Question: How to set a persistant resolution? #304
Comments
Ideally Cage would support a mode where it completely delegates output configuration to kanshi, instead of making decisions on its own. |
So there are no startup -options or -scripts that can be used now - and |
You can use wlr-randr instead of kanshi if you don't need hotplug. However cage will still perform its own modeset before wlr-randr has the chance to change it to something else. |
What I ended up doing was calling
More on this here: https://github.com/SergeySn/PiKiosk/?tab=readme-ov-file#run-the-sample-compose-app-with-cage -> |
I am able to set the desired resolution with
wlr-randr
after Cage is started.I understand, that changing the resolution is not possible before Cage is started.
To provide some form of resolution persistance: what could be a method to call wlr-randr while starting Cage?
I experimented with some old-school X11 start configurations, like
~/.xinitrc
, but none worked.In the Cage wiki/issues there was only a daemon named kanshi mentioned on a related topic.
Is there any additional start configuration or xinit-comparable script-hook for cage/wayland?
The text was updated successfully, but these errors were encountered: