We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Did a quick bisect and a tag 0.0.21 the text still renders normally:
And at least from commit 1ed56c3 :
Tested on a Vmware virtual machine with a wayland compositor (labwc 0.6)
labwc 0.6
The text was updated successfully, but these errors were encountered:
Logs with RIO_LOG_LEVEL=info:
RIO_LOG_LEVEL=info
Log with the issue present: log-bad.txt
Log without the issue: log-good.txt
Sorry, something went wrong.
Unless wgpu and/or vmware get their sh*t together, I'm not sure if there's a viable fix for this :/
At least when using the mesa drivers, a reliable workaround seems to be setting LIBGL_ALWAYS_SOFTWARE=1 to force software rendering.
LIBGL_ALWAYS_SOFTWARE=1
Good finding! Looks related as well gfx-rs/wgpu#1443 , microsoft/wslg#469
No branches or pull requests
Did a quick bisect and a tag 0.0.21 the text still renders normally:
And at least from commit 1ed56c3 :
Tested on a Vmware virtual machine with a wayland compositor (
labwc 0.6
)The text was updated successfully, but these errors were encountered: