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
Clementine segfaults when QT_QPA_PLATFORM=wayland #6587
Comments
I can repro. As indicated by the trace above, shortcut keys need to be configured. |
After opening the preferences menu, selecting "Use GNOME's shortcut keys", and reopening using Wayland, things seem to work as expected. I suppose this is a bug - Clementine should do something other than crash if the shortcut settings are insufficient. |
So, it looks like this was fixed once before. #6469 |
I think I discounted that issue originally because the trace was slightly different - perhaps the cause is the same. |
Yeah, that other fix looks for org.kde.kglobalaccel, so it specifically targets kde systems. The 3rd party qxt library that we're using hasn't been maintained since 2014, so maybe some of the features have since been implemented in the base qt. |
A stopgap to prevent the crash could be to check QGuiApplication::platformName for "wayland". But should also figure out a way to let the user know that shortcuts won't work in this case. |
It opens now on wayland. |
Before posting
Please follow the steps below and check the boxes with [x] once you did the step.
System information
Please provide information about your system and the version of Clementine used.
Expected behaviour / actual behaviour
I expect Clementine to run under wayland. However, when I run clementine with QT_QPA_PLATFORM=wayland under GNOME, it immediately crashes with a segfault (no other output).
I've also tried on Weston - same issue.
I use two monitors with fractional scaling enabled. The issue occurs regardless of how many monitors are connected.
Steps to reproduce the problem (only for bugs)
Run
QT_QPA_PLATFORM=wayland clementine
The text was updated successfully, but these errors were encountered: