Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Actually, I might not want to install it, since I just patched the kernel to support my DJ controller and I just got my system getting mixxx to run bypassing pulseaudio, which was a big challenge.
Trying now to replicate it on a fresh install.
In the case of nvidia, it usually means something has not been updated due to some dependency. Update/installing it again usually works to get the remainder of the dependencies in that are required to get the DKMS+driver combo working.
Obviously I am not a fan of DKMS, but licensing issues might be a reason to opt for it.
update-alternatives: error: alternative link /usr/lib/i386-linux-gnu/libGLX_indirect.so.0 is already managed by nvidia
dpkg: error processing package glx-alternative-nvidia:i386 (--configure):
subprocess installed post-installation script returned error exit status 2
Errors were encountered while processing:
glx-alternative-nvidia:i386
E: Sub-process /usr/bin/dpkg returned an error code (1)
That might be the reason for the recovery loop?
I tend to keep my SteamOS installation as unaltered as possible, but with the latest (snail) pace of updates I ended modifying my installation in certain parts, to keep up "with the rest of the world".
So I want first to make sure that this issue is not a results of my meddling.
Anyway, I did a fresh install from the latest DVD (which went OK), then added the beta repos and I got caught in the same error loop. According to unattended-upgrades logs everything is fine, what is not fine is the Xorg.0.log, which displays the same segmentation fault on both SteamOS installations tested:
After that I had to dkms build -m nvidia-current -v <...> by hand.
In upgrade cases like this, I replace my .xsessionrc in one that starts a normal window manager instead of a steam session. That defeats the recovery loop, because X usually starts, but steam itself crashes due to lack of opengl support, which tears down the X session.
I hate to say it, but that might be a good point to start a terminal with recovery options.
"UPGRADE" "UPGRADE ME HARDER" "FORCE UPGRADE ME HARDER" "APTITUDE" "DKMS ALL"
something like that.
I think aptitude and DKMS ALL are the most important ones, but aptitude is to hard on a normal end user.
Edit: this conflict was supposedly fixed in builds 145 and 148, but still caused issues.