As you see, java simply works for a normal user. And when you follow all the symlinks from /usr/bin/java to the end, you see that everybody has execution permission.
So, yes, I guess something is borked on your system.
PS. Please copy/paste the prompt, the command, the output and the next prompt in one mouse sweep. That is so much easier for you to do and for us to read then all that story telling: When I do …, then I get …
-rwxr--r-- 1 root root 8632 Aug 19 16:17 /usr/lib64/jvm/jre-1.9.0-openjdk/bin/java*
That is indeed not what to expect. But as I said, I do not uee Tumbleweed, thus it would be better if a Tumbleweed user that used the same java could comment.
PS, how did the green texts appear in de copy/paste? I never get that.
I assume that the OP also understands that changing them is a solution to the incident. But the important thing is of course understanding the root cause. Simply reporting a bug without further evidence that it is realy wrong in the RMP is a bit of an easy shortcut imho.
> I assume that the OP also understands that changing them is a solution
> to the incident. But the important thing is of course understanding the
> root cause. Simply reporting a bug without further evidence that it is
> realy wrong in the RMP is a bit of an easy shortcut imho.
I just installed openjdk 1.9 to take a look at this on a TW.
Ran into the same issue, you can’t “read” the java version using a normal User account although you can if you execute the same command from a root console.
Unless something new is reported, I don’t know if this issue also applies to running a jar as a normal user (openjdk 1.9).
(Somewhere I’ve got an old standalone jar for testing but it’s not on my current machine)
Who knows, maybe it’s a new security loophole that’s been closed if it’s intentional.