Application doesn't close inside flatpak, but local build works

1

Hello,

I’m not sure if this place is a good place to ask for help, If it’s not, simply delete it, and sorry.

I’m trying to help bring dune dynasty project (a reverse enginering project of dune 2 game) to flatpak, we get the project compile and run fine, but when we exit the game, it doesn’t work. The person maintaining it, seems to have it working with the linux subsystem for windows with ubuntu, in X11, but with Fedora & Wayland doesn’t seem to stop, I need to run a kill command or similar to get it to stop. (Black window/full-screen is always there)

Any idea of what it can be?

Thanks,
Jaume.

1 Like
2

Doesn’t sound like a Flatpak issue to me.

You mentioned that you tested:

  • WSL with Ubuntu and X11
  • Fedora with Wayland

So, this could be just an issue with your Wayland code (assuming you have Wayland support), like not releasing the window after closing the game…

So, it would be good to first test if this is reproduceable under Fedora with X11 as well.

If you want to check under Flatpak as well, you could use the arguments --nosocket and --socket to force one system.

For example,

flatpak run --nosocket=x11 --nosocket=fallback-x11 --socket=wayland APP_ID

would give the app only access to the Wayland server, while

flatpak run --socket=x11 --nosocket=fallback-x11 --nosocket=wayland APP_ID

would only provide the app with X11.

3

Thank you,

I know the app is only X11, and I’ve got a wayland, trying the two run samples you comment:

  1. It throws an error, for what I know, the library used there doesn’t support Wayland, and fails
  2. It does exactly the same.

Funny thing, I tried yesterday in the steamdeck, (with bazzite in gnome) and everything worked fine.

I tried restarting my session, into a gnome with xorg, and the problem is still there.

4

Right, I did assume you have Wayland support for my previous comment…
My bad.

Anyway, if you used the same Flatpak on both Steam Deck and your other System, it doesn’t sound to me like its an issue with Flatpak itself.
Maybe related to some GNOME Shell extension or hardware/software correlation?