I manage to reinstall it with yast. It wont start from the menu but i can launch it from a console. But a got this message:
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
And i do not know how to fix this.
I manage to reinstall it with yast. It wont start from the menu but i can launch it from a console. But a got this message:
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
And i do not know how to fix this.
I get that message. It doesn’t seem to cause any problems. Just ignore the message.
On Tue, 01 Jan 2019 15:56:03 +0000, Asimov wrote:
> I manage to reinstall it with yast. It wont start from the menu but i
> can launch it from a console. But a got this message:
>
> QStandardPaths: wrong ownership on runtime directory /run/user/1000,
> 1000 instead of 0
>
> And i do not know how to fix this.
If you uninstalled it, you can use zypper to reinstall it.
What is the output from:
rpm -qa | grep -i yast
?
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
i already done it with zypper. I can launch it from a terminal. But i can not launch it from the Plasma’s menu.
Specialy when it is about a GUI interface, where nobody here can see what you do and see, detailed description is needed to give others any idea about your problem.
Isn’t the item in the Plasma menu at all?
Is it there but when you click on it YaST is not started?
Please provide the output asked for. Installing ‘yast’ is not enough.
Plus, show
rpm -qa | grep yast2
Yes, Yast is visible in the menu. But a can not lunch it from the menu. I have to open a terminal and write yast2 to have it.
You’ll need at least the following YaST packages:
Once those packages are installed, you should be able to use the following Patterns to pull in the rest of the YaST environment:
You may also need:
Hi,
The file
/var/log/zypp/history
Which is owned by the root user, might be a good start if you want to look for the packages that has been removed.
(Just replace the remove with install to find out which packages got installed.)
NOTE: The code below assumes that you’re using the default shell which is bash.
For example If you want to look for the packages that has been remove today, a filter can be used (pattern matching)
grep "$(date -d'**now**' '+%F').*|**remove**" /var/log/zypp/history
From the last three days.
grep "$(date -d'**3days ago**' '+%F').*|**remove**" /var/log/zypp/history
From last month.
grep "$(date -d'**last month**' '+%F').*|**remove**" /var/log/zypp/history
Since GNU date is being used in the above code, I suggest you look at the info pages for more info about some examples on which words/syntax is accepted when searching for date.
info date
It’s a “GNU thing” so don’t ask me why info pages and not man pages.
When searching for just the package name which has been removed. Like for example you want to search for the word yast ANY WHERE in the package name.
(Just replace the remove with install to do the opposite.)
grep ".*|**remove**:space:]]*|**.*yast**" /var/log/zypp/history
Note that grep is using BRE by default unless you tell it to use ERE but that is another story.
See
man 7 regex
grep --help
man grep
for more info about BRE, and btw if I’m not mistaken Leap 15.0 does not come with the Linux man pages so you might need to install the package
man-pages
and
man-pages-posix
I did all the reinstallation. But i have the feeling that my menu is set on a broken link. Can you tell me the directory of the binary ?
I will keep this one in mind the next time in update go south.
In your initial post you mention “QStandardPaths:” – therefore I’m assuming that, your user GUI is KDE …
For the case of KDE Plasma 5, the menu command for YaST is “/usr/bin/xdg-su -c /sbin/yast2”.
The problem is still not solved. And i really do not know what missing.
susepaste yast.txtPasted as:
http://susepaste.org/92758692
http://paste.opensuse.org/92758692
I did try /sbin/yast2. And i think i found the problem:
Yast.rb is unable to import a file in “import_pure”:
Line 186.
The complete message:
Error
internal error. Please report a bug report with logs.
run save_y2logs to get complet logs
Details: failed to load module 'PackageCallbacks' due to failed to load Module 'SignatureCheckCallbacks' due to: indefined method 'message' for nil:Nilclass caller: usr/lib64/ruby/vendor_ruby/2.5.0/yast/yast.rb: 186 in 'import_pure'
You haven’t, yet, completely restored everything needed by YaST2:
> rpm --query --whatprovides /usr/lib64/ruby/vendor_ruby/2.5.0/yast/yast.rb
yast2-ruby-bindings-4.0.6-lp150.1.1.x86_64
>
> zypper info --requires yast2-ruby-bindings
Loading repository data...
Reading installed packages...
Information for package yast2-ruby-bindings:
--------------------------------------------
Repository : Haupt-Repository (OSS)
Name : yast2-ruby-bindings
Version : 4.0.6-lp150.1.1
Arch : x86_64
Vendor : openSUSE
Installed Size : 421.9 KiB
Installed : Yes
Status : up-to-date
Source package : yast2-ruby-bindings-4.0.6-lp150.1.1.src
Summary : Ruby bindings for the YaST platform
Description :
The bindings allow YaST modules to be written using the Ruby language
and also Ruby scripts can use YaST agents, APIs and modules.
Requires : [26]
libc.so.6(GLIBC_2.14)(64bit)
libstdc++.so.6()(64bit)
libstdc++.so.6(CXXABI_1.3)(64bit)
libstdc++.so.6(GLIBCXX_3.4)(64bit)
libm.so.6()(64bit)
libgcc_s.so.1()(64bit)
libgcc_s.so.1(GCC_3.0)(64bit)
libstdc++.so.6(GLIBCXX_3.4.21)(64bit)
libstdc++.so.6(GLIBCXX_3.4.9)(64bit)
libstdc++.so.6(GLIBCXX_3.4.20)(64bit)
libstdc++.so.6(CXXABI_1.3.8)(64bit)
libcrypt.so.1()(64bit)
libcrypt.so.1(GLIBC_2.2.5)(64bit)
/usr/bin/ruby.ruby2.5
libruby2.5.so.2.5()(64bit)
ruby
liby2.so.4()(64bit)
libycp.so.5()(64bit)
rubygem(ruby:2.5.0:fast_gettext)
libowcrypt.so.1()(64bit)
libowcrypt.so.1(OW_CRYPT_1.0)(64bit)
libpy2UI.so.2()(64bit)
libpy2wfm.so.2()(64bit)
libpy2scr.so.2()(64bit)
yast2-ycp-ui-bindings >= 3.2.0
yast2-core >= 3.2.2
>