Yast modules cant start after zypper update and restart computer

Oracle VM Virtualbox gui cant start too

I can see this errors in /var/log/warn

2019-12-17T09:33:05.863079+03:00 kadrf3 plasmashell[1499]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 12821, resource id: 41943046, major code: 142 (Unknown), minor code: 3
2019-12-17T09:33:07.236995+03:00 kadrf3 plasmashell[1499]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 13125, resource id: 41943046, major code: 142 (Unknown), minor code: 3
2019-12-17T09:37:33.963531+03:00 kadrf3 kwin_x11[1490]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2778, resource id: 67108936, major code: 18 (ChangeProperty), minor code: 0
2019-12-17T09:37:33.987931+03:00 kadrf3 kwin_x11[1490]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2810, resource id: 37749254, major code: 18 (ChangeProperty), minor code: 0

May be problem appeared because I started zypper update few weeks ago and didnt restart computer. And yesterday I’ve started zypper update again. Then after restart I got this problem.

KDE Plasma 5.12.8
KDE Framework 5.55.0
Qt 5.9.7
kernel 4.12.14-lp.151.28.36-default

Can anybody help me?

One more thing. I can start yast module from console without problems. For example

yast2 online_update

@rustemka71:

After patching or updating, run “zypper ps” to determine what needs to be restarted.

  • Maybe simply log out and then in again for most affected user processes.
  • After logging out, check again with “zypper ps
    ” to catch any user processes which didn’t get killed by logging out. - “ps -u «User ID»” may be needed to catch any other user processes which didn’t die at logout.
  • Maybe “systemctl restart «service name»
    ” to restart the affected system processes. - If the “systemd” process itself is affected or, a new Kernel has been installed then, a reboot is needed …

To check how much of the system needs to be repaired, with the user “root” execute:

  • “zypper verify”
  • “rpm --verify --all”
  • “rpmconfigcheck”

Hello! Thank you for answer.
**zypper ps, **zypper verify, rpmconfigcheck - everything is ok

And rpm --verify --all gives that

kadrf3:/etc/sysconfig # rpm --verify --allmissing     /var/cache/libx11/compose/l4_030_2629ba98_00280cc0
.M...U...    /var/cache/cups
.M.......  g /var/lib/ca-certificates/ca-bundle.pem
.M.......  g /var/lib/ca-certificates/java-cacerts
....L....    /usr/share/java/xml-commons-apis.jar
....L....    /etc/ImageMagick-7
.M.......  g /usr/share/fonts/75dpi/encodings.dir
.M.......  g /usr/share/fonts/75dpi/fonts.scale
.M.......  g /usr/share/fonts/misc/encodings.dir
.M.......  g /usr/share/fonts/misc/fonts.scale
.M....G..    /usr/lib/virtualbox/VBoxHeadless
.M....G..    /usr/lib/virtualbox/VBoxNetAdpCtl
.M....G..    /usr/lib/virtualbox/VBoxNetDHCP
.M....G..    /usr/lib/virtualbox/VBoxNetNAT
.M....G..    /usr/lib/virtualbox/VBoxSDL
.M....G..    /usr/lib/virtualbox/VirtualBox
.M....G..    /usr/lib/virtualbox/VirtualBoxVM
.M.......  c /etc/X11/xorg.conf.d/00-keyboard.conf
.M.......  c /etc/locale.conf
.M.......  c /etc/machine-id
.M.......  c /etc/vconsole.conf
.M.......  g /var/lib/systemd/random-seed
.M.......  g /etc/xml/catalog-d.xml
SM5....T.  c /etc/fonts/conf.d/30-metric-aliases.conf
.M.......  g /var/log/boot.log
.M.......  g /usr/share/fonts/100dpi/encodings.dir
.M.......  g /usr/share/fonts/100dpi/fonts.scale
.M.......  g /usr/share/fonts/Type1/encodings.dir
.M.......  g /usr/share/fonts/cyrillic/encodings.dir
.M.......  g /usr/share/fonts/cyrillic/fonts.scale
.M.......  g /usr/share/fonts/truetype/encodings.dir
.......T.  c /etc/xdg/kickoffrc
.M.......  g /var/log/alternatives.log
.M.......  g /run/mcelog
S.5....T.  c /etc/postfix/main.cf
S.5....T.  c /etc/postfix/master.cf
.......T.    /usr/lib64/gconv/gconv-modules.cache
.M.......  c /var/log/NetworkManager
.M.......  g /run/cryptsetup
.M....G..  g /var/log/lastlog
.M.......  g /etc/udev/hwdb.bin
.M.......  g /usr/lib/udev/compat-symlink-generation
S.5....T.  c /etc/unixODBC/odbcinst.ini
.....UG..  g /run/sddm
.M.......  g /boot/grub2/grub.cfg
S.5....T.  c /etc/default/grub
.M.......  g /run/avahi-daemon
....L....  c /etc/pam.d/common-account
....L....  c /etc/pam.d/common-auth
....L....  c /etc/pam.d/common-password
....L....  c /etc/pam.d/common-session
....L....  d /usr/share/man/man1/ftp.1.gz
.M.......  c /var/log/audit/audit.log
.......T.  c /etc/login.defs
S.5....T.  c /etc/fonts/conf.d/10-rendering-options.conf
S.5....T.  c /etc/fonts/conf.d/58-family-prefer-local.conf
.M.......  g /etc/iscsi/initiatorname.iscsi



You’ve posted not enough information to tie your various problems together.

If you suspect your system has lost consistency, a zypper update normally should clean things up. Of course, be sure that all your repositories are set to the correct openSUSE version (You can list your repositories with “zypper lr -d”)

zypper update

If a normal update doesn’t work, then you can try running a more complete update which borders on a re-install with

zypper dup

And, of course reboot to be sure you capture all changes made to your system.

As for your Virtualbox, you’ll first need to start with whether you installed from the openSUSE repositories or a download from the Oracle website, troubleshooting procedures are different depending on which way you installed.

TSU


 > rpm --query --whatprovides /var/cache/libx11/compose/l4_030_2629ba98_00280cc0
xorg-x11-libX11-ccache-7.6-lp151.2.1.noarch
 > 

You have to forcibly reinstall “xorg-x11-libX11-ccache” to remove the “missing” output of “rpm --verify”.

You may have to clean out the “~/.cache/” directory of the user “root” to recover from the YaST modules issue.

  • I doubt that, the contents of the “~/.cache/” directory of the user who is invoking YaST will need to be cleaned up but, you may have to that as well …
  • I suspect that, there’s nothing related to YaST in either the user’s “~/.config/” directory nor, the “~/.config/” directory of the user “root” …

Here, I see:


# ls -l .config/YaST2
total 12
-rw-r--r-- 1 root root 185 Dec 17 13:10 y2controlcenter-qt.conf
-rw-r--r-- 1 root root 185 Dec 17 13:10 YQOnlineUpdate.conf
-rw-r--r-- 1 root root 207 Dec 17 13:10 YQPackageSelector.conf

The timestamp is probably from the last time that I used Yast Online Update.
I doubt that there is anything there that is relevant to the specific problem being discussed in this thread.