Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#66645 - steam and steam-native-runtime 1.0.0.62-1 pull vulkan-driver

Attached to Project: Community Packages
Opened by Luca Bortolotti (optiluca) - Thursday, 14 May 2020, 12:58 GMT
Last edited by Levente Polyak (anthraxx) - Saturday, 23 May 2020, 19:15 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Levente Polyak (anthraxx)
Giancarlo Razzolini (grazzolini)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

As of version 1.0.0.62-1, steam and steam-native-runtime depend on vulkan-driver and lib32-vulkan-driver. Some cards (e.g. cards requiring nvidia-340xx drivers in my case) don't support vulkan, so on these systems steam can't be updated. Presumably the dependency is at the very least optional, since up to the previous version steam worked just fine without having vulkan installed?
This task depends upon

Closed by  Levente Polyak (anthraxx)
Saturday, 23 May 2020, 19:15 GMT
Reason for closing:  Won't fix
Additional comments about closing:  hard dependency of core components (proton) which valve considers a crucial dependency. any way this is being worked around by users is considered an unsupported state unfortunately.
Comment by Jonny Robbie (JonnyRobbie) - Saturday, 23 May 2020, 11:10 GMT
I can confirm the same thing. This added dependency "vulkan-driver" (and lib32) breaks compatibility with "nvidia-340xx-dkms", since 340 drivers do not support vulkan. Please check if vulkan drivers are truly necessary for steam since it worked fine with 1.0.0.61 version without vulkan.

$ sudo pacman -Syu
...

resolving dependencies...
:: There are 4 providers available for vulkan-driver:
:: Repository extra
1) amdvlk 2) nvidia-utils 3) vulkan-intel 4) vulkan-radeon

Enter a number (default=1): 2
:: There are 4 providers available for lib32-vulkan-driver:
:: Repository multilib
1) lib32-amdvlk 2) lib32-nvidia-utils 3) lib32-vulkan-intel 4) lib32-vulkan-radeon

Enter a number (default=1): 2
looking for conflicting packages...
:: nvidia-utils and nvidia-340xx-utils are in conflict (nvidia-libgl). Remove nvidia-340xx-utils? [y/N] y
:: lib32-nvidia-utils and lib32-nvidia-340xx-utils are in conflict. Remove lib32-nvidia-340xx-utils? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: removing nvidia-340xx-utils breaks dependency 'nvidia-340xx-utils=340.107' required by nvidia-340xx-dkms
Comment by Levente Polyak (anthraxx) - Saturday, 23 May 2020, 14:36 GMT
core components of steam now require vulkan, like the proton runtime. if you want that unsupported driver to satisfy the dependency you will need to implement like a dummy package that provides it, however note that doing so is not supported as it marks vulkan-driver as available while its not.
Comment by Jonny Robbie (JonnyRobbie) - Saturday, 23 May 2020, 19:11 GMT
In that vein, I could get this steam with abs and edit out the deps in PKGBUILD to be slightly cleaner, right? Is vulkan a "hard" dependency (it will crash/will not load) or is is more of a "soft" dependency (it might crash if trying to access certain features)?
Comment by Levente Polyak (anthraxx) - Saturday, 23 May 2020, 19:13 GMT
the whole proton runtime just does not work, and its considered a core component. according to valve it should be indeed a hard requirement to reflect this essential part. Sure, you can also do that, but that is also an unsupported state whenever something will break :)

Loading...