You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, Workbench is considered as "probably safe" by Flathub and GNOME Software.
The reason it is not considered "Safe" is because we require network and audio permission (via --socket=pulseaudio and --share=network. Those are not strictly required to use Workbench and are only needed for a handful of demos. In addition, we would also like to add a permission for gamepads workbenchdev/demos#88
Eventually there will be portals for all of these things but until then we need static permissions.
Let's
remove those permissions so that Workbench is considered safe
add a mechanism for demos to advertise which permissions they need - maybe flatpak-finish-args: ["--socket=fallback-x11"] in main.json
when a needed permission is not enabled, Workbench should show a dialog on "Run" to explain what this is about and how to enable the permission using flatpak overrides
Since overrides are permanent - it should be a one time thing only anyway.
The text was updated successfully, but these errors were encountered:
Hey, and sorry for the late response! I can have a shot at it if you can provide some textual content / an instruction set to be conveyed in the dialog. I'm not too knowledgeable on that stuff 😃
Currently, Workbench is considered as "probably safe" by Flathub and GNOME Software.
The reason it is not considered "Safe" is because we require network and audio permission (via
--socket=pulseaudio
and--share=network
. Those are not strictly required to use Workbench and are only needed for a handful of demos. In addition, we would also like to add a permission for gamepads workbenchdev/demos#88Eventually there will be portals for all of these things but until then we need static permissions.
Let's
flatpak-finish-args: ["--socket=fallback-x11"]
inmain.json
flatpak overrides
Since overrides are permanent - it should be a one time thing only anyway.
The text was updated successfully, but these errors were encountered: