Results 1 to 3 of 3

Thread: The submenu for software management do not start.

  1. #1
    Join Date
    Aug 2017
    Location
    Montréal. Canada
    Posts
    86

    Default The submenu for software management do not start.

    The submenu of Yast2. I forgot to specified.

    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.
    Hard times create strong men,
    Strong men create good times,
    Good times create weak men,
    Weak men create hard times.

  2. #2
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,481
    Blog Entries
    3

    Default Re: The submenu for software management do not start.

    Quote Originally Posted by Asimov View Post
    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
    That can be safely ignored.

    Qt: Session management error: None of the authentication protocols specified are supported
    I don't think I have seen that issue.

    Whatever you did with Ruby might well be the problem.
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  3. #3
    Join Date
    Aug 2017
    Location
    Montréal. Canada
    Posts
    86

    Default Re: The submenu for software management do not start.

    Quote Originally Posted by nrickert View Post
    That can be safely ignored.


    I don't think I have seen that issue.

    Whatever you did with Ruby might well be the problem.
    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.
    Hard times create strong men,
    Strong men create good times,
    Good times create weak men,
    Weak men create hard times.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •