Use default Depth for Xvnc #1071
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
imobachgs
approved these changes
Dec 5, 2022
|
✔️ Public Jenkins job #243 successfully finished |
|
FYI, |
|
✔️ Internal Jenkins job #141 successfully finished |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Bugzilla
https://bugzilla.suse.com/show_bug.cgi?id=1205585
Problem
On installations using Xvnc, sometimes the font rendering is broken in the Qt UI to the point of making some fonts illegible.
See the wizard steps on the left side.
Underlying Cause
@Vogtinator found out that there is a bug in the Qt libs:
https://bugreports.qt.io/browse/QTBUG-109169
Workaround
@Vogtinator also suggested to drop using the
-depth 16option when startingXvncto avoid getting into that special case. That's what this PR does.