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

Stop forcing Wayland for Qt #209

Open
ilya-fedin opened this issue Jun 26, 2020 · 0 comments
Open

Stop forcing Wayland for Qt #209

ilya-fedin opened this issue Jun 26, 2020 · 0 comments

Comments

@ilya-fedin
Copy link

ilya-fedin commented Jun 26, 2020

tdesktop has recently been updated to core20 that has Qt 5.12 and, therefore, has support for native Wayland.
Qt desktop helper has a block that forces Wayland even if a compositor is blacklisted by Qt

GNOME is blacklisted due to a bug that fixed in upstream a long time ago, but still actual in 18.04 LTS. But, since snapcraft-desktop-helpers forces Wayland, people see this flickering by default, what is not a good UX and complains in tdesktop issues.

I believe that the fix for mutter should be backported to 18.04 LTS or snapcraft-desktop-helpers should stop forcing Wayland.

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

No branches or pull requests

1 participant