XCB surface: Don't crash on wayland proper #221
Closed
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
When running the X11 caps viewer on wayland, QX11Info::connection is null
HildarTheDorf
force-pushed
the
X11OnWaylandCrash
branch
from
4191d77 to
b55010f
Compare
This was referenced Nov 21, 2024
|
Code should probabally not use the Qt connection at all for querying X information, as Qt could be using XCB, Wayland, or neither. I intend to make a longer PR fixing that but for now this should be a harmless stopgap. |
|
Resolved as part #225 |
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.
When running the X11 caps viewer on wayland, QX11Info::connection is null.
This prevents a segfault, although no useful surface information is returned.