can confirm this issue as well
if steam could simply pass the path into xdg-open and allow us to open a non steam game folder it could save us a lot of time.
what may be an even better addition would be to allow us to open the compatdata folder of non steam games. Currently, the compatdata folders for non steam games are stored in ~/.local/share/Steam/steamapps/compatdata/ under a directory named with seemingly random numbers.
Considering its quite hard to decipher which directory is which, a button in steam to open the compatdata of non steam games (and steam games will also benefit greatly from this although their directory is partially easier to find due to the numbers being the games steamappid) would be very useful.
Looking forward to seeing steam teams take on this. I'm surprised something like this hadn't already been implemented.
+1 for this. It really irritates me that it doesn't work.
This is fixed for me on the latest Steam Client Beta!!
Now it would still be even better if we could have an extra option to access the compatdata of the non-steam game entry, since right now they are currently in a randomly generated directory
Closing per the last comment.
It's fixed now on the latest stable Steam client (1751405894). It can open game's "START IN" path.
I appreciate all of your work.
Nothing extracted yet.
Your system information
Additional system information
Computer Information:
Manufacturer: ASRock
Model: B550M Pro4
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: AuthenticAMD
CPU Brand: AMD Ryzen 5 5600X 6-Core Processor
CPU Family: 0x19
CPU Model: 0x21
CPU Stepping: 0x0
CPU Type: 0x0
Speed: 4651 MHz
12 logical processors
6 physical processors
Hyper-threading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Supported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Unsupported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Unsupported
AVX512VNNI: Unsupported
SHA: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
Operating System Version:
Fedora Linux 38 (Workstation Edition) (64 bit)
Kernel Name: Linux
Kernel Version: 6.4.15-200.fc38.x86_64
X Server Vendor: The X.Org Foundation
X Server Release: 12201009
X Window Manager: GNOME Shell
Steam Runtime Version: steam-runtime_0.20230801.56012
Video Card:
Driver: AMD AMD Radeon RX 6800 (navi21, LLVM 16.0.6, DRM 3.52, 6.4.15-200.fc38.x86_64)
Driver Version: 4.6 (Compatibility Profile) Mesa 23.1.7
OpenGL Version: 4.6
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 59 Hz
VendorID: 0x1002
DeviceID: 0x73bf
Revision Not Detected
Number of Monitors: 1
Number of Logical Video Cards: 1
Primary Display Resolution: 3840 x 2160
Desktop Resolution: 3840 x 2160
Primary Display Size: 18.90" x 10.63" (21.65" diag), 48.0cm x 27.0cm (55.0cm diag)
Primary VRAM: 16384 MB
Sound card:
Audio device: ATI R6xx HDMI
Memory:
RAM: 64212 Mb
VR Hardware:
VR Headset: None detected
Miscellaneous:
UI Language: English
LANG: en_US.UTF-8
Total Hard Disk Space Available: 952244 MB
Largest Free Hard Disk Block: 928602 MB
Storage:
Number of SSDs: 2
SSD sizes: 1000G,1000G
Number of HDDs: 0
Number of removable drives: 0
Please describe your issue in as much detail as possible:
I could not open a non-Steam game's directory with by clicking "Browse local files" in Steam Desktop Client (I mean the one in the screenshot), but I could open a Steam game's directory. That function does not work regardless whether TARGET path and START IN path that can be set via "Properties..." have space characters or not.
I saw the following
xdg-openhelp message, when I launchedsteamfrom the terminal.Steps for reproducing this issue:
Additional info
Issues #8907 #9447 encounter simmilar problem that Steam cannot open the file-picker for them. On the other hand, this issue says Steam cannot open the filesystem viewer, e.g., Windows Explorer in Windows, Dolphin in KDE and GNOME Files in GNOME.
I can open the filesystem viewer (GNOME Files in my case) via
xdg-open <path or file:///url>I think Steam launches it with null string likexdg-open '', which prints out the same help message as opening a non-Steam game's directory.