Problems installing steam [Solved]

[fresh_orange_00]

Code: Select all

System:
  Host: <filter> Kernel: 5.10.0-9-amd64 x86_64 bits: 64 compiler: N/A 
  parameters: BOOT_IMAGE=/vmlinuz-5.10.0-9-amd64 
  root=UUID=<filter> ro quiet splash 
  Desktop: KDE Plasma 5.20.5 wm: kwin_x11 dm: SDDM 
  Distro: MX-21_KDE_x64 Wildflower October 20  2021 
  base: Debian GNU/Linux 11 (bullseye) 
Machine:
  Type: Laptop System: LENOVO product: 20K6S0L400 v: ThinkPad X270 W10DG 
  serial: <filter> Chassis: type: 10 serial: <filter> 
  Mobo: LENOVO model: 20K6S0L400 serial: <filter> UEFI: LENOVO 
  v: R0IET58W (1.36 ) date: 04/19/2019 
Battery:
  ID-1: BAT0 charge: 18.6 Wh condition: 18.6/23.2 Wh (80%) 
  volts: 12.4/11.1 model: SANYO 45N1773 type: Li-ion serial: <filter> 
  status: Full cycles: 27 
  ID-2: BAT1 charge: 19.7 Wh condition: 19.7/23.2 Wh (85%) 
  volts: 12.4/11.1 model: SANYO 45N1775 type: Li-ion serial: <filter> 
  status: Full cycles: 56 
CPU:
  Topology: Dual Core model: Intel Core i5-6200U bits: 64 type: MT MCP 
  arch: Skylake family: 6 model-id: 4E (78) stepping: 3 microcode: EA 
  L2 cache: 3072 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 19200 
  Speed: 800 MHz min/max: 400/2800 MHz Core speeds (MHz): 1: 800 2: 800 
  3: 800 4: 800 
  Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, 
  SMT vulnerable 
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
  Type: meltdown mitigation: PTI 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Full generic retpoline, IBPB: 
  conditional, IBRS_FW, STIBP: conditional, RSB filling 
  Type: srbds mitigation: Microcode 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: Intel Skylake GT2 [HD Graphics 520] vendor: Lenovo 
  driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:1916 
  Display: x11 server: X.Org 1.20.13 driver: modesetting 
  unloaded: fbdev,vesa compositor: kwin_x11 resolution: 1366x768~60Hz 
  OpenGL: renderer: Mesa Intel HD Graphics 520 (SKL GT2) 
  v: 4.6 Mesa 21.2.5 direct render: Yes 
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo 
  driver: snd_hda_intel v: kernel bus ID: 00:1f.3 chip ID: 8086:9d70 
  Sound Server: ALSA v: k5.10.0-9-amd64 
Network:
  Device-1: Intel Ethernet I219-V vendor: Lenovo driver: e1000e 
  v: kernel port: efa0 bus ID: 00:1f.6 chip ID: 8086:1570 
  IF: eth0 state: down mac: <filter> 
  Device-2: Intel Wireless 8260 driver: iwlwifi v: kernel port: efa0 
  bus ID: 03:00.0 chip ID: 8086:24f3 
  IF: wlan0 state: up mac: <filter> 
Drives:
  Local Storage: total: 931.51 GiB used: 588.56 GiB (63.2%) 
  ID-1: /dev/sda vendor: Western Digital model: WD10SPZX-22Z10T0 
  size: 931.51 GiB block size: physical: 4096 B logical: 512 B 
  speed: 6.0 Gb/s rotation: 5400 rpm serial: <filter> rev: 1A01 
  temp: 43 C scheme: GPT 
Partition:
  ID-1: / raw size: 45.22 GiB size: 44.21 GiB (97.76%) 
  used: 8.89 GiB (20.1%) fs: ext4 dev: /dev/sda2 
  ID-2: /boot raw size: 2.00 GiB size: 1.90 GiB (94.92%) 
  used: 102.2 MiB (5.3%) fs: ext4 dev: /dev/sda8 
  ID-3: /home raw size: 19.53 GiB size: 19.06 GiB (97.57%) 
  used: 12.10 GiB (63.5%) fs: ext4 dev: /dev/sda3 
Sensors:
  System Temperatures: cpu: 59.0 C mobo: N/A 
  Fan Speeds (RPM): cpu: 4459 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
  1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian.list 
  1: deb http://deb.debian.org/debian bullseye main contrib non-free
  2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
  No active apt repos in: /etc/apt/sources.list.d/lutris-team-ubuntu-lutris-jammy.list 
  Active apt repos in: /etc/apt/sources.list.d/mx.list 
  1: deb https://espejito.fder.edu.uy/mxlinux/packages/mx/repo/ bullseye main non-free
  2: deb https://espejito.fder.edu.uy/mxlinux/packages/mx/repo/ bullseye ahs
Info:
  Processes: 254 Uptime: 6d 23h 24m Memory: 15.53 GiB 
  used: 5.44 GiB (35.0%) Init: SysVinit v: 2.96 runlevel: 5 default: 5 
  Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in 
  running in: quick-system-in inxi: 3.0.36 

Install log:

Code: Select all

$ sudo apt-get install steam --install-recommends
[sudo] password for user: 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  steam-devices xterm zenity zenity-common
Suggested packages:
  nvidia-driver-libs:i386 nvidia-vulkan-icd:i386 xfonts-cyrillic
The following NEW packages will be installed:
  steam:i386 steam-devices xterm zenity zenity-common
0 upgraded, 5 newly installed, 0 to remove and 45 not upgraded.
Need to get 7,126 kB of archives.
After this operation, 15.5 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://deb.debian.org/debian bullseye/non-free i386 steam i386 1.0.0.68-1 [1,575 kB]
Get:2 http://deb.debian.org/debian bullseye/non-free amd64 steam-devices all 1.0.0.68-1 [34.4 kB]
Get:3 http://deb.debian.org/debian bullseye/main amd64 xterm amd64 366-1 [819 kB]
Get:4 http://deb.debian.org/debian bullseye/main amd64 zenity-common all 3.32.0-6 [4,423 kB]
Get:5 http://deb.debian.org/debian bullseye/main amd64 zenity amd64 3.32.0-6 [275 kB]
Fetched 7,126 kB in 1s (6,205 kB/s)
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QCommandLineParser: already having an option named "h"
QCommandLineParser: already having an option named "help-all"
QCommandLineParser: already having an option named "v"
Preconfiguring packages ...
Selecting previously unselected package steam:i386.
(Reading database ... 311296 files and directories currently installed.)
Preparing to unpack .../steam_1.0.0.68-1_i386.deb ...
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QCommandLineParser: already having an option named "h"
QCommandLineParser: already having an option named "help-all"
QCommandLineParser: already having an option named "v"
dpkg: error processing archive /var/cache/apt/archives/steam_1.0.0.68-1_i386.deb (--unpack):
 new steam:i386 package pre-installation script subprocess returned error exit status 1
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QCommandLineParser: already having an option named "h"
QCommandLineParser: already having an option named "help-all"
QCommandLineParser: already having an option named "v"
Installation terminated: Steam License Agreement was DECLINED.
Selecting previously unselected package steam-devices.
Preparing to unpack .../steam-devices_1.0.0.68-1_all.deb ...
Unpacking steam-devices (1.0.0.68-1) ...
Selecting previously unselected package xterm.
Preparing to unpack .../archives/xterm_366-1_amd64.deb ...
Unpacking xterm (366-1) ...
Selecting previously unselected package zenity-common.
Preparing to unpack .../zenity-common_3.32.0-6_all.deb ...
Unpacking zenity-common (3.32.0-6) ...
Selecting previously unselected package zenity.
Preparing to unpack .../zenity_3.32.0-6_amd64.deb ...
Unpacking zenity (3.32.0-6) ...
Errors were encountered while processing:
 /var/cache/apt/archives/steam_1.0.0.68-1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

[j2mcgreg]

You likely will have a better experience if you use MXPI to install the Steam Flatpack.

[dolphin_oracle]

next time agree to the steam end-user agreement. you said no at install time.

Installation terminated: Steam License Agreement was DECLINED.

I think you can reset that by doing an apt purge on steam and then reinstalling, paying attention to the question box that will pop up.

Code: Select all

sudo apt purge steam:i386

viewtopic.php?p=593452#p593452

[fresh_orange_00]

next time agree to the steam end-user agreement. you said no at install time.

https://i.postimg.cc/8PYfPD0k/Screensho ... 205719.png

When I click "Continue" the window closes itself

[SwampRabbit]

I know the installer works, I just ran it the other day to do other testing, but on MX-21 Xfce

I see you’re using KDE, you might have to scroll all the way down in that window?

I can test a install on MX KDE later.

[fresh_orange_00]

I see you’re using KDE, you might have to scroll all the way down in that window?

Thank you very much, that was the solution :)

[fresh_orange_00]

You likely will have a better experience if you use MXPI to install the Steam Flatpack.

Why flatpaks instead of repo packages?

[SwampRabbit]

You likely will have a better experience if you use MXPI to install the Steam Flatpack.

Why flatpaks instead of repo packages?

Just use the package from the repo, you'll have less issues with it because of library dependencies. Steam games can use either the Steam provided or system provided libraries. This is partially dependent upon each individual game.

I don't the flatpak for this exact reason, plus in the past there have been issues with the sandbox isolation and accessing games if they are on different storage.
I read not too long ago that the flatpak maintainer actually disabled Vulkan shaders caching because of issues specific to flatpak. Some games and features (certain Proton versions) will not work unless you have a specific version of flatpak itself, then you have to wait for the Steam flatpak to get updated. There are some issues with game controllers too, but not all. Plus I assume the flatpak is huge in install size.

Also you'll get better help and updates if you use the native client.

Note: This is a community package of Steam gaming plaform not officially supported by Valve.

https://flathub.org/apps/details/com.va ... ware.Steam
Note they even have a typo in that "platform", there are a few other typos on that page too (might not be a big deal but I wouldn't use a community flatpak if they can't spell check)

[j2mcgreg]

You likely will have a better experience if you use MXPI to install the Steam Flatpack.

Why flatpaks instead of repo packages?

Because of the circumstances we are collectively in. Staffing shortages because of Covid 19 restrictions have meant that in the past couple of years not all repositories have been properly maintained. I have found that when I have run into a repository problem, using a flatpack (if available) was an easier out.