[BUG] No Wayland support in Flatpak

[Bammede]

Bug Description
The app doesn't work on Wayland in Fedora Silverblue. X11 works fine.

To Reproduce
Steps to reproduce the behavior:

1. Run the app on Wayland in Fedora

Screenshots
If applicable, add screenshots to help explain your problem.

Info (please complete the following information):

• Operating system: Fedora Silverblue
• App version: newest
• Package version (flatpak/snap/other): newest

[aandrew-me]

Strange, I am on wayland myself and I had no issues. It would be super helpful if you could try enabling wayland socket in flatseal for the app, and let me know if it works :)

[Bammede]

on my Fedora Silverblue the app works on X11 only

[aandrew-me]

Even with that option enabled? Can you try running the app from the terminal
flatpak run io.github.aandrew_me.ytdn
and send the output

[Bammede]

x display not found

[aandrew-me]

I installed Fedora Silverblue, tried launching the app and it launched without any problem. So that would mean that something is wrong in your system

[Bammede]

and do you have xwayland disabled as I have?

[aandrew-me]

and do you have xwayland disabled as I have?

Is it disabled on a fresh install?

[aandrew-me]

Looks like its enabled, how did you disable it? And why would you disable it?

[Bammede]

I use fedora secureblue which has xwayland disabled by default for security reasons.

[aandrew-me]

Ah I see, I will try to set things up

[Adam-Ladd]

I suspect this may be a fedora issue. I am running on the KDE spin of fedora. The app previously worked fine on the same spin but it currently either fails to launch or launches and then shows only a white screen. I have tried uninstalling and re-installing several times but it is still not working.

P.S.
There was an issue recently where an update to yt downloader would always show up in my updates but then fail because it was attempting to update to the current version. I initially re-installed ytDownloader in hopes of fixing this issue which is when the no launch / white screen issue began so I suspect this may be related.