Installa Steam
Accedi
|
Lingua
简体中文 (cinese semplificato)
繁體中文 (cinese tradizionale)
日本語 (giapponese)
한국어 (coreano)
ไทย (tailandese)
Български (bulgaro)
Čeština (ceco)
Dansk (danese)
Deutsch (tedesco)
English (inglese)
Español - España (spagnolo - Spagna)
Español - Latinoamérica (spagnolo dell'America Latina)
Ελληνικά (greco)
Français (francese)
Indonesiano
Magyar (ungherese)
Nederlands (olandese)
Norsk (norvegese)
Polski (polacco)
Português (portoghese - Portogallo)
Português - Brasil (portoghese brasiliano)
Română (rumeno)
Русский (russo)
Suomi (finlandese)
Svenska (svedese)
Türkçe (turco)
Tiếng Việt (vietnamita)
Українська (ucraino)
Segnala un problema nella traduzione
Regole e linee guida per le discussioni
Segnala questo messaggio
What game is this on.
Do you have any particular Proton settings changed?
File Explorer is now run as a background service, instead of as an executable capable linked library. However, it shouldn't be displaying any actual windows.
As a note, the proton-wine explorer.exe executable should run as a support service. While functionally it can be loaded as a dll like they were doing, not having it already running in the background sets off some anti-cheat and anti-tamper systems because it thinks the game is running in a "modification sandbox" with an altered explorer.exe loaded as a dll.
This is a bug for bug replication of the Windows bug: Explorer.exe always runs in the background even if you are using a different GUI shell service.
If you have a game that was previously running an older version of Proton that is doing this, you may need to purge your compat directory.
To do this back up your game files stored in the compat directory of the game if they aren't cloud-synced, and the dilete the compat directory for the game
The compat directory is: [STEAM_LIBRARY]/compat/[game-id]. You can look up the game ID from the community page URL or store URL for the game. It's the number after "app".
You might note that everything on Steam, even Steam itself and Proton has App IDs. (The Steam Linux Client itself has an app ID of 221410.) These IDs are used for various utilities inside Steam, such as SteamCMD, which is the backend to the Steam Client.
on steam, go to the properties of one of the affected games and add this as launch parameter:
if you then click play, steam should create a text file called "test.txt" directly in your user home folder, instead of actually running the game
post the content of this file here, so we can have a look at exactly what command steam is trying to run for that game...
do the same for a non-affected game, for comparison
it doesn't seem to show anything when I try that command in the launch options it gives me this print out with the following;
waiting for exit and run, which is what seems to be doing when it launches File Explorer after hitting Play, it expects me to launch the game from File Explorer myself by going to the executable of the game.
looks like you got the expected output, but there is one tiny thing you should confirm... is the folder '/media/▆▆▆▆▆▆▆/DH/games/steamapps/common/Okami/okami.exe really spelled with a capital "O"? and is everything else really in smallcaps?
With that taken care of, try items [4], [6] and [7] from this post, for debugging Proton:
https://steamcommunity.com/app/221410/discussions/0/1636417404917541481/
Proton/Wine is case sensitive, Windows is not
That is very possible. I didn't think of that possibility. The default behavior of the Proton launcher on "executable not found" very well may be to launch file explorer.
Case sensitivity doesn't matter all that much since Wine/Proton follows whatever the directory names are in the directory path names, and because Steam Pipe is a thing it'll always find the directory it needs regardless of case sensitivity. https://developer.valvesoftware.com/wiki/SteamPipe
Sounds like the Steam launcher is pointing to the wrong thing. In order to help you I need to know how are you opening it. Are you launching through the menu app list or as you launching from a dock?
Open up the file explorer and browse to the following directory, you should be able to press Ctrl+L to type in the path bar into the file explorer, or copy-paste it.
You should see a file called Steam or Steam (Runtime), right-click that and go to Open With and select Text Editor, in your case it's probably called Kate. If you scroll down a bit it should say something like this;
check if the Exec part is correct and points to the actual Steam binary as shown in my example. If it doesn't have Steam there you'll need to correct it. But you need to have root permission to change the contents of the file and save it.
See Steam OS Accounts on user and root access: https://help.steampowered.com/en/faqs/view/4FD6-1AD6-CDD5-D31E
If the changes were done successfully, go open up Konsole the terminal emulator and type the following commands separately.
This should update the application launchers in both the menu and icon on the taskbar so you can launch them as normal.
you having the same issue on windows means Valve forked up something (the shortcut's path to steam) affecting a handful of users regardless of the OS
either way, i don't know, but you can probably find them easily
1) go to the base url of steam's discussions pages
2) look for a generic discussions community about the steam app (no OS specified = Windows 99% of the time)
3) use the discussions search field to find stuff related to this... "Steam launching Windows Explorer" might be enough