protonscr

Proton 5.13 build error

protonopen
ValveSoftware/Proton#4461 · opened 2020-12-12 by promexahnk · updated 2020-12-15 · 2 comments · github
Ppromexahnk 2020-12-12 github

Hardware: https://linux-hardware.org/?probe=d802289f2c
Ubuntu 20.10

oooo@Oooo:~/proton$ make install
vagrant up
Platform: 4 CPUs, 4096 MB memory
Bringing machine 'debian10' up with 'virtualbox' provider...
==> debian10: Checking if box 'generic/debian10' version '3.1.12' is up to date...
==> debian10: Machine already provisioned. Run vagrant provision or use the --provision
==> debian10: flag to force provisioning. Provisioners marked to run always will still run.
vagrant rsync debian10
Platform: 4 CPUs, 4096 MB memory
==> debian10: Rsyncing folder: /home/oooo/proton/ => /home/vagrant/proton
==> debian10: - Exclude: [".vagrant/", "vagrant_share"]
Platform: 4 CPUs, 4096 MB memory
make: Entering directory '/home/vagrant/build-proton_5.13-local'
make downloads -f Makefile NO_NESTED_MAKE=1
make[1]: Entering directory '/home/vagrant/build-proton_5.13-local'
make[1]: Nothing to be done for 'downloads'.
make[1]: Leaving directory '/home/vagrant/build-proton_5.13-local'
make: Leaving directory '/home/vagrant/build-proton_5.13-local'
Connection to 127.0.0.1 closed.
vagrant ssh -c 'make -C "build-proton_5.13-local"/ ENABLE_CCACHE=1 STEAM_DIR=/vagrant/ install'
Platform: 4 CPUs, 4096 MB memory
make: Entering directory '/home/vagrant/build-proton_5.13-local'
make install -f Makefile NO_NESTED_MAKE=1
make[1]: Entering directory '/home/vagrant/build-proton_5.13-local'
cp -n ../proton/fonts/liberation-fonts/src/LiberationSans-Regular.sfd ../proton/fonts/liberation-fonts/src/LiberationSans-Bold.sfd ../proton/fonts/liberation-fonts/src/LiberationSerif-Regular.sfd ../proton/fonts/liberation-fonts/src/LiberationMono-Regular.sfd obj-fonts
cp -n ../proton/fonts/liberation-fonts/src/LiberationSans-Regular.sfd ../proton/fonts/liberation-fonts/src/LiberationSans-Bold.sfd ../proton/fonts/liberation-fonts/src/LiberationSerif-Regular.sfd ../proton/fonts/liberation-fonts/src/LiberationMono-Regular.sfd obj-fonts
fontforge -quiet -script ../proton/fonts/scripts/generatefont.pe obj-fonts/LiberationSans-Regular.sfd "Arial" "Arial" "Arial"
/bin/bash: fontforge: command not found
make[1]: *** [../proton/build/makefile_base.mak:1486: obj-fonts/LiberationSans-Regular.ttf] Error 127
make[1]: Leaving directory '/home/vagrant/build-proton_5.13-local'
make: *** [../proton/build/makefile_base.mak:17: nested_make] Error 2
make: Leaving directory '/home/vagrant/build-proton_5.13-local'
Connection to 127.0.0.1 closed.
make: *** [Makefile:115: install] Ошибка 2

FontForge is installed, trying to call it manually opens it

oooo@Oooo:~$ fontforge
Copyright (c) 2000-2020. See AUTHORS for Contributors.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
with many parts BSD http://fontforge.org/license.html. Please read LICENSE.
Version: 20190801
Based on sources from 15:50 UTC 11-Jun-2020-ML-D-GDK3.

Any ideas?

Ssrgtlord 2020-12-13 github

Just went through something similar on Ubuntu 20.04. Make sure you have the latest tested drivers installed through the ubuntu software updater. Make sure your steam library is on an ext4 partition. Delete all files within the steam compatdata folder. Delete proton 5.13 and steam linux runtime soldier. Within the steam library do a search for proton 5.13 and steam linux runtime soldier. From there you can verify the tool integrity. This fixed my proton 5.13 issue

Aaeikum 2020-12-15 github

I'd suggest destroying the vagrant VM and letting it try again. Run vagrant destroy in your proton directory, then try make install again.

Proton versions