STO, Steam Play/Proton version 4.11-7 breaking (but usable by a previous proton version, at least with one since 4.2-9):
An advice from a newbie: try reverting to a previous version SPECIFICALLY FOR STO (or other affected games, if any).
The last working build (for me) was vanilla (beta) 4.11-6 but it's not available for choosing anymore, so I'm using vanilla 4.2-9 (or a custom build)
Explanation/Description: A few days ago I couldn't connect to STO by steam play/proton (mouse clicks couldn't work though cursor could move, so couldn't enter the game from the character selection screen, possibly it came along with other issues, unsure if keyboard worked perfectly or if mousekeys worked), and found out reverting to a previous build specifically for this game, in this case vanilla 4.2-9, allowed me to reconnect (as well as some custom proton build as an option) even if possibly having some issues.
___
your mileage may vary, linux is not supported here officially (we are free to connect as long and when we can,) and I am just a newbie, no responsibility.
Still I think it worth noting, since it's likely to be the difference between being unable to even enter a character (without mousekeys at least) and being able to join STO and hopefully play normally/almost normally.
THIS IS NOT A BUG REPORT and the issue is not cryptic's.
STO, Steam Play/Proton version 4.11-7 breaking (but usable by a previous proton version, at least with one since 4.2-9):
An advice from a newbie: try reverting to a previous version SPECIFICALLY FOR STO (or other affected games, if any).
The last working build (for me) was vanilla (beta) 4.11-6 but it's not available for choosing anymore, so I'm using vanilla 4.2-9 (or a custom build)
Explanation/Description: A few days ago I couldn't connect to STO by steam play/proton (mouse clicks couldn't work though cursor could move, so couldn't enter the game from the character selection screen, possibly it came along with other issues, unsure if keyboard worked perfectly or if mousekeys worked), and found out reverting to a previous build specifically for this game, in this case vanilla 4.2-9, allowed me to reconnect (as well as some custom proton build as an option) even if possibly having some issues.
___
your mileage may vary, linux is not supported here officially (we are free to connect as long and when we can,) and I am just a newbie, no responsibility.
Still I think it worth noting, since it's likely to be the difference between being unable to even enter a character (without mousekeys at least) and being able to join STO and hopefully play normally/almost normally.
THIS IS NOT A BUG REPORT and the issue is not cryptic's.
Some advice from an STO Veteran......
Star Trek Online does not connect to Steam and does not require Steam to work. Steam is only a Portal. Rip the Startrekonline.exe executable out of the folder and put it in it's own folder, then uninstall Steam, and you will be free of Steam.
"You don't want to patrol!? You don't want to escort!? You don't want to defend the Federation's Starbases!? Then why are you flying my Starships!? If you were a Klingon you'd be killed on the spot, but lucky for you.....you WERE in Starfleet. Let's see how New Zealand Penal Colony suits you." Adm A. Necheyev.
STO, Steam Play/Proton version 4.11-7 breaking (but usable by a previous proton version, at least with one since 4.2-9):
An advice from a newbie: try reverting to a previous version SPECIFICALLY FOR STO (or other affected games, if any).
The last working build (for me) was vanilla (beta) 4.11-6 but it's not available for choosing anymore, so I'm using vanilla 4.2-9 (or a custom build)
Explanation/Description: A few days ago I couldn't connect to STO by steam play/proton (mouse clicks couldn't work though cursor could move, so couldn't enter the game from the character selection screen, possibly it came along with other issues, unsure if keyboard worked perfectly or if mousekeys worked), and found out reverting to a previous build specifically for this game, in this case vanilla 4.2-9, allowed me to reconnect (as well as some custom proton build as an option) even if possibly having some issues.
___
your mileage may vary, linux is not supported here officially (we are free to connect as long and when we can,) and I am just a newbie, no responsibility.
Still I think it worth noting, since it's likely to be the difference between being unable to even enter a character (without mousekeys at least) and being able to join STO and hopefully play normally/almost normally.
THIS IS NOT A BUG REPORT and the issue is not cryptic's.
Some advice from an STO Veteran......
Star Trek Online does not connect to Steam and does not require Steam to work. Steam is only a Portal. Rip the Startrekonline.exe executable out of the folder and put it in it's own folder, then uninstall Steam, and you will be free of Steam.
Good advice for Windows, not so much for OP's specific use of Steam's Proton API interpretation layer under Linux.
UPDATE: Problem solved AFAIK with the newest (steamplay/)proton version.
Today proton 4.11-8 was released, and it seems the problem was fixed - STO seems to works for linux users that use the new proton version. (your mileage may vary)
Just to clarify again, this issue was not Cryptic's and this is not a bug report. Also, this allegedly solved issue does not apply to Windows users or to linux users not using steamplay/proton to play STO.
Just a note for completion, since otherwise it may mislead. (again this note is irrelevant to windows user / players who don't use SteamPlay/proton to play to STO, beside noting that a known crash issue may be fixed today for them also.)
If you tried version 4.11-8 (current default) for the 1st time since the 12th of November's patch and crashed/failed, do know there is a more "global" issue in STO (or STO's servers maybe), not related to steam or your OS or your proton version, which may lead to crash.
Do try again to connect STO after today's maintenance which is supposed to solve the crash issue.
Update regarding an issue POTENTIALLY linked to the general crash issue noted above: The crash issue for windows OS seems not to have been fully addressed in that maintenance, and while don't know how linux "fares" in that regard (I don't have the crash issue itself at the moment even though I had a hard time to connect for the 1st time after 12/11,) - there seems to be a possibly linux only issue of a chat system not reconecting after switching a character (even if re-choosing the same character) so that friend list seems in a frozen state and no chat is possible (to be seen or said) - all silently without an error. This issue is solved symptomatically after a full relog. For me it happens with updated OS and drivers. (some kind of an intel GPU which is supposed to be supported)
Since I don't know if it's linked to windows' crash issue or not, and as the game does not officially support linux, we can only wait and see if it's fixed after things are more "stabilized" for windows (or alternatively accept the state as it is). Or hope a dev wants and is able to locate the issue still...
Thanks both leemwatson - I will try your way now using wine and see if it works!
and also tom61sto - you are right as well! but the time has come that I have to try a new solution and try to use another way to run STO beside steam play and steam due to some issue. (though I don't uninstall steam - I seem to need it for other things, and for now also won't deinstall sto from steam at least until have the other installation as a working solution.)
Update: this works but doesn't solve my bug/issue which was the reason for trying
Comments
Some advice from an STO Veteran......
Star Trek Online does not connect to Steam and does not require Steam to work. Steam is only a Portal. Rip the Startrekonline.exe executable out of the folder and put it in it's own folder, then uninstall Steam, and you will be free of Steam.
Good advice for Windows, not so much for OP's specific use of Steam's Proton API interpretation layer under Linux.
Today proton 4.11-8 was released, and it seems the problem was fixed - STO seems to works for linux users that use the new proton version. (your mileage may vary)
Just to clarify again, this issue was not Cryptic's and this is not a bug report. Also, this allegedly solved issue does not apply to Windows users or to linux users not using steamplay/proton to play STO.
If you tried version 4.11-8 (current default) for the 1st time since the 12th of November's patch and crashed/failed, do know there is a more "global" issue in STO (or STO's servers maybe), not related to steam or your OS or your proton version, which may lead to crash.
Do try again to connect STO after today's maintenance which is supposed to solve the crash issue.
Update regarding an issue POTENTIALLY linked to the general crash issue noted above: The crash issue for windows OS seems not to have been fully addressed in that maintenance, and while don't know how linux "fares" in that regard (I don't have the crash issue itself at the moment even though I had a hard time to connect for the 1st time after 12/11,) - there seems to be a possibly linux only issue of a chat system not reconecting after switching a character (even if re-choosing the same character) so that friend list seems in a frozen state and no chat is possible (to be seen or said) - all silently without an error. This issue is solved symptomatically after a full relog. For me it happens with updated OS and drivers. (some kind of an intel GPU which is supposed to be supported)
Since I don't know if it's linked to windows' crash issue or not, and as the game does not officially support linux, we can only wait and see if it's fixed after things are more "stabilized" for windows (or alternatively accept the state as it is). Or hope a dev wants and is able to locate the issue still...
and also tom61sto - you are right as well! but the time has come that I have to try a new solution and try to use another way to run STO beside steam play and steam due to some issue. (though I don't uninstall steam - I seem to need it for other things, and for now also won't deinstall sto from steam at least until have the other installation as a working solution.)
Update: this works but doesn't solve my bug/issue which was the reason for trying