We cannot reproduce. There were several changes made to the non-steam shortcuts code, so this may have been addressed.
Please see if you can reproduce in the beta client that shipped today (Feb 17th), and provide an ID for an uploaded crash report.
Nevermind! The beta client crashes but our internal code doesn't ..
This will be fixed in next beta client update (planned to ship today).
Although the crash appears to be fixed, the feature doesn't seem to be entirely functional. Trying to run a non-steam game with custom arguments behaves oddly, first taking an unusually long amount of time to launch (and in Deck's game mode, the "failed cloud sync" dialog popped up.. for a non-steam game), only to launch without the actual arguments.
Repro steps are the same as in the original post too.
Hello @Xinerki, your follow up issue should be tracked separately. Please open a new issue report.
I believe the problems @Xinerki reports are adressed in next update also. See https://github.com/ValveSoftware/steam-for-linux/issues/8164 (meaning, no need to create a new report, this is known)
Your system information
Feb 10 2023 at 02:38:06Please describe your issue in as much detail as possible:
When using the
steam://rungameid/launch argument to launch a non-Steam game with custom command line arguments, the main Steam process will crash.If running the main Steam process from a terminal, it shows the following output:
In
dmesg, the following segfault is shown:Steps for reproducing this issue:
.desktopfile.steam "steam://rungameid/15059998769837768704//test"in a terminal, replacing15059998769837768704with the game ID from the shortcut.