Bug 23943 - Hardinfo will not load modules (No module could be loaded. Check permissions on "/usr/usr/lib64/hardinfo" and try again.)
Summary: Hardinfo will not load modules (No module could be loaded. Check permissions ...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Stig-Ørjan Smelror
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-06 00:40 CET by Thomas Andrews
Modified: 2018-12-07 19:11 CET (History)
2 users (show)

See Also:
Source RPM: hardinfo-0.5.2-0.git20180615.2.mga7
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Thomas Andrews 2018-12-06 00:40:33 CET 
Description of problem:

When you run hardinfo, you immediately get an error message that says "No module could be loaded. Check permissions on "/usr/usr/lib64/hardinfo" and try again."

Note that "/usr/usr/lib64/hardinfo" does not exist. It should be "/usr/lib64/hardinfo."
Comment 1 Marja Van Waes 2018-12-06 07:55:33 CET 
Confirming the issue.

Creating a link in the /usr directory ([root@localhost usr]# ln -s /usr usr) makes hardinfo work again. I'll remove the link again, though, it is too dirty.
 
There's no registered maintainer, so assigning to all packagers.

CC: (none) => marja11
Source RPM: (none) => hardinfo-0.5.2-0.git20180615.2.mga7
Assignee: bugsquad => pkg-bugs
Summary: Hardinfo will not load modules => Hardinfo will not load modules (No module could be loaded. Check permissions on "/usr/usr/lib64/hardinfo" and try again.)

Stig-Ørjan Smelror 2018-12-06 21:30:20 CET

Assignee: pkg-bugs => smelror
CC: (none) => smelror

Comment 2 Stig-Ørjan Smelror 2018-12-06 21:42:02 CET 
Fixed in hardinfo 0.6 just pushed to Cauldron.
Comment 3 Thomas Andrews 2018-12-07 19:11:54 CET 
Waited overnight for my mirror to sync before trying this, then just as I was about to report here, my Internet service went down for a while. 

This does indeed fix the issue. Moreover, the problems reported in Bug 20549 appear to be gone. 

Marking it as "Fixed."

Resolution: (none) => FIXED
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.