protonscr

System Info Report Generation Has Failing Sub-processes

steamopen
ValveSoftware/steam-for-linux#8651 · opened 2022-06-25 by ThisNekoGuy · updated 2022-06-25 · 2 comments · github
TThisNekoGuy 2022-06-25 github

Your system information

  • Steam client version (build number or date):
  • Distribution (e.g. Ubuntu): Arch Linux
  • Opted into Steam client beta?: No
  • Have you checked for system updates?: Yes
  • Filesystem: BTRFS
  • Desktop Environment: KDE Plasma (version 5.25.1)
  • Steam System Information: gist

Please describe your issue in as much detail as possible:

Attempting to generate system info reports from the Steam Client can supposedly cause at least some of the report's sub-processes to fail/crash silently; I only found out about this due to having a certain environment variable enabled alongside some related systemd services to notify of application crashes.

Example screenshot:
Screenshot_20220624_195342

This might impact the accuracy of system info outputs, so I figured this would probably be something important to report.

Steps for reproducing this issue:

  1. Run a KDE Desktop system with drkonqi installed (run sudo pacman -Syu drkonqi if it isn't already installed)
  2. Edit /etc/environment and add: export KDE_COREDUMP_NOTIFY=1
  3. sudo systemctl enable [email protected]
  4. Reboot
  5. Login to Steam
  6. Attempt to generate a system info report
Kkisak-valve maintainer 2022-06-25 github

Hello @ThisNekoGuy, the extended diagnostics section of Steam's system information is fairly through in exercising various common render paths. It looks like what you're highlighting is a general lack of support for VA-API with NVIDIA's proprietary driver and that isn't particularly concerning since the VDPAU render paths read as healthy. Those failures are not a real issue.

The only real thing to ponder here is https://gist.github.com/ThisNekoGuy/0fc4aef8635c77f63a2a3e25ad2fabfb#file-system-info_june-24-2022-log-L1048, and that's non-essential as well.

TThisNekoGuy 2022-06-25 github

Also noticed around where you mentioned that the steam uri handler seems to be missing (a little further down), but thanks for letting me know about the other things; I wasn't exactly aware of the depth of the issue.

Nothing extracted yet.