Bug 1226389 - Aeon Desktop doesn't block the screen lock with the Flatpak versions of Heroic Games Launcher and RetroArch
Summary: Aeon Desktop doesn't block the screen lock with the Flatpak versions of Heroi...
Status: RESOLVED UPSTREAM
Alias: None
Product: openSUSE Aeon
Classification: openSUSE
Component: Flatpak (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Richard Brown
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-15 13:54 UTC by Eduardo Medina
Modified: 2024-06-25 08:29 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eduardo Medina 2024-06-15 13:54:14 UTC
Hi, I'm trying Aeon Desktop more seriously and I see that the Flatpak versions of Heroic Games Launcher and RetroArch don't block the lock screen, so the screen turns black/off while your are using those apps in fullscreen.

With Heroic Games Launcher I could fix the problem setting the ' --talk-name=org.freedesktop.ScreenSaver ' option and enabling the Bluetooth through Flatseal, but with RetroArch I can't avoid the lock screen.

The bug appears if you use a gamepad. If you use the keyboard and the mouse, the bug doesn't appear because those peripherals reset the time for the shutdown of the screen everytime you use them. I use an 8BitDo Pro 2 in Xbox mode and a DualShock 4 through Bluetooth, so I think this is reproducible with any controller. The bug is reproducible in wired mode too.

The problem here is that the bug doesn't appear in Silverblue with the default configuration provided by the Flatpak versions of Heroic Games Launcher and RetroArch, so I think there is something missing or misconfigured in Aeon Desktop. Heroic Games Launcher and RetroArch are verified apps in Flathub and they are very important for the Linux Gaming ecosystem.

If you don't have a controller for video games, you can set the shutdown of the screen in one minute (it doesn't mind if there is a password or not) with GNOME Setting and after you can run a game through Heroic Games Launcher or RetroArch in fullscreen. If the screen turns off, it means that the bug is still there.

I don't know if this old RetroArch bug can give you some clues, but I'm leaving it out as a precaution. https://github.com/flathub/org.libretro.RetroArch/issues/58

Seeing that Aeon tries to be focused in Flatpak and the out of the box experience and the gaming is one of the supported areas, I think this is an important topic. With Steam everything seems to work correctly.

You can give me instructions to get more information or data.

Sorry if my English is not fully correct.
Comment 1 Eduardo Medina 2024-06-18 17:18:16 UTC
I don't know what happened, but now the permissions I set for Heroic Games Launcher doesn't work, so now I'm forced to disable the screen shutdown through GNOME Settings.
Comment 2 Richard Brown 2024-06-25 08:29:26 UTC
The issues are clearly a result of upstream flatpaks not correctly using the dbus inhibit route provided

This is documented in https://github.com/flathub/org.libretro.RetroArch/issues/58 already and I suspect the same is true in Heroic (there are bug reports implying the problem may be wider there, affecting both X11 AND Wayland, whereas RetroArch just has the problem on wayland as it falls back to an x11 specific workaround normally)

Either way, this is nothing Aeon can fix