Bug 2333659

Summary:	Opening a .step file fails with /usr/bin/OCCTWrapper.so: cannot open shared object file: No such file or directory
Product:	[Fedora] Fedora	Reporter:	Jan Pazdziora <adelton>
Component:	prusa-slicer	Assignee:	Jan Pazdziora <adelton>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	41	CC:	adelton, jstanek, j, mhroncok, spotrh
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-01-01 15:37:59 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jan Pazdziora 2024-12-21 17:06:19 UTC

When opening a .step file, prusa-slicer tries to dynamically load a OCCTWrapper.so. Sadly, even if prusa-slicer-2.8.0-3.fc41.x86_64 ships /usr/lib64/OCCTWrapper.so, it is not found because the program searches for it in /usr/bin.

Reproducible: Always

Steps to Reproduce:
1. Start prusa-slicer.
2. In Menu > File > Import > Import STL/3MF/STEP/OBJ/AMF... find /usr/share/opencascade/data/step/linkrods.step, click the Open button.
Actual Results:  
PrusaSlicer has encountered an error

Cannot load OCCTWrapper.so:
/usr/bin/OCCTWrapper.so: cannot open shared object file: No such file or directory

Expected Results:  
No error, .step file loaded.

Possible patch is in https://github.com/prusa3d/PrusaSlicer/pull/13761.

Comment 1 Jan Pazdziora 2024-12-21 19:39:44 UTC

Filed https://src.fedoraproject.org/rpms/prusa-slicer/pull-request/45.

Comment 2 Jan Pazdziora 2024-12-31 09:44:40 UTC

Pull request merged, rawhide build initiated: https://koji.fedoraproject.org/koji/taskinfo?taskID=127428607

Comment 3 Jan Pazdziora 2024-12-31 14:35:15 UTC

https://bodhi.fedoraproject.org/updates/FEDORA-2024-2c921de3af submitted to rawhide stable.

Comment 4 Jan Pazdziora 2025-01-01 15:37:59 UTC

The prusa-slicer-2.8.0-6.fc42 package is now available in the rawhide repo.

Comment 5 Jan Pazdziora 2025-01-01 21:17:41 UTC

Also filed https://src.fedoraproject.org/rpms/prusa-slicer/pull-request/46 to backport to Fedora 41.

Comment 6 Fedora Update System 2025-01-04 20:24:55 UTC

FEDORA-2025-21c5e4d2fd (prusa-slicer-2.8.0-4.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-21c5e4d2fd

Comment 7 Fedora Update System 2025-01-05 02:53:13 UTC

FEDORA-2025-21c5e4d2fd has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-21c5e4d2fd`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-21c5e4d2fd

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

Comment 8 Jan Pazdziora 2025-01-07 12:04:49 UTC

I've now created https://bodhi.fedoraproject.org/updates/FEDORA-2025-c9a6f25ca5 with a rebase to 2.8.1 which unfortunately made the https://bodhi.fedoraproject.org/updates/FEDORA-2025-21c5e4d2fd update obsolete. The new build however contains the backport of the fix for this bugzilla as well.

Comment 9 Fedora Update System 2025-01-08 02:12:34 UTC

FEDORA-2025-c9a6f25ca5 has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-c9a6f25ca5`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-c9a6f25ca5

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

Comment 10 Fedora Update System 2025-01-16 01:59:09 UTC

FEDORA-2025-c9a6f25ca5 (prusa-slicer-2.8.1-3.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.