You are not logged in.

#1 2022-04-30 12:28:32

Artlav
Member
Registered: 2016-07-11
Posts: 36
Website

[SOLVED] Recent libseccomp update killed Steam Proton

Not sure if it should go into bug reports or what, but i want to document it in case someone is trying to google it.

After a routine update all games on Steam started to run extremely slowly or fail to launch at all.

Downgrading all of it fixed things, and after much back and forth i narrowed it down to libseccomp-2.5.3-3 updating to libseccomp-2.5.4-1

With older one everything runs fine, with newer one all Steam games consume 100% CPU and either fail to launch or run as if the CPU is 100 times slower than it should be.

At the same time non-steam games and similar programs run just fine.

Another note is that Proton 6 seem to work fine (at it's usual slowness),  while Proton 7 and experimental are the ones affected.

Relevant packages:

intel-compute-runtime 22.16.22992-1
intel-media-driver 22.3.1-1
lib32-libva 2.13.0-1
lib32-libva-intel-driver 2.4.1-1
lib32-libvdpau 1.4-2
lib32-vulkan-icd-loader 1.3.208-1
lib32-vulkan-intel 22.0.2-1
lib32-vulkan-validation-layers 1.3.204.1-1
libva 2.14.0-1
libva-utils 2.14.0-1
libvdpau 1.5-1
mesa 22.0.2-1
steam 1.0.0.74-1
steam-native-runtime 1.0.0.70-3
vulkan-headers 1:1.3.211-1
vulkan-icd-loader 1.3.208-1
vulkan-intel 22.0.2-1
xf86-video-intel 1:2.99.917+916+g31486f40-2

CPU is i7-1195G7 with Iris Xe Graphics integrated GPU, in case that is relevant.

Last edited by Artlav (2023-05-14 14:23:43)

Offline

#2 2022-07-11 20:07:00

Artlav
Member
Registered: 2016-07-11
Posts: 36
Website

Re: [SOLVED] Recent libseccomp update killed Steam Proton

It is getting annoying to downgrade it all the time.
Is there some workaround or config update i'm missing?

Offline

#3 2022-07-12 11:34:49

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,919

Re: [SOLVED] Recent libseccomp update killed Steam Proton

CPU is i7-1195G7 with Iris Xe Graphics integrated GPU

xf86-video-intel 1:2.99.917+916+g31486f40-2

Your processor with that iGPU was released in Q2 2021 .
xf86-video-intel worked well for iGPU of 10+ years ago.

libva-intel-driver doesn't support anything newer then coffee lake (2017) .

vdpau is not supported on intel gpus at all.


I don't know if the libseccomp update is related to your issue or merely a symptom, but your graphics setup has serious flaws.
fix them first.

Are you using Xorg or wayland ?
Which WM / DE ?
How are you starting the graphics environment ?

Please post lspci -k output (run as user)

Last edited by Lone_Wolf (2022-07-12 11:35:11)


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#4 2022-07-15 11:03:16

Artlav
Member
Registered: 2016-07-11
Posts: 36
Website

Re: [SOLVED] Recent libseccomp update killed Steam Proton

Lone_Wolf wrote:

xf86-video-intel 1:2.99.917+916+g31486f40-2

Your processor with that iGPU was released in Q2 2021 .
xf86-video-intel worked well for iGPU of 10+ years ago.

Hm, i looked through the intel video driver arch page and am not really sure what there is to change.
Apparently it's still supposed to be installed for managing things.

Lone_Wolf wrote:

libva-intel-driver doesn't support anything newer then coffee lake (2017) .

That might be a remnant from trying to get Steam remote play streaming to run with hw acceleration, removing it changed nothing.

Lone_Wolf wrote:

vdpau is not supported on intel gpus at all.

It appears to be a Steam dependency, won't uninstall without taking Steam with it.

Lone_Wolf wrote:

I don't know if the libseccomp update is related to your issue or merely a symptom, but your graphics setup has serious flaws.
fix them first.

Well, it works fine otherwise.

Lone_Wolf wrote:

Are you using Xorg or wayland ?
Which WM / DE ?
How are you starting the graphics environment ?

Xorg, XFCE, via .bash_profile:

if [ -z "$DISPLAY" ] && [ -n "$XDG_VTNR" ] && [ "$XDG_VTNR" -eq 1 ]; then
  exec startx >/tmp/xlog.txt 2>&1
fi
Lone_Wolf wrote:

Please post lspci -k output (run as user)

00:00.0 Host bridge: Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers (rev 02)
	DeviceName: Onboard - Other
	Kernel modules: igen6_edac
00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 03)
	DeviceName: Onboard - Video
	Kernel driver in use: i915
	Kernel modules: i915
00:04.0 Signal processing controller: Intel Corporation TigerLake-LP Dynamic Tuning Processor Participant (rev 02)
	DeviceName: Onboard - Other
	Kernel driver in use: proc_thermal
	Kernel modules: processor_thermal_device_pci_legacy
00:06.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller (rev 02)
	Kernel driver in use: pcieport
00:07.0 PCI bridge: Intel Corporation Tiger Lake-LP Thunderbolt 4 PCI Express Root Port #0 (rev 02)
	Kernel driver in use: pcieport
00:07.1 PCI bridge: Intel Corporation Tiger Lake-LP Thunderbolt 4 PCI Express Root Port #1 (rev 02)
	Kernel driver in use: pcieport
00:07.2 PCI bridge: Intel Corporation Tiger Lake-LP Thunderbolt 4 PCI Express Root Port #2 (rev 02)
	Kernel driver in use: pcieport
00:07.3 PCI bridge: Intel Corporation Tiger Lake-LP Thunderbolt 4 PCI Express Root Port #3 (rev 02)
	Kernel driver in use: pcieport
00:08.0 System peripheral: Intel Corporation GNA Scoring Accelerator module (rev 02)
	DeviceName: Onboard - Other
00:0a.0 Signal processing controller: Intel Corporation Tigerlake Telemetry Aggregator Driver (rev 01)
	DeviceName: Onboard - Other
	Kernel driver in use: intel_vsec
	Kernel modules: intel_vsec
00:0d.0 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt 4 USB Controller (rev 02)
	DeviceName: Onboard - Other
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci
00:0d.2 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt 4 NHI #0 (rev 02)
	DeviceName: Onboard - Other
	Subsystem: Device 2222:1111
	Kernel driver in use: thunderbolt
	Kernel modules: thunderbolt
00:0d.3 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt 4 NHI #1 (rev 02)
	DeviceName: Onboard - Other
	Subsystem: Device 2222:1111
	Kernel driver in use: thunderbolt
	Kernel modules: thunderbolt
00:14.0 USB controller: Intel Corporation Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller (rev 30)
	DeviceName: Onboard - Other
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci
00:14.2 RAM memory: Intel Corporation Tiger Lake-LP Shared SRAM (rev 30)
	DeviceName: Onboard - Other
00:15.0 Serial bus controller: Intel Corporation Tiger Lake-LP Serial IO I2C Controller #0 (rev 30)
	DeviceName: Onboard - Other
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci
00:15.1 Serial bus controller: Intel Corporation Tiger Lake-LP Serial IO I2C Controller #1 (rev 30)
	DeviceName: Onboard - Other
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci
00:16.0 Communication controller: Intel Corporation Tiger Lake-LP Management Engine Interface (rev 30)
	DeviceName: Onboard - Other
	Kernel driver in use: mei_me
	Kernel modules: mei_me
00:1c.0 PCI bridge: Intel Corporation Device a0ba (rev 30)
	Kernel driver in use: pcieport
00:1c.6 PCI bridge: Intel Corporation Device a0be (rev 30)
	Kernel driver in use: pcieport
00:1e.0 Communication controller: Intel Corporation Tiger Lake-LP Serial IO UART Controller #0 (rev 30)
	DeviceName: Onboard - Other
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci
00:1e.3 Serial bus controller: Intel Corporation Tiger Lake-LP Serial IO SPI Controller #1 (rev 30)
	DeviceName: Onboard - Other
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci
00:1f.0 ISA bridge: Intel Corporation Tiger Lake-LP LPC Controller (rev 30)
	DeviceName: Onboard - Other
00:1f.3 Multimedia audio controller: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller (rev 30)
	DeviceName: Onboard - Sound
	Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Device 0000
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl
00:1f.4 SMBus: Intel Corporation Tiger Lake-LP SMBus Controller (rev 30)
	DeviceName: Onboard - Other
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801
00:1f.5 Serial bus controller: Intel Corporation Tiger Lake-LP SPI Controller (rev 30)
	DeviceName: Onboard - Other
	Kernel driver in use: intel-spi
	Kernel modules: spi_intel_pci
01:00.0 Non-Volatile memory controller: Biwin Storage Technology Co., Ltd. Device 2263 (rev 03)
	Subsystem: Biwin Storage Technology Co., Ltd. Device 2263
	Kernel driver in use: nvme
	Kernel modules: nvme
ae:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a)
	Subsystem: Intel Corporation Wi-Fi 6 AX210 160MHz
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi
af:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
	Subsystem: Realtek Semiconductor Co., Ltd. Device 0123
	Kernel driver in use: r8169
	Kernel modules: r8169

Offline

#5 2022-07-20 10:40:53

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,919

Re: [SOLVED] Recent libseccomp update killed Steam Proton

lspci and the way you start X work look fine.

Artlav wrote:
Lone_Wolf wrote:

vdpau is not supported on intel gpus at all.

It appears to be a Steam dependency, won't uninstall without taking Steam with it.

$ pactree --reverse --sync --depth=1 libvdpau
libvdpau
├─avidemux-cli
├─ffmpeg
├─ffmpeg4.4
├─kodi
├─lib32-libvdpau
├─libva-vdpau-driver
├─libvdpau-va-gl
├─mplayer
├─mpv
├─nvidia-settings
├─steam-native-runtime
└─vdpauinfo
$

I misjudged how many things have a hard dependency on libvdpau. Although it's uselss on your system it's much easier to keep it.


Artlav wrote:
Lone_Wolf wrote:

xf86-video-intel 1:2.99.917+916+g31486f40-2

Your processor with that iGPU was released in Q2 2021 .
xf86-video-intel worked well for iGPU of 10+ years ago.

Hm, i looked through the intel video driver arch page and am not really sure what there is to change.
Apparently it's still supposed to be installed for managing things.

xf86-video-intel is so often the cause of graphics problems on intel processors younger then 2006 that removing it to verify whether it's involved has become the most recommended action.

There are however some very rare situations where xf86-video-intel is needed on modern intel graphics.

I suggest you remove it and check whether that solves/reduces the issue.
NOTE:
Check your static *.conf files before removing, there may be a few that force X to use xf86-video-intel and need to be removed also.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#6 2022-12-16 21:40:44

Artlav
Member
Registered: 2016-07-11
Posts: 36
Website

Re: [SOLVED] Recent libseccomp update killed Steam Proton

The problem is still there, and is still reliably solvable by downgrading to libseccomp-2.5.3-3-x86_64.pkg.tar.zst
Nothing else have been able to cause it with older libseccomp.
Nothing else have been able to solve it with newer libseccomp.

Offline

#7 2022-12-20 11:56:49

Artlav
Member
Registered: 2016-07-11
Posts: 36
Website

Re: [SOLVED] Recent libseccomp update killed Steam Proton

Another thing i noticed is that it's not just games - regular Steam activity like opening it up and doing stuff in it also cause 100% CPU load on all cores with new libseccomp. It feels only a little more laggy, so i never noticed before.

Offline

#8 2023-04-29 17:49:28

Artlav
Member
Registered: 2016-07-11
Posts: 36
Website

Re: [SOLVED] Recent libseccomp update killed Steam Proton

As of libseccomp 2.5.4-2 the problem have disappeared.
Everything works fine now without the need to downgrade it.

Offline

#9 2023-04-29 20:06:52

seth
Member
Registered: 2012-09-03
Posts: 51,148

Re: [SOLVED] Recent libseccomp update killed Steam Proton

\o/

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Offline

Board footer

Powered by FluxBB