Hello @Damglador, this reads like https://github.com/ValveSoftware/steam-runtime/issues/470. In general, games started from Steam are expected to be run in a Steam Linux Runtime container, and that container environment is not expected to have unlimited access to the host system.
@kisak-valve but should it affect me if I don't use a runtime? In Aseprite and Blender I don't have any runtimes enabled and Steam is launched using /usr/bin/steam-native. Or does Steam apply a runtime to Linux games by default? In this case, is there a way I can disable the runtime to test if it works without it?
Your system information
Please describe your issue in as much detail as possible:
I've noticed this with Aseprite at first, but now also see this with Blender. The desktop files created by Steam include only
steamand the "game" ID inExec, meaning if I want to open a png with Aseprite, it'll just open Aseprite and will not pass the file to it. In command line doingsteam steam://rungameid/365670 /home/damglador/Documents/Blender/Шахи.blendorsteam steam://rungameid/365670 -- /home/damglador/Documents/Blender/Шахи.blendalso doesn't pass the file to the program, but launching it directly with ELF does:/home/damglador/Games/SteamLibrary/steamapps/common/Blender/blender /home/damglador/Documents/Blender/Шахи.blend. So Steam can't pass files to programs it launches? At least it for sure doesn't do this by default with desktop files it creates.Steps for reproducing this issue: