Bug 1653638 - Unable to load native library: libnsl.so.1: cannot open shared object file: No such file or directory
Summary: Unable to load native library: libnsl.so.1: cannot open shared object file: N...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Carlos O'Donell
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-27 10:30 UTC by Juan Andres Moreno
Modified: 2018-11-27 11:12 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-27 11:12:46 UTC
Type: Bug


Attachments (Terms of Use)
Screenshot (49.89 KB, image/png)
2018-11-27 10:30 UTC, Juan Andres Moreno
no flags Details

Description Juan Andres Moreno 2018-11-27 10:30:18 UTC
Created attachment 1508791 [details]
Screenshot

Description of problem:
When I try to execute an Oracle jdk component, I get the following error:

Unable to load native library: libnsl.so.1: cannot open shared object file: No such file or directory 


Version-Release number of selected component (if applicable):
Fedora 29
Oracle Java jdk1.6u45


How reproducible:


Steps to Reproduce:
1.Download oracle java jdk 1.6u45.rpm.bin
2.Install appropiate package version
3.Execute any java command (e.g. java, javac, etc)

Actual results:
$ ./java -version
Error occurred during initialization of VM
Unable to load native library: libnsl.so.1: cannot open shared object file: No such file or directory

Expected results:
$ java -version
java version "1.6.0_45"


Additional info:

Comment 1 Florian Weimer 2018-11-27 10:32:04 UTC
Does the failure go away if you install the libnsl package?  Thanks.

Comment 2 Juan Andres Moreno 2018-11-27 11:10:26 UTC
(In reply to Florian Weimer from comment #1)
> Does the failure go away if you install the libnsl package?  Thanks.

Yes, Thank you so much. It works!


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