Skip to content
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

Don't require Xlib to behave synchronously #249

Merged
merged 1 commit into from
Jan 2, 2022
Merged

Don't require Xlib to behave synchronously #249

merged 1 commit into from
Jan 2, 2022

Conversation

tsujan
Copy link
Member

@tsujan tsujan commented Jan 1, 2022

Otherwise, after a recent libx11 commit, the app might exit with code 1 (see the comment inside the code).

Closes #247

Otherwise, after a recent libx11 commit, the app might exit with code 1 (see the comment inside the code).

Closes #247
@tsujan
Copy link
Member Author

tsujan commented Jan 1, 2022

@stefonarch
We could wait for a week or so and then make a point release if no problem happens.

@stefonarch
Copy link
Member

@stefonarch We could wait for a week or so and then make a point release if no problem happens.

I agree.

@tsujan
Copy link
Member Author

tsujan commented Jan 2, 2022

All things are difficult before they are easy. This is really a libx11 problem that no one has encountered except for us; who else uses XSynchronize()? Merging…

@tsujan tsujan merged commit 03e987e into master Jan 2, 2022
@tsujan tsujan deleted the async_X branch January 2, 2022 05:35
@tsujan
Copy link
Member Author

tsujan commented Feb 13, 2022

BTW, on my old laptop, lxqt-panel wan't ready for use immediately after it started; it was frozen for a few annoying seconds after startup. This patch also fixed that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Shortcuts Ignored After Upgrade
2 participants