Bug 1858437

Summary: /usr/bin/lspci symlink missing, causes Dying Light game not to launch
Product: [Fedora] Fedora Reporter: Tom Crider <tcrider>
Component: pciutilsAssignee: Michal Hlavinka <mhlavink>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 39CC: awilliam, carl, cschalle, gmarr, mhlavink, ngompa13
Target Milestone: ---Keywords: FutureFeature, Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: RejectedFreezeException
Fixed In Version: pciutils-3.10.0-3.fc39 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-11-03 18:31:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Tom Crider 2020-07-18 00:49:39 UTC
Description of problem:

The game 'Dying Light' does not launch from steam, while it works on other distributions. 

Error it shows is:

{18:22:15.406} INFO: [INFO] > [OpenGL] Video memory detected: 0 [MB]!
{18:22:34.979} INFO: [INFO] > Caught signal 2 (Interrupt).

Contact with the game's developer, Techland, stated the following:
--------------
Dying Light uses lspci to detect your video card (at least when running on mesa). Since on most distributions this binary is located in /usr/sbin/, the game cannot find it, reports no video memory and crashes.
Try creating a symlink "ln -s /usr/sbin/lspci /usr/bin/lspci" and start the game, please.

Best Regards
--------------


Version-Release number of selected component (if applicable):

pciutils-3.6.4-1.fc32.x86_64

How reproducible:

Install the native version of the game from steam then attempt to launch it. The logo will show for a second, then the game will crash.


Additional info:

Creating the symlink as instructed in the correspondence e-mail resolves the issue:

$ ln -s /usr/sbin/lspci /usr/bin/lspci

After doing so the game runs perfectly fine.

Comment 1 Michal Hlavinka 2020-07-20 08:35:12 UTC
nothing wrong with pciutils, we don't link binaries to multiple locations, that's what PATH env variable is for
If the game does not work, file a bug against that game, that's the part that needs to be fixed

Comment 2 Christian Fredrik Kalager Schaller 2022-06-28 17:25:14 UTC
Hi Michal,
In principle I agree with you here this is a bug in the application, the problem with old games is that the devs have close to zero commercial interest in doing fixes for them and thus it is exceedingly unlikely to happen. Adding a symlink is ugly, but it is the only viable way of fixing this and since we would like to make a bit of a push to improve Fedora Workstation for gaming for Fedora 37 it would be really nice if we could resolve this issue somehow.

Comment 3 Carl George 🤠 2022-09-03 21:44:17 UTC
I don't notice a difference when running lspci as root versus running it as a non-root user.  The man page doesn't indicate that root permissions are needed (unlike setpci which does state that explicitly).  Would it be appropriate to just move lspci from /usr/sbin to /usr/bin outright?

Comment 4 Estinabot56 2022-11-26 06:36:19 UTC Comment hidden (spam)
Comment 5 Neal Gompa 2023-09-25 03:14:24 UTC
I would like this to be reconsidered for Fedora 39+ to fix this as Carl suggests and just move it.

Can we please do this?

Comment 6 Neal Gompa 2023-09-25 03:20:20 UTC
Oh actually, we can't move it because it's entirely possible things rely on "/sbin/lspci" Provides actually meaning something.

So, symlink it is... :/

Comment 7 Neal Gompa 2023-09-25 03:34:30 UTC
PR submitted: https://src.fedoraproject.org/rpms/pciutils/pull-request/4

Comment 8 Neal Gompa 2023-10-06 09:45:57 UTC
Now that the pull request has been merged, let's try to get this in for F39...

Comment 9 Fedora Blocker Bugs Application 2023-10-06 09:47:46 UTC
Proposed as a Freeze Exception for 39-final by Fedora user ngompa using the blocker tracking app because:

 This would make it so that Dying Light and other games can launch properly. It'd be nice to have this fix in F39 GA for reviewers who might try gaming in Fedora reviews.

Comment 10 Fedora Update System 2023-10-06 10:07:25 UTC
FEDORA-2023-5ed3ec0f58 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-5ed3ec0f58

Comment 11 Fedora Update System 2023-10-07 02:32:34 UTC
FEDORA-2023-5ed3ec0f58 has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-5ed3ec0f58`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-5ed3ec0f58

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 12 Geoffrey Marr 2023-10-09 18:00:01 UTC
Discussed during the 2023-10-09 blocker review meeting: [0]

The decision to delay the classification of this as a freeze exception was made as we cannot agree on a decision. Note that the effect of a punt is similar to a rejection, which is intended; active acceptance must be the requirement to break the freeze. 

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2023-10-09/f39-blocker-review.2023-10-09-16.00.txt

Comment 13 Adam Williamson 2023-10-11 17:11:35 UTC
+4 / -8 in https://pagure.io/fedora-qa/blocker-review/issue/1387 , marking rejected FE. We think it's fine for this to be just a regular update. It is already submitted to stable, so it will be available immediately on release day (actually a little before).

Comment 14 Fedora Update System 2023-11-03 18:31:06 UTC
FEDORA-2023-5ed3ec0f58 has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.