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

AppImage not launching after update from 1.1.8 to 1.2.0 #82

Closed
mattkwarren opened this issue May 19, 2023 · 6 comments
Closed

AppImage not launching after update from 1.1.8 to 1.2.0 #82

mattkwarren opened this issue May 19, 2023 · 6 comments

Comments

@mattkwarren
Copy link

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

@borgbyte
Copy link
Contributor

borgbyte commented May 19, 2023

I think the issue is:

  • you are running Wayland, check echo $XDG_SESSION_TYPE
  • in that case Green/Qt will use Wayland QPA plugin
  • looks like there are some issues regarding Wayland and AppImage

Try the following workaround for now:

QT_QPA_PLATFORM=xcb ./BlockstreamGreen-x86_64.AppImage

@mattkwarren
Copy link
Author

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.

@borgbyte
Copy link
Contributor

borgbyte commented May 19, 2023

Shouldn't the update run fine without user input?

Yes, it will be fixed in the next release.

The Green AppImage is the only variable that has changed

Yes, here are the changes that caused this issue:

  • before: qt 5.15.2 and the official build only included xcb qpa plugin
  • now: qt 6.4.3 and both xcb and wayland plugins are builtin in the official binary.

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
cnr-isti-vclab/meshlab#738

For the record, it didn't work.

Not sure if you noticed a typo in the workaround command, if not please try again.

@borgbyte
Copy link
Contributor

borgbyte commented Jul 1, 2023

@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

@borgbyte borgbyte closed this as completed Jul 1, 2023
@darosior
Copy link

darosior commented Apr 6, 2024

I'm getting the same issue with version 2.0.3 here. The workaround doesn't work for me too.

$ QT_QPA_PLATFORM=xcb ./BlockstreamGreen-x86_64.AppImage 
qt.qpa.xcb: could not connect to display 
qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: xcb.

Aborted

Trying to use 1.1.8 just in case i don't get the error message but it still aborts:

$ QT_QPA_PLATFORM=xcb ./BlockstreamGreen-x86_64\(2\).AppImage 
Aborted

@borgbyte
Copy link
Contributor

@darosior please install libxcb-cursor0 and try again.

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

3 participants