Try unchecking Civ 5 DirectX 9 and Civ 5 DirectX 10/11 in the Virtu MVP control panel. Issues with opening movies edit If the game crashes to desktop or loads to a black screen, then there may be an incompatibility with the video files. Looks like Aspyr got around to offering a 64-bit version of Civ V for people who use Steam on macs! The newest macOS update Catalina wouldn't run 32-bit programs anymore, so if you wanted to run a 32-bit game like Civ V on steam before yesterday the game wouldn't launch.
Steam is a video game digital distribution service by Valve. Steam offers digital rights management (DRM), matchmaking servers, video streaming, and social networking services. It also provides the user with installation and automatic updating of games, and community features such as friends lists and groups, cloud saving, and in-game voice and chat functionality. - Wikipedia, the free encyclopedia
The Steam client is not open source software, therefore each user must accept the Steam Subscriber Agreement before using the software, then typically accept EULAs or Terms of Use agreements for each particular title accessed through the Steam client.
Valve Corporation has collaborated with open source software organizations such as CodeWeavers (Wine)[1] in order to make closed source games possible to run on open source operating systems.
Games
- Official Steam Linux games list.
Prerequisites
Steam is a 32-bit application and requires a multilibprofile on amd64. That is, during Gentoo installation, when choosing profiles the no-multilib option was not selected. This prerequisite can be ignored if installing Steam in a chroot.
Kernel
Steam expects that /dev/shm, which requires kernel tmpfs support, is mounted prior to being started. /dev/shm should be mounted automatically by OpenRC and systemd during boot, but can also be mounted explicitly via /etc/fstab:
The kernel option CONFIG_COMPAT_32BIT_TIME has to be set, otherwise Steam may fail to start with the error message: 'The futex facility returned an unexpected error code.'
Installation
Steam officially supports only the most recent version of Ubuntu LTS. Attempting to run Steam on any other Linux distribution may cause various issues. Refer to client and games troubleshooting for details.
The Steam installer downloads and installs the Steam client to the users home directory. This prevents Portage from managing the Steam client updates or the software installed by it. Hearthstone blizzard shop. The Steam client is solely responsible for managing software installation and updates.
The instructions throughout this page use the typical Steam installation directory ~/.local/share/Steam.
External repositories
The steam-launcher ebuild is available from the steam-overlay repository, which is Gentoo's primary repository for the Steam client and Steam-based games. The steam-overlay repository can be added manually or with repository management tools eselect-repository and layman.
Adding the repository manually
Install the required dependencies:
Install the Steam repository configuration:
root #wget -P /etc/portage/repos.conf/ https://raw.githubusercontent.com/anyc/steam-overlay/master/steam-overlay.confSync the Steam repository:
The above only needs to be performed once, since the repository will be auto synced during emerge --sync or emaint sync --auto operations.
eselect-repository
Install app-eselect/eselect-repository and dev-vcs/git:
root #emerge --ask --noreplace app-eselect/eselect-repository dev-vcs/gitAdd the Steam repository:
Layman
Please refer to the Layman page for comprehensive installation instructions.
Install Layman:
Fetch the Steam repository:
Display the information about the specified repository:
Add the Steam repository:
Emerge
Thanks to the Proton runtime built into Steam, 32-bit binaries of most dependencies are included within the Steam installation. Some system dependencies remain however, but Portage should prompt for them. These packages should be added to /etc/portage/package.use/steam with their
abi_x86_32 USE flag enabled.Once the repository has been added install the steam-launcher ebuild:
Alternatively, install the steam-meta ebuild to pull in all Steam related ebuilds:
Manual
Installing Steam manually is not recommend as various fixes are not applied automatically[2]. Please consider installing Steam from an external repository.
Dependencies
The following dependencies may be outdated and require verification. Some of the dependencies may be bundled by the Steam runtime, in which case the system libraries will not be used.
Create the following set of required Steam dependencies:
And then run:
Do not run emerge --unmerge @steam to remove Steam as it may make the system unusable. Instead use emerge --ask --depclean @steam for this method.
USE flags
To enable the required USE flags for Steam dependencies under amd64, add the the following file:
Update the system:
Users may receive an error citing circular dependencies due to gpm and ncurses. If this is the case, add
-gpm to sys-libs/ncurses and update the @world set once more.Default installer
Fetch and extract the Steam installer:
user $wget https://repo.steampowered.com/steam/pool/steam/s/steam/steam_1.0.0.66.tar.gzRun the Steam installer:
user $./steamAfter invoking ./steam a libGL error may appear. See Steam/Client troubleshooting for the resolution.
If the Steam client crashes, try running:
Running Steam with the -textclient option may be necessary each time the client wants to update.
Install the above Steam installer script:
Steam can be started with:
Alternative installer
The following installation method is almost identical to the Default installer installation method, except that an alternative Steam installer script is used.
Fetch the Steam installer and extract the required files:
user $wget https://repo.steampowered.com/steam/pool/steam/s/steam/steam_1.0.0.66.tar.gzuser $tar -xvzf steam_1.0.0.66.tar.gz steam/bootstraplinux_ubuntu12_32.tar.xzuser $tar -xvzf steam_1.0.0.66.tar.gz steam/steam.desktopFetch and run Julian Ospald's (hasufell) Steam installer script:
user $wget https://gist.githubusercontent.com/hasufell/d02a93eccbe35be7a803/raw/987ea287dc81a60d2eb5fa1bb188eae0a5f1049f/steamuser $./steamIf the installer script creates broken symbolic links when run with Dash, run the installer script with Bash instead:
Civ 5 64 Bit Steam
Chroot
Steam can be run in a 64-bit multilibchroot on amd64. The major advantage of a chroot is that Steam and its dependencies will be isolated from the root filesystem.
The Steam browser is no longer supported on 32-bit Linux distributions, and is disabled when viewing the Store, Community, or User Profile tabs in the Steam client[3]. Although Steam can be be run in a 32-bit chroot, it is recommend (and necessary for 64-bit games) to use a 64-bit multilib chroot.
Create the chroot directory. If a 32-bit chroot is used, adjust the chroot directory accordingly.
root #cd /usr/local/steam64Fetch and extract the stage3 tarball. If a 32-bit chroot is used, download the x86 stage3 tarball instead.
root #wget http://distfiles.gentoo.org/releases/amd64/autobuilds/current-stage3-amd64/stage3-amd64-20191002T214502Z.tar.xzroot #tar xpvf stage3*.tar.xz --xattrs-include='*.*' --numeric-ownerCopy DNS information and ensure it's world-readable:
root #chmod a+r etc/resolv.confCreate the ebuild repository directory:
/var/db/repos/gentoo is used as the location for the main ebuild repository. This has been the default for new installations since sys-apps/portage 2.3.64[4]. If this is an old installation or migration to the new location has not taken place, then use the legacy location /usr/portage accordingly. Please be aware that all recent stage tarballs also use the new location.
Mount the necessary filesystems:
root #mount -R /sys sysroot #mount -R /run runroot #mount -R /var/db/repos/gentoo var/db/repos/gentooChroot with linux64 and update the environment. If a 32-bit chroot is used, chroot with linux32 instead. The use of linux64 is not required on amd64, and it is only used here for consistency.
root #env-update && source /etc/profileThe chroot should now be updated and configured accordingly. It is recommended to at least configure the timezone and enable sound support by installing media-libs/alsa-lib.
Now create the Steam user with the same UID (usually 1000) as the local user. The local UID can be determined by running id -u as the local user, outside of the chroot. Using the same UID will simplify the process of granting access to the X server from inside the chroot.
(chroot) root #useradd -u -m -G audio,video steamInstall Steam from one of the above installation methods. When complete, exit the chroot:
Unmount the chroot directories:
root #umount -l sysroot #umount -l runInstall xhost to allow access to the X server from inside the chroot:
Logout, and then login. This allows the display manager or xinit to process /etc/X11/xinit/xinitrc.d/00-xhost and automatically grant all local connections to the X server from the local UID. This will not work if the Steam UID is different to that of the local UID. Either set the same UID when creating the Steam user, as was mentioned earlier, or if the Steam user already exists change the Steam UID with usermod -u steam to match the local UID.
Alternatively, run xhost +local: to allow all local connections to the X server from any local UID. This is a potential security risk as any user could access the X server without authentication. To revoke access run xhost -local:
Next, create the following wrapper script to setup the chroot, substitute to the Steam user, and start Steam. The wrapper script has two user defined variables: chroot_bits and chroot_dir. The chroot_bits variable must be set to 32 for a 32-bit chroot, and 64 for a 64-bit chroot. The chroot_dir variable should be set to the location of the chroot directory.
/usr/local/bin/steam-chrootThe wrapper script bind mounts /run so Steam can connect to D-Bus if it is running on the host. Steam will work even if D-Bus is not installed, but there will be non-fatal errors relating to Steam's bundled dev-libs/libappindicator. Steam also needs D-Bus if the Remember my password option is selected at the Steam login dialog. Refer to client troubleshooting for further details.
Make the wrapper script executable:
Run the wrapper script as root to start Steam:
Flatpak
A quite simple, fast and clean method (e.g. 32-bit dependencies do not need to be compiled) of installing Steam is to use the Flatpak package com.valvesoftware.Steam from Flathub:
user $flatpak install flathub com.valvesoftware.SteamSteam will update itself and install its files in the ~/.var/app/com.valvesoftware.Steam directory.
Client troubleshooting
See Steam/Client troubleshooting.
Games troubleshooting
The above only needs to be performed once, since the repository will be auto synced during emerge --sync or emaint sync --auto operations.
eselect-repository
Install app-eselect/eselect-repository and dev-vcs/git:
root #emerge --ask --noreplace app-eselect/eselect-repository dev-vcs/gitAdd the Steam repository:
Layman
Please refer to the Layman page for comprehensive installation instructions.
Install Layman:
Fetch the Steam repository:
Display the information about the specified repository:
Add the Steam repository:
Emerge
Thanks to the Proton runtime built into Steam, 32-bit binaries of most dependencies are included within the Steam installation. Some system dependencies remain however, but Portage should prompt for them. These packages should be added to /etc/portage/package.use/steam with their
abi_x86_32 USE flag enabled.Once the repository has been added install the steam-launcher ebuild:
Alternatively, install the steam-meta ebuild to pull in all Steam related ebuilds:
Manual
Installing Steam manually is not recommend as various fixes are not applied automatically[2]. Please consider installing Steam from an external repository.
Dependencies
The following dependencies may be outdated and require verification. Some of the dependencies may be bundled by the Steam runtime, in which case the system libraries will not be used.
Create the following set of required Steam dependencies:
And then run:
Do not run emerge --unmerge @steam to remove Steam as it may make the system unusable. Instead use emerge --ask --depclean @steam for this method.
USE flags
To enable the required USE flags for Steam dependencies under amd64, add the the following file:
Update the system:
Users may receive an error citing circular dependencies due to gpm and ncurses. If this is the case, add
-gpm to sys-libs/ncurses and update the @world set once more.Default installer
Fetch and extract the Steam installer:
user $wget https://repo.steampowered.com/steam/pool/steam/s/steam/steam_1.0.0.66.tar.gzRun the Steam installer:
user $./steamAfter invoking ./steam a libGL error may appear. See Steam/Client troubleshooting for the resolution.
If the Steam client crashes, try running:
Running Steam with the -textclient option may be necessary each time the client wants to update.
Install the above Steam installer script:
Steam can be started with:
Alternative installer
The following installation method is almost identical to the Default installer installation method, except that an alternative Steam installer script is used.
Fetch the Steam installer and extract the required files:
user $wget https://repo.steampowered.com/steam/pool/steam/s/steam/steam_1.0.0.66.tar.gzuser $tar -xvzf steam_1.0.0.66.tar.gz steam/bootstraplinux_ubuntu12_32.tar.xzuser $tar -xvzf steam_1.0.0.66.tar.gz steam/steam.desktopFetch and run Julian Ospald's (hasufell) Steam installer script:
user $wget https://gist.githubusercontent.com/hasufell/d02a93eccbe35be7a803/raw/987ea287dc81a60d2eb5fa1bb188eae0a5f1049f/steamuser $./steamIf the installer script creates broken symbolic links when run with Dash, run the installer script with Bash instead:
Civ 5 64 Bit Steam
Chroot
Steam can be run in a 64-bit multilibchroot on amd64. The major advantage of a chroot is that Steam and its dependencies will be isolated from the root filesystem.
The Steam browser is no longer supported on 32-bit Linux distributions, and is disabled when viewing the Store, Community, or User Profile tabs in the Steam client[3]. Although Steam can be be run in a 32-bit chroot, it is recommend (and necessary for 64-bit games) to use a 64-bit multilib chroot.
Create the chroot directory. If a 32-bit chroot is used, adjust the chroot directory accordingly.
root #cd /usr/local/steam64Fetch and extract the stage3 tarball. If a 32-bit chroot is used, download the x86 stage3 tarball instead.
root #wget http://distfiles.gentoo.org/releases/amd64/autobuilds/current-stage3-amd64/stage3-amd64-20191002T214502Z.tar.xzroot #tar xpvf stage3*.tar.xz --xattrs-include='*.*' --numeric-ownerCopy DNS information and ensure it's world-readable:
root #chmod a+r etc/resolv.confCreate the ebuild repository directory:
/var/db/repos/gentoo is used as the location for the main ebuild repository. This has been the default for new installations since sys-apps/portage 2.3.64[4]. If this is an old installation or migration to the new location has not taken place, then use the legacy location /usr/portage accordingly. Please be aware that all recent stage tarballs also use the new location.
Mount the necessary filesystems:
root #mount -R /sys sysroot #mount -R /run runroot #mount -R /var/db/repos/gentoo var/db/repos/gentooChroot with linux64 and update the environment. If a 32-bit chroot is used, chroot with linux32 instead. The use of linux64 is not required on amd64, and it is only used here for consistency.
root #env-update && source /etc/profileThe chroot should now be updated and configured accordingly. It is recommended to at least configure the timezone and enable sound support by installing media-libs/alsa-lib.
Now create the Steam user with the same UID (usually 1000) as the local user. The local UID can be determined by running id -u as the local user, outside of the chroot. Using the same UID will simplify the process of granting access to the X server from inside the chroot.
(chroot) root #useradd -u -m -G audio,video steamInstall Steam from one of the above installation methods. When complete, exit the chroot:
Unmount the chroot directories:
root #umount -l sysroot #umount -l runInstall xhost to allow access to the X server from inside the chroot:
Logout, and then login. This allows the display manager or xinit to process /etc/X11/xinit/xinitrc.d/00-xhost and automatically grant all local connections to the X server from the local UID. This will not work if the Steam UID is different to that of the local UID. Either set the same UID when creating the Steam user, as was mentioned earlier, or if the Steam user already exists change the Steam UID with usermod -u steam to match the local UID.
Alternatively, run xhost +local: to allow all local connections to the X server from any local UID. This is a potential security risk as any user could access the X server without authentication. To revoke access run xhost -local:
Next, create the following wrapper script to setup the chroot, substitute to the Steam user, and start Steam. The wrapper script has two user defined variables: chroot_bits and chroot_dir. The chroot_bits variable must be set to 32 for a 32-bit chroot, and 64 for a 64-bit chroot. The chroot_dir variable should be set to the location of the chroot directory.
/usr/local/bin/steam-chrootThe wrapper script bind mounts /run so Steam can connect to D-Bus if it is running on the host. Steam will work even if D-Bus is not installed, but there will be non-fatal errors relating to Steam's bundled dev-libs/libappindicator. Steam also needs D-Bus if the Remember my password option is selected at the Steam login dialog. Refer to client troubleshooting for further details.
Make the wrapper script executable:
Run the wrapper script as root to start Steam:
Flatpak
A quite simple, fast and clean method (e.g. 32-bit dependencies do not need to be compiled) of installing Steam is to use the Flatpak package com.valvesoftware.Steam from Flathub:
user $flatpak install flathub com.valvesoftware.SteamSteam will update itself and install its files in the ~/.var/app/com.valvesoftware.Steam directory.
Client troubleshooting
See Steam/Client troubleshooting.
Games troubleshooting
See Steam/Games troubleshooting.
Removal
Removing a manual installation
Remove the Steam dependencies:
Remove the Steam executable and Portage configuration: Playstation network number.
root #rm /etc/portage/sets/steamRemove the Steam directory from the user accountː
Remove all files and directories from the user account which contain 'steam' (case-insensitive) in the name:
Use with caution as this may remove files and directories unrelated to Steam.
Removing an external repository installation
Remove the steam-launcher ebuild:
root #emerge --ask --depclean --verbose games-util/steam-launcherIf it was installed, remove the steam-meta ebuild:
root #emerge --ask --depclean --verbose games-util/steam-metaAsking for help
The best place to ask for help is the Steam thread on the Gentoo Forums. If a solution to an issue is confirmed by others, add it to this page or the relevant troubleshooting subpage. Please do not remove content without discussion, unless it is obviously wrong.
See also
- Games — a landing page for many of the games (especially open source variants) available in Gentoo's main ebuild repository.
- Steam Controller — a game controller developed by Valve.
Civ 5 64 Bit Steam Download
External resources
Civ 5 64 Bit Steam Apk
References
- ↑https://steamcommunity.com/games/221410/announcements/detail/1696055855739350561
- ↑chewi. Issues on 4.18.9-gentoo kernel, Steam for Linux, September 24th, 2018. Retrieved on September 25th, 2018.
- ↑Valve. The Steam Browser is Disabled, Steam Support Knowledge Base, December 12th, 2016. Retrieved on January 12th, 2019.
- ↑Zac Medico. Portage 2.3.64 News, Portage Git repository, April 18th, 2019. Retrieved on September 29th, 2019.
