I've spent a few days organizing my Linux Steam scripts: https://github.com/shkhln/linuxulator-steam-utils. They might even work outside of my desktop machine if we are lucky. Anybody wants to check this before Steam manages to break itself again?
$ cd /opt/steam-utils/bin/steam-
/opt/steam-utils/bin/steam-install /opt/steam-utils/bin/steam-kill
$ cd /opt/steam-utils/bin/steam-install
cd: /opt/steam-utils/bin/steam-install: Not a directory
$ cd /opt/steam-utils/bin/
$ ls
steam steam-install steam-kill
$ ./steam-install
Downloading Steam...
steam_1.0.0.61.tar.gz 2808 kB 2293 kBps 01s
Extracting bootstrap...
Creating symlink bin -> bin32
Creating symlink bin32 -> steam/ubuntu12_32
Creating symlink bin64 -> steam/ubuntu12_64
Creating symlink root -> steam
Creating symlink sdk32 -> steam/linux32
Creating symlink sdk64 -> steam/linux64
Donwloading runtime...
steam-runtime_0.20190711.3.tar.xz 89 MB 6453 kBps 14s
Extracting runtime...
ELF binary type "0" not known.
/compat/linux/bin/bash: cannot open d: No such file or directory
/compat/linux/bin/bash: �: not found
/compat/linux/bin/bash: 1: Syntax error: ")" unexpected
/compat/linux/bin/bash: 19: Syntax error: Error in command substitution
$
Code:ELF binary type "0" not known.
BTW: Why does it have to be a non-wheel user account?
kldload linux64
solved the issue and I could proceed. In my /boot/loader.conf I have 'linux_load="YES"' for years now as required by the nvidia-driver. What is the recommended entry nowadays? 'linux64_load="YES"' or both?Installing breakpad exception handler for appid(steam)/version(1.0)
[2019-09-11 13:27:35] Installing update...
[2019-09-11 13:27:37] Cleaning up...
[2019-09-11 13:27:37] Update complete, launching...
[2019-09-11 13:27:37] Shutdown
CWorkThreadPool::~CWorkThreadPool: work processing queue not empty: 6 items discarded.
$
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x00000000) differs from mask derived from shader name (0x0000000C) for shader ps-file teeth_flashlight_ps20b ps-index 0 ps-combo 2
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x00000000) differs from mask derived from shader name (0x0000000C) for shader ps-file teeth_flashlight_ps20b ps-index 0 ps-combo 3
CCrossProcessPipe::BWrite wrote too few bytes: 32 (Broken pipe). Continuing.
../common/pipes.cpp (766) : CClientPipe::BWriteAndReadResult: BWaitResult failed, disconnected
../common/pipes.cpp (766) : CClientPipe::BWriteAndReadResult: BWaitResult failed, disconnected
../common/pipes.cpp (766) : Fatal assert failed: ../common/pipes.cpp, line 766. Application exiting.
../common/pipes.cpp (766) : Fatal assert failed: ../common/pipes.cpp, line 766. Application exiting.
ExceptionHandler::GenerateDump waitpid failed:No child processes
No minidump written, nothing to upload.
_ExitOnFatalAssert
$ ../common/pipes.cpp (766) : CClientPipe::BWriteAndReadResult: BWaitResult failed, disconnected
../common/pipes.cpp (766) : CClientPipe::BWriteAndReadResult: BWaitResult failed, disconnected
../common/pipes.cpp (766) : Fatal assert failed: ../common/pipes.cpp, line 766. Application exiting.
../common/pipes.cpp (766) : Fatal assert failed: ../common/pipes.cpp, line 766. Application exiting.
ExceptionHandler::GenerateDump waitpid failed:No child processes
No minidump written, nothing to upload.
_ExitOnFatalAssert
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x00000000) differs from mask derived from shader name (0x0000000C) for shader ps-file teeth_flashlight_ps20b ps-index 0 ps-combo 2
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x00000000) differs from mask derived from shader name (0x0000000C) for shader ps-file teeth_flashlight_ps20b ps-index 0 ps-combo 3
CCrossProcessPipe::BWrite wrote too few bytes: 32 (Broken pipe). Continuing.
../common/pipes.cpp (766) : CClientPipe::BWriteAndReadResult: BWaitResult failed, disconnected
../common/pipes.cpp (766) : CClientPipe::BWriteAndReadResult: BWaitResult failed, disconnected
../common/pipes.cpp (766) : Fatal assert failed: ../common/pipes.cpp, line 766. Application exiting.
../common/pipes.cpp (766) : Fatal assert failed: ../common/pipes.cpp, line 766. Application exiting.
ExceptionHandler::GenerateDump waitpid failed:No child processes
No minidump written, nothing to upload.
_ExitOnFatalAssert
OK, doing akldload linux64
solved the issue and I could proceed. In my /boot/loader.conf I have 'linux_load="YES"' for years now as required by the nvidia-driver. What is the recommended entry nowadays? 'linux64_load="YES"' or both?
This is the message I got at the end, so is that OK?
Code:CWorkThreadPool::~CWorkThreadPool: work processing queue not empty: 6 items discarded.
there were connection problems, I had to push the "Reconnect" button several times to finally log in.
but the news window was black and browsing the store is also not possible, so how would you be able to search and download/install games?
That doesn't happen to me. Although, I have to admit that I didn't investigate the login problem to the root cause, only enough of it to make a workaround. I guess that needs more work.
The regular web browser still works. That's what I use anyway for security reasons.
I have just tried again, same problem.
But can you make it work? And I still don't know how exactly I can install steam games through the browser when the interface does not work.
I'm not sure what you are trying to say. The library view works without in-client web browser.
The library view, yes, this is to view the games that you have already installed.
For example I want to know what games are there for Linux anyway, what demos, which are free to play, search games by category, or if this should work, buy a game...
I disabled steam play in the settings, but that does not change the fact that what you are showing me in your screenshot is a list of what you have already installed.
Where you get SteamOS+Linux(35) I get (2) and where you get Games(99) I get (2) and I repeat, I only get those two in the list because I logged into my existing steam account.
Apart from that, did the log file give you any useful info?
Go buy some or whatever.
Also, to be clear, I'm never going to work on tracing/debugging the damned embedded browser — that's out of scope. It's a huge codebase, it interacts with every API that ever existed
and it's absolutely unnecessary for actual games to function.
Well, that is the whole point for me, how do I do that when the browser does not work?
Well that sounds complicated indeed, maybe somebody else would be willing to do that job?
Use that browser for logging into https://store.steampowered.com/, then add whatever you want to add to your game library. After that it should available in the client in the library view (probably after restart).
There is no library menu on the website, even when you are logged in. However, I could click on a game, click on "Play now" -> "Steam already installed" which would open a window where I could select an application to open it. Pointing it to "/opt/steam-utils/bin/steam" worked.
I installed TF2, it started, I got into the main menu but then it hanged with a stuttering sound.
Installed three more free games but they wouldn't start at all.
I don't know much about these things, but I can only guess that, while SteamOS is based on Debian8, our Centos7 is just not good enough.
I installed TF2, it started, I got into the main menu but then it hanged with a stuttering sound.
there were connection problems, I had to push the "Reconnect" button several times to finally log in.
git pull
, make
, sudo make install
and try again. git pull
before. I downloaded the zip-file from your website, extracted it, which gave me a second folder (as this is obviously the second time), I moved into that folder , did make
and make install
as root. I guess that overwrote thje contents of /opt/steam-utils/ correctly. Then I switched into my special non-wheel user account and changed into /opt/steam-utils/bin/ and ran ./steam-install
which apparently did nothing, just got the prompt again immediately. Consequently, starting steam gave the same reconnection problems again.ran./steam-install
which apparently did nothing
--- steam/bin/steam 2019-09-16 16:03:25.241779000 +0200
+++ /opt/steam-utils/bin/steam 2019-09-16 19:18:21.838663000 +0200
@@ -54,4 +54,4 @@
ENV['SDL_AUDIODRIVER'] = 'dsp'
ENV['STEAM_ENABLE_SHADER_CACHE_MANAGEMENT'] = '0' # ?
-exec steam_root + '/ubuntu12_32/steam', *ARGV
+exec steam_root + '/ubuntu12_32/steam', '-tcp', *ARGV
Running steam with -tcp worked well for the connection issues on my end: