-
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
output: do not always terminate when last output is destroyed #274
output: do not always terminate when last output is destroyed #274
Conversation
Only terminate if the last output was nested under the Wayland or X11 backend. If not, using DRM backend for example, terminating Cage when unplugging the last monitor or simply turning it off does not seem to be the right behavior.
Tested on one machine with a single monitor. Cage continues running when the monitor cable is disconnected then reconnected however screen resolution changes from 1920x1080 to 720x400. |
@sodface |
wlr-randr output:
|
I was expecting the output to be configured in the preferred mode when handled as new. Do you have logs of Cage built in debug mode? |
See attached. |
Interesting lines are:
Maybe calling |
That seems to have fixed it. Log attached. |
Otherwise, testing to set preferred / "best" mode will always return an error. Consequently, output will simply be configured with last and probably "worst" mode.
I also had the opportunity to test using DRM backends with one or two monitors. Now, Cage does not terminate when last monitor is unplugged. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
Only terminate if the last output was nested under the Wayland or X11 backend. If not, using DRM backend for example, terminating Cage when unplugging the last monitor or simply turning it off does not seem to be the right behavior.
Proposed as a draft for now.
It addresses issue #208 .