-
Notifications
You must be signed in to change notification settings - Fork 0
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
Running this flatpak claims wayland even under X11 #5
Comments
Thanks for the report! Could you please check the output of |
When I run that in a terminal emulator I get:
Which is not what I expected. I can however confirm that running XDG_SESSION_TYPE=x11 flatpak run codes.merritt.Nyrna does indeed starts the application in X11 mode. |
My understanding is that I tried installing Fedora with XFCE, and |
Thank you for the clarification. |
You make a good point; I will give a think on how to do the check logic so it can pass even if the environment variables are broken.. Thanks! 💙 |
Provides hint if user environment variables are not as expected and gives us a chance of running successfully anyway: flathub/codes.merritt.Nyrna#5
Provides hint if user environment variables are not as expected and gives us a chance of running successfully anyway: flathub/codes.merritt.Nyrna#5
I made a change to the session check, now it will only present the error if Wayland is actually detected; if the environment variable is unexpected it will try to load normally and emit an error to console about the unexpected variable. New version pushing to Flathub shortly.. hopefully that will be an improvement. Thanks for the report and ideas! 💙 🎉 |
When I run the flatpak version of this application, installed from flathub, the window show up but states:
I am in fact using X11, using the XFCE4 desktop environment.
Could it be some internal variable forcing wayland, in the flatpak that is causing this? Something equivalent to GDK_BACKEND=wayland for GTK?
In general other QT, GTK2+3+4 and other gui toolkit flatpak applications work fine in this installation.
The text was updated successfully, but these errors were encountered: