-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
lp1850729: Disable QtWayland in desktop launcher #2340
Conversation
I wonder if this does not harm at all distros. Do we need to install libx11-xcb1 for that? |
I don't think so. Fedora patched Qt to make this change: https://fedoraproject.org/wiki/Changes/Qt_Wayland_By_Default_On_Gnome |
The change should work on all distros and only makes a formerly implicit assumption explicit. My first attempt to patch the launcher failed, because I got confused by the redundant occurrences. New builds with an effective patch are available in the testing repositories. I will remove the patch with the release of 2.2.3. |
LGTM. Do you mind adding some info to the Wiki's troubleshooting page? Not everybody launches Mixxx via the *.desktop entry (e.g. users of Sway WM might just run the |
Merge? |
Yes. I have just tested it on Ubuntu Xenial and it still works. |
I'm okay with merging this for the stable branch, but I think we should try to get Mixxx working with the Qt Wayland platform plugin for 2.3. That may require risky changes that wouldn't be appropriate for the stable branch. |
We should not add more requirements, that prevents releasing 2.3. IMHO it is overdue since long. |
Yes, if we don't fix it by the time we release 2.3 that is okay. But I think we should try to fix it soon. |
Workaround for https://bugs.launchpad.net/mixxx/+bug/1850729
Mixxx has massive usability issues and a CPU utilization leak on QtWayland that is now used as the default in Fedora 31 on Wayland if QT_QPA_PLATFORM is unset. By explicitly setting it to "xcb" Qt uses XWayland as a fallback.