Bug 24679 - Crash when ldconfig not in $PATH
Summary: Crash when ldconfig not in $PATH
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Rémi Verschelde
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-17 08:32 CEST by patrice metz
Modified: 2019-04-19 13:23 CEST (History)
1 user (show)

See Also:
Source RPM: lutris-0.5.2-1.mga7.src.rpm
CVE:
Status comment:


Attachments

Description patrice metz 2019-04-17 08:32:35 CEST
Description of problem:

I report bug on the github of lutris and be repaired with version 0.5.2.1

https://lutris.net/releases/lutris_0.5.2.1.tar.xz
https://github.com/lutris/lutris/issues/2018


now need add in spec file

"%post -p /sbin/ldconfig"

other problem
need vulkan libraries

32bits
Requires:       libmesavulkan-drivers
Requires:       libvulkan-loader1

64bit
Requires:       libmesavulkan-drivers
Requires:       libvulkan-loader1
Requires:       lib64mesavulkan-drivers
Requires:       lib64vulkan-loader1

see spec file from github lutris
https://github.com/lutris/lutris/blob/master/lutris.spec

for test I add 

Requires:       libmesavulkan-drivers
Requires:       libvulkan-loader1
%if x86_64
Requires:       lib64mesavulkan-drivers
Requires:       lib64vulkan-loader1
%endif


but despite vulkan libraries installed, vulkan no work but maybe it comes from my system

https://zupimages.net/up/19/16/6whj.png
Comment 1 David GEIGER 2019-04-17 08:42:19 CEST
Assigning to our registered maintainer!

Assignee: bugsquad => rverschelde
CC: (none) => geiger.david68210

Comment 2 Rémi Verschelde 2019-04-18 11:06:20 CEST
Thanks for the detailed feedback, it should be fixed in lutris-0.5.2.1-1.mga7.

> but despite vulkan libraries installed, vulkan no work but maybe it comes from my system

See if it works with the new package, your spec changes would have failed to install the 64-bit library as the package was noarch. I had to make it arch-specific for this logic to work.

But I'm not sure that Intel Sandybridge supports Vulkan at all though, even with the drivers installed.

I'm having an issue now that both 32-bit and 64-bit vulkan drivers are installed, as somehow the loader seems to try to load 32-bit first:

$ vulkaninfo
ERROR: [Loader Message] Code 0 : /usr/lib/libvulkan_intel.so: wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib/libvulkan_radeon.so: wrong ELF class: ELFCLASS32
INTEL-MESA: warning: ../src/intel/vulkan/anv_device.c:1242: FINISHME: Implement pop-free point clipping

But that's a separate issue, unrelated to Lutris itself.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 3 patrice metz 2019-04-18 15:03:13 CEST
I just tested your package (64 bits) this one works well
https://zupimages.net/up/19/16/1ztn.png

here is result with my package (noarch)
https://www.zupimages.net/up/19/16/ibrk.png

here is the spec file if you're interested
https://mega.nz/#!oIEinYxI!P-k717kOLuM8eDSmiytnNCwWt0Nz4nF8lMD6hiT5aUI

yes indeed my video card is not compatible vulkan, in addition to be optimus which adds problems hahaha 
https://videocardz.net/nvidia-geforce-gt-630m/

I found "Primus-vk" which allows to run Vulkan with the optimus cards

I spoke on MLO but with my old video card I can not really deepen the tests
https://www.mageialinux-online.org/forum/topic-25926-2+pb-serveur-d-affichage-nvidia-suite-mise-a-jour.php#m250519
Comment 4 Rémi Verschelde 2019-04-19 13:23:06 CEST
(In reply to patrice metz from comment #3)
> I just tested your package (64 bits) this one works well
> https://zupimages.net/up/19/16/1ztn.png
> 
> here is result with my package (noarch)
> https://www.zupimages.net/up/19/16/ibrk.png
> 
> here is the spec file if you're interested
> https://mega.nz/#!oIEinYxI!P-k717kOLuM8eDSmiytnNCwWt0Nz4nF8lMD6hiT5aUI

Your spec file worked for you because

`%if x86_64`

is not a correct way to check the architecture, it always evaluates to true. `%if oops` would have given the same result. So it works on x86_64, but would fail on i586.

Note You need to log in before you can comment on or make changes to this bug.