-
Notifications
You must be signed in to change notification settings - Fork 32
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
AppImage not launching after update from 1.1.8 to 1.2.0 #82
Comments
I think the issue is:
Try the following workaround for now: QT_QPA_PLATFORM=xcb ./BlockstreamGreen-x86_64.AppImage |
The root issue is that the previous version worked on the exact same system that the update doesn't work on. I was always running Wayland, as most modern GNU/Linux systems do at this point. Shouldn't the update run fine without user input? The Green AppImage is the only variable that has changed, so I don't see how that suggests an issue with AppImage or Wayland. I appreciate the workaround though. For the record, it didn't work. |
Yes, it will be fixed in the next release.
Yes, here are the changes that caused this issue:
Internally Qt will pick the qpa plugin according to the environment, and it's selecting wayland. But seems that you are experiencing similar issues as: moonlight-stream/moonlight-qt#916
Not sure if you noticed a typo in the workaround command, if not please try again. |
@mattkwarren I believe this has been fixed, please reopen otherwise. Just update to 1.2.3. You can also get the flatpak https://flathub.org/apps/com.blockstream.Green |
I'm getting the same issue with version 2.0.3 here. The workaround doesn't work for me too.
Trying to use 1.1.8 just in case i don't get the error message but it still aborts:
|
@darosior please install libxcb-cursor0 and try again. |
Description
Version
1.2.0 (AppImage)
Steps to reproduce
Try to launch the application
Expected behaviour
The application should launch
The application never launches, even after complete removal, resinstallation, and machine restart and updates.
Device or machine
Fedora 37
The text was updated successfully, but these errors were encountered: