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

Deploy the Wayland platform plugin #189

Open
probonopd opened this issue Nov 20, 2017 · 10 comments · May be fixed by #540
Open

Deploy the Wayland platform plugin #189

probonopd opened this issue Nov 20, 2017 · 10 comments · May be fixed by #540

Comments

@probonopd
Copy link
Owner

probonopd commented Nov 20, 2017

https://bugs.kde.org/show_bug.cgi?id=372346#c3 says:

Wayland is a completely new graphics system. Nothing will run there unless the framework and/or application ports to that stack. For Qt, unless you ship the Wayland platform plugin, your application has no chance to run.

I have a hard time believing that given that Fedora already has switched to Wayland and apps apparently are still running there but if true, then linuxdeployqt better starts deploying the Wayland platform plugin whenever libQtXGui.so is being deployed.

@TheAssassin
Copy link
Collaborator

Due to XWayland being installed on distributions, this shouldn't be a problem in the near future. But yes, it'd be nice if the applications would natively run on Wayland (if available).

We have to investigate whether deploying the Wayland platform plugin will mean that Qt switches to Wayland if available, and falls back to X11 otherwise.

@probonopd
Copy link
Owner Author

probonopd commented Nov 20, 2017

Thanks @TheAssassin I was assuming that XWayland will not go away anytime soon. At least not in the LTE and Enterprise distributions that we are trying to (also) target with AppImages.

@TheAssassin
Copy link
Collaborator

XWayland will probably stay for years. The point is, why bother using XWayland, when you can use Wayland directly.

@DiabeticCrab
Copy link

@probonopd Could you please stop blocking this issue from being resolved and finally merge #540?

It's silly to prohibit a highly demanded feature from being implemented due to ideological reasons and this is hurts AppImage as a whole!

@probonopd
Copy link
Owner Author

probonopd commented Feb 20, 2023

It has been claimed that Wayland can run X11 applications using XWayland. So it should be able to run "normal" applications just fine?

@Elsie19
Copy link

Elsie19 commented Feb 21, 2023

So should we all just run every application we need that has a windows exe under wine or should we all use the native version?

@probonopd
Copy link
Owner Author

probonopd commented Nov 5, 2023

Wayland is still so broken that you can't even set window icons ("Using QT_QPA_PLATFORM=xcb works, though")

https://bugreports.qt.io/browse/QTBUG-101427

If you want to set icons on windows, unlike all other windowing systems apparently Wayland forces one to install .desktop files into the system and use (reverse-DNS notation) application IDs - concepts AppImage is not using.

Blocked by (among others):

@DiabeticCrab
Copy link

DiabeticCrab commented Nov 10, 2023

So your plan is continuing to stall, because some non-critical inconvenience hasn't been sorted out yet? I agree that it needs fixing, but it certainly isn't a blocker. Are you bananas?

@CodeMystic21
Copy link

It has been claimed that Wayland can run X11 applications using XWayland. So it should be able to run "normal" applications just fine?

just because they kind of work doesn't mean a want to run my software in legacy x11 mode.

@CodeMystic21
Copy link

So should we all just run every application we need that has a windows exe under wine or should we all use the native version?

Oh what a great idea with wine. Even better idea: why not then got back to the for sure best operating system and run it NATIVE on windows ..... 🤣

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants