Description of problem: While scanning using xsane from a HP LaserJet M1132MFP device, I get error messages about libhpmud.so and libm.so not being found in the logs. Version-Release number of selected component (if applicable): hplip-3.22.2-1.fc35.x86_64 How reproducible: Always Steps to Reproduce: 1. Run xsane 2. Select M1132MFP scanner device 3. Acquire preview Actual results: Apr 29 11:19:49 xsane[3637]: common/utils.c 249: unable to load library libhpmud.so: libhpmud.so: cannot open shared object file: No such file or directory Apr 29 11:19:49 xsane[3637]: common/utils.c 249: unable to load library libm.so: /lib64/libm.so: invalid ELF header Expected results: No messages about library load failures. Additional info: It seems that the code attempts to load the .so file first and then falls back to loading .so.X in some places: libhpmud.so: https://fossies.org/linux/misc/legacy/hplip-3.22.2.tar.gz/hplip-3.22.2/scan/sane/marvell.c#l_63 https://fossies.org/linux/misc/legacy/hplip-3.22.2.tar.gz/hplip-3.22.2/scan/sane/soap.c#l_71 libm.so: https://fossies.org/linux/misc/legacy/hplip-3.22.2.tar.gz/hplip-3.22.2/scan/sane/escl.c#l_47 https://fossies.org/linux/misc/legacy/hplip-3.22.2.tar.gz/hplip-3.22.2/scan/sane/marvell.c#l_70 https://fossies.org/linux/misc/legacy/hplip-3.22.2.tar.gz/hplip-3.22.2/scan/sane/soap.c#l_78 https://fossies.org/linux/misc/legacy/hplip-3.22.2.tar.gz/hplip-3.22.2/scan/sane/soapht.c#l_72
Hi Dominik, I'm sorry for the late response and thank you for filing the bug! The issue was a little tricky - we shipped libhpmud.so in hplip-libs in the past, but rpmlint was complaining about it so it was removed. The proper solution would be to have the file in -devel package, but then we would need to require -devel package during runtime, which is not ideal as well. So in the end I've removed loading of unversioned .so files. The commit is https://src.fedoraproject.org/rpms/hplip/c/297f625d957216cbfffbab984afbc76424f5e30f?branch=rawhide .
FEDORA-2022-83d0e628a8 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-83d0e628a8
FEDORA-2022-0ec7dd5c78 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-0ec7dd5c78
FEDORA-2022-83d0e628a8 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-83d0e628a8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-83d0e628a8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-0ec7dd5c78 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-0ec7dd5c78` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-0ec7dd5c78 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Confirmed fixed on F36, thanks!
FEDORA-2022-83d0e628a8 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
(In reply to Dominik 'Rathann' Mierzejewski from comment #6) > Confirmed fixed on F36, thanks! Thank you for checking this, Dominik!
FEDORA-2022-0ec7dd5c78 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.