I got this error message: "QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
Qt: Session management error: None of the authentication protocols specified are supported
I did screw up with rbenv. And I have accidentally installed a new version of Ruby for the System. Since then i was able to have Yast2 via a terminal. But not anymore. thing seems to get worse with the arrival of an app call: Discovery . Or Discovers, I do not remember exactly.
I would have to see the script calling Yast. Because since 2.4, the attention on the garbage collection. The language is losing popularity because of if speed. with the exception of the lambda function, the language is pretty mature, all the energy go in that direction. The optional setting might possibly be the cause. By default, the usage of memory is low. Changing affect the speed. But in my experience a big program made with Ruby on Rails, retro-compatibility is not usually an issue for me. But if Yast is using Lambda function it is possible.
But a bug in 2.5 would be on the top of suspect.