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
I tried:
Problem still persists - Steam just keeps getting stuck at login.
Ok so I tried running it through terminal, this is what I got:
First of all I use Playonlinux in order to download the wine version I desire, so I don't install wine version I use in my system, but I can have multiple wine versions for multiple situations.
For steam I use WINE 1.7.37 32bit and winetricks (32bit WINE even if I am using Ubuntu 64bit). I use playonlinux only to download wine versions, but in this case I use wine directly, using bash scripts that have this structure
with this script you can adapt your "launcher" for different wine prefixes, different wine version (previously downloaded with playonlinux) etc. The variable $WINETRICKS should be setted where you downloaded winetricks bash script (in this example winetricks is stored on $HOME)
Well... when you use WINE to install steam you probably want to start in this way:
1) create a first script that has this line after "starting script"
this will linstall steam on $HOME/.local/share/wineprefixes/steam
(so in this case WINEPREFIX is ignored due to winetricks design for this specail case)
Now you can decide:
- either leave wineprefix to default location for steam ($HOME/.local/share/wineprefixes/steam)
- or move wineprefix to another location, so you can have multiple steam installations. Usually you will probably choose to leave steam where is it, but it is your decision
2A) if you decide to leave steam where is it, the other scripts (that will interact with steam) must change the line
3) create a second script (after changing WINEPREFIX correctly) and in this case, after "starting script" you can add libraries you require to add through winetricks (those depends on game you will install).
An example could be:
$WINETRICKS d3dx9
4) finally, when all "installation" step finished, create a last script that will launch steam.
So, after "starting script" you will put this code
Now you can download, "install" and run your game. Perhaps steam will not see immediately you downloaded dependencies on step 3 and it will ask you to install them. But afer this "installation" the game will work.
LOGIN WARNING:
every time you create a new instance of steam you will require to "activate" your login, becouse steam thinks you are accessing your account with another pc and it wants to be sure you are actually the owner of your account. So you will require to open the mail received from steam and "authorize" your new steam instance to access using your account rights.
This is another reason why you probably want to have only one WINEPREFIX for steam for windows (and in this case it is fine to leave steam installed on "$HOME/.local/share/wineprefixes/steam".
Hope it is useful
I've installed them, didn't help. I've noticed that sometimes steam actually gets through the connection process, but after rebooting, it gets stuck again.