After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 767982 - screensaver-proxy: Better metadata for SDL games
screensaver-proxy: Better metadata for SDL games
Status: RESOLVED INCOMPLETE
Product: gnome-settings-daemon
Classification: Core
Component: plugins
unspecified
Other All
: Normal normal
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2016-06-23 16:45 UTC by Bastien Nocera
Modified: 2018-10-25 11:32 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
screensaver-proxy: Better metadata for SDL games (3.01 KB, patch)
2016-06-23 16:46 UTC, Bastien Nocera
none Details | Review
screensaver-proxy: Better metadata for SDL games (8.80 KB, patch)
2018-05-04 10:49 UTC, Bastien Nocera
none Details | Review

Description Bastien Nocera 2016-06-23 16:45:58 UTC
.
Comment 1 Bastien Nocera 2016-06-23 16:46:03 UTC
Created attachment 330273 [details] [review]
screensaver-proxy: Better metadata for SDL games

XXX unfinished
Comment 3 Bastien Nocera 2018-05-04 10:49:02 UTC
Created attachment 371664 [details] [review]
screensaver-proxy: Better metadata for SDL games

SDL applications (usually games) don't have any API to provide an
application ID and a reason for inhibition, so if those are Flatpak'ed
get the application ID from the Flatpak, and use the gathered name as
the reason for inhibition.
Comment 4 Bastien Nocera 2018-05-04 10:49:30 UTC
I haven't tested this yet, so beware.
Comment 5 Benjamin Berg 2018-09-17 10:06:06 UTC
Review of attachment 371664 [details] [review]:

To be honest, I am not a huge fan of this special case just for the sake of SDL. And this case is so specific, that it will break already if SDL e.g. marks the string as translatable.

If we do this hack, would it be possible to document it in the SDL code to ensure we are notified about changes there?