Don't delete RandR outputs and CRT controllers #283
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Draft for now until work resumes on devel.
This change doesn't delete outputs or CRT controllers when the screen configuration changes. Instead, the outputs are disconnected.
This emulates the behaviour of other virtual X servers (e.e. tigervnc) and prevents X applications from encountering BadRROutput or BadRRCtrc errors.
The following command can now be used to monitor RandR events generated by
xorgxrdp
. Previously it could fail withBadRROutput
when reconnecting from a client with fewer screens.