Not starting in Linux Mint 22.3-zena - installed via Flathub

[GitHubbet]

Hi
Just to inform you about this.

Not a problem, I wanted to try it and I could not.

Thanks
M

Info:
wattage + 2 instances of bwrap run - looking via System Monitor
I am no expert - just reporting.

[v81d]

Thanks for reporting this. I'll take a look at it and do some testing when I have the time.

[arthurmoldom]

Came to check if anyone else also had issue. Similar case.
System:
Kernel: 6.8.0-51-generic arch: x86_64 bits: 64 compiler: gcc v: 13.3.0 clocksource: tsc
Desktop: Cinnamon v: 6.4.6 tk: GTK v: 3.24.41 wm: Muffin v: 6.4.1 with: Docker,docker vt: 7dm: LightDM v: 1.30.0
Distro: Linux Mint 22.1 Xia base: Ubuntu 24.04 noble.

If you need any more info please let us know

[v81d]

Sorry, I can't seem to reproduce this bug on a similar setup (Linux Mint 22.3 - Cinnamon 64-bit running Linux 6.17.0-14-generic). Do you notice any logs or errors when trying to start the app using flatpak run io.github.v81d.Wattage?

[arthurmoldom]

Will try again later... Unfortunatelly my cat cannot remote startup it so i can ssh...

[v81d]

Update: After some more experimenting, I found that this problem only happens if I switch display servers (i.e., from Cinnamon X11 to Wayland and vice versa) without rebooting. However, if I directly boot into X11 or Wayland, the app launches fine. This seems to happen for a lot of GTK/GNOME apps that implement the --socket=fallback-x11 argument in their Flatpak manifests (see flatpak/flatpak#4690 and AchetaGames/Epic-Asset-Manager#258).

After setting flatpak override --user --nosocket=wayland --nosocket=fallback-x11 --socket=x11 io.github.v81d.Wattage, everything seemed to be functional again on both X11 and Wayland.

According to flatpak/flatpak#4690, something could be detecting a Wayland socket (i.e., in $XDG_RUNTIME_DIR/wayland-0) despite actually being in the X11 session. Removing that socket (rm $XDG_RUNTIME_DIR/wayland-0) temporary fixes the problem until you enter a Wayland session again.

This seems to be a problem more related to Flatpak's sandboxing system rather than the GTK apps themselves, but I'll leave this issue open until there's more information or when I find a more permanent solution.