Opened 6 years ago
Closed 5 years ago
#18682 closed defect (fixed)
libcrypt legacy usage by vboxadd-service in Fedora 30 - Fixed in SVN
Reported by: | gats | Owned by: | |
---|---|---|---|
Component: | guest additions | Version: | VirtualBox 6.0.8 |
Keywords: | libcrypt vboxadd | Cc: | |
Guest type: | Linux | Host type: | all |
Description
It appears that the vboxadd-service in Fedora 30 is looking for the libcrypt.so.1 library:
vboxadd-service[1647]: /usr/sbin/VBoxService: error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory
This requirement appears to be for version 1 of libcrypt, and Fedora is now using version 2 according to this related link: https://www.mathworks.com/matlabcentral/answers/456839-fedora-30-matlab-start-issue
The version 1 library needs to be installed in Fedora by adding the libxcrypt-compat package:
dnf install libcrypt-compat
Alternatively, the vboxadd-service should be compiled against the new version of libcrypt, as most users are not innately familiar with legacy library troubleshooting.
Change History (5)
comment:1 by , 6 years ago
comment:2 by , 6 years ago
I thought that there was a ticket about this already, but apparently I simply remember a discussion in the forums: https://forums.virtualbox.org/viewtopic.php?f=3&t=92953
comment:3 by , 6 years ago
Since libxcrypt only ship with a very few distros, it makes no sense to build vboxadd-service against it rather than the glibc based libcrypt that distros have been using since forever. We're currently trying to dynamically resolve the crypt_r symbol we need from libcrypt.so or libxcrypt.so. The result should hit a test build next week, if it works out.
In the mean while just install the libxcrypt-compat package.
comment:4 by , 6 years ago
Summary: | libcrypt legacy usage by vboxadd-service in Fedora 30 → libcrypt legacy usage by vboxadd-service in Fedora 30 - Fixed in SVN |
---|
comment:5 by , 5 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
It looks like my typing instead of copy-paste tripped up the interim solution. The command should be:
dnf install libxcrypt-compat
Note the "x" in the name of the package. Too bad the interface here doesn't allow for editing my original entry.