FS#63218 - [steam] Absolute path in desktop files Exec key
Attached to Project:
Community Packages
Opened by Stanisław Wokulski (fenuks) - Wednesday, 17 July 2019, 17:36 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:09 GMT
Opened by Stanisław Wokulski (fenuks) - Wednesday, 17 July 2019, 17:36 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:09 GMT
|
Details
Description:
Package `Exec` keys in steam.desktop and steam-native.desktop contain absolute path to the executable (`/usr/bin/steam-runtime` and `/usr/bin/steam-native` respectively), which makes it more difficult to run steam, for example, in sandbox with firejail (firejail creates symbolic link in `/usr/local/bin`). One is required to copy desktop to local applications directory, and alter it by hand. Please consider removing hard-coded binary path in Exec command. Additional info: * package version(s): 1.0.0.61-1 Steps to reproduce: $ sudo bash -c 'cat << EOF > /usr/local/bin/steam-runtime #!/bin/sh firejail steam "\$@" EOF' $ sudo chmod +x /usr/local/bin/steam-runtime # run desktop file somehow, exo-open is provided by exo $ exo-open /usr/share/applications/steam.desktop # steam is run without sandbox because of hard-coded path |
This task depends upon
Closed by Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:09 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/steam/issues/15
Saturday, 25 November 2023, 20:09 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/steam/issues/15
The package maintainer may or may not choose to fix this now vs. wait for upstream's response. :)