It may be that, the issue is “zypper dup” together with some repositories which provide software which is no compatible with YaST.
Please check the following:
"zypper repos --priority --uri
" – AKA “zypper lr -pu” – check the repositories listed very carefully – “zypper dup” functions correctly ONLY for the default openSUSE repositories with the possibly exception of the OFFICIAL update repositories. - Assuming that, any “rogue” repositories have been disabled, execute "zypper verify
". - You may need to rebuild the RPM database: "rpm --rebuilddb
". - When you have done all that and, you’re certain that the installed Ruby is the package from the default openSUSE repositories, forcibly reinstall YaST and all the packages YaST depends on plus, the packages which depend on YaST:
When you’ve done all that and, YaST is behaving as it should do, perform “rcrpmconfigcheck” and perform any needed housekeeping with respect to the system’s configuration files.
[HR][/HR]Possibly, your post with respect to a Java issue related to execution privileges and rights, is related to the houskeeping to be performed due to this issue.
After trying the above and more it was still no go.
I finally just used
snapper rollback nnn
and got to a point before the problem started. I backed up all my data first of course.
Then I restored my data (not sure if it was necessary but it doesn’t hurt) and everything was working as it should. I personally don’t like not knowing the exact cause and precision fix of things like this but in this case expediency won out.
One very nice thing I noticed about snapper rollback is that is automatically makes a current snapshot before it rolls back to a previous state.