O Steam funciona bem, mas trava quando eu aplico os seguintes passos:
Agora o cliente de vapor trava na inicialização. Eu só vejo uma janela em branco sem qualquer conteúdo. Eu suponho que deveria ser o pop-up de login ("Conectando a conta steam").
A única solução é reiniciar o meu sistema. Se eu tentar killall steam && steam , ele ainda trava novamente no mesmo ponto.
Aqui está a saída do console:
Running Steam on ubuntu 14.10 64-bit
STEAM_RUNTIME is enabled automatically
[2015-01-02 16:06:15] Startup - updater built Nov 21 2014 16:23:41
Looks like steam didn't shutdown cleanly, scheduling immediate update check
[2015-01-02 16:06:15] Checking for update on startup
[2015-01-02 16:06:15] Checking for available updates...
[2015-01-02 16:06:16] Download skipped by HTTP 304 Not Modified
[2015-01-02 16:06:16] Nothing to do
[2015-01-02 16:06:16] Verifying installation...
[2015-01-02 16:06:16] Performing checksum verification of executable files
[2015-01-02 16:06:17] Verification complete
Requested Force create but SharedObjectMutex already created
Forced create but already created for SharedObjectEvent
Forced create but already created for SharedObjectEvent
--- here it hangs. After a reboot, it would continue like that ---
Running Steam on ubuntu 14.10 64-bit
STEAM_RUNTIME has been set by the user to: /home/phil/.steam/ubuntu12_32/steam-runtime
Aqui está a saída de ~/.steam/error.log :
rm: cannot remove ‘/home/phil/.steam/steam’: Is a directory
rm: cannot remove ‘/home/phil/.steam/bin’: Is a directory
Installing breakpad exception handler for appid(steam)/version(1416617579)
Installing breakpad exception handler for appid(steam)/version(1416617579)
Gtk-Message: Failed to load module "overlay-scrollbar"
Gtk-Message: Failed to load module "overlay-scrollbar"
Installing breakpad exception handler for appid(steamwebhelper)/version(20141121162341)
Installing breakpad exception handler for appid(steamwebhelper)/version(1416587021)
Installing breakpad exception handler for appid(steamwebhelper)/version(1416587021)
Installing breakpad exception handler for appid(steamwebhelper)/version(20141121162341)
Installing breakpad exception handler for appid(steamwebhelper)/version(1416587021)
[0102/162746:ERROR:nss_util.cc(1018)] Failed to load NSS libraries.
Installing breakpad exception handler for appid(steam)/version(1416617579)
Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 70: non-double matrix element
Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 70: non-double matrix element
Fontconfig warning: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 78: saw unknown, expected number
Installing breakpad exception handler for appid(steam)/version(1416617579)
Installing breakpad exception handler for appid(steam)/version(1416617579)
Installing breakpad exception handler for appid(steam)/version(1416617579)
Installing breakpad exception handler for appid(steam)/version(1416617579)
Installing breakpad exception handler for appid(steam)/version(1416617579)
FillInMachineIDInfo took a total of 0 milliseconds
Installing breakpad exception handler for appid(steam)/version(1416617579)
Installing breakpad exception handler for appid(steam)/version(1416617579)
Installing breakpad exception handler for appid(steam)/version(1416617579)
Generating new string page texture 2: 48x256, total string texture memory is 49,15 KB
Generating new string page texture 3: 256x256, total string texture memory is 311,30 KB
Eu tentei várias soluções recomendadas, por exemplo:
killall steam && rm ~/.steam/steam/appcache mv /etc/fonts/conf.d/10-scale-bitmap-fonts.conf{,.BAK} No entanto, apenas uma reinicialização corrige o problema inicial.
Estou usando o Ubuntu 14.10 (64 bits). (Meu gerenciador de janelas é o i3. Não pense que é relevante, mas li sobre problemas com o xmonad.)
Eu poderia resolvê-lo instalando a versão de 32 bits do libnss3:
sudo apt-get install libnss3:i386
Isso corrige o seguinte erro em ~/.steam/error.log :
[0102/162746:ERROR:nss_util.cc(1018)] Failed to load NSS libraries.
(Ainda não tenho certeza porque o problema não ocorre após uma reinicialização).