Newest Kernel with MATE - black screen - previous kernel works fine

This is a virtualbox virtual machine
I can get into tty4 from the black screen - this is what MATE startup shows

UID        PID  PPID  C STIME TTY          TIME CMD
root         1     0  1 18:30 ?        00:00:02 /usr/lib/systemd/systemd --switched-root --system --deserialize 29
root      1669     1  0 18:30 ?        00:00:00 /usr/sbin/gdm
root      1679  1669  0 18:30 ?        00:00:00 gdm-session-worker [pam/gdm-autologin]
user      1693  1679  0 18:30 tty2     00:00:00 /usr/lib/gdm/gdm-x-session --register-session --run-script mate-session
user      1695  1693  0 18:30 tty2     00:00:00 /usr/bin/X vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
user      1716  1693  0 18:30 tty2     00:00:00 -bash --login -c exec "${@}" - /etc/X11/xdm/sys.xsession
user      1800  1716  0 18:30 tty2     00:00:00 /usr/bin/xset s 0 0

this is what a the previous kernel for MATE running looks like - It showed some warning about unable to resizing the virtual screen that went away after 10 seconds

UID        PID  PPID  C STIME TTY          TIME CMD
root         1     0  5 18:34 ?        00:00:02 /usr/lib/systemd/systemd --switched-root --system --deserialize 29
root      1668     1  0 18:34 ?        00:00:00 /usr/sbin/gdm
root      1677  1668  0 18:34 ?        00:00:00 gdm-session-worker [pam/gdm-autologin]
user      1691  1677  0 18:34 tty2     00:00:00 /usr/lib/gdm/gdm-x-session --register-session --run-script mate-session
user      1693  1691  3 18:34 tty2     00:00:01 /usr/bin/X vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3
user      1714  1691  0 18:34 tty2     00:00:00 mate-session
user      1753  1714  0 18:34 tty2     00:00:00 [Xsession] <defunct>
user      1807  1714  0 18:34 ?        00:00:00 /usr/bin/ssh-agent /etc/X11/xinit/xinitrc
user      1892  1714  0 18:34 tty2     00:00:00 /usr/bin/mate-settings-daemon
user      1899  1714  0 18:34 tty2     00:00:00 marco
user      1916  1714  0 18:34 tty2     00:00:00 mate-panel
user      1931  1714  2 18:34 tty2     00:00:00 /usr/bin/caja
user      1941  1714  0 18:34 tty2     00:00:00 nm-applet --indicator
user      1945  1714  0 18:34 tty2     00:00:00 /usr/lib/polkit-mate/polkit-mate-authentication-agent-1
user      1948  1714  0 18:34 tty2     00:00:00 package-update-indicator
user      1962  1714  0 18:34 tty2     00:00:00 /usr/bin/python3 /usr/share/system-config-printer/applet.py

This is the contents of /boot

ll /boot
total 74192
-rw-r--r-- 1 root root       65 May 15 21:56 .vmlinuz-5.6.12-1-default.hmac
-rw-r--r-- 1 root root       65 May 26 11:56 .vmlinuz-5.6.14-1-default.hmac
-rw-r--r-- 1 root root  4782313 May 15 21:03 System.map-5.6.12-1-default
-rw-r--r-- 1 root root  4782540 May 26 11:09 System.map-5.6.14-1-default
-rw-r--r-- 1 root root     1725 Apr 27 17:06 boot.readme
-rw-r--r-- 1 root root   232175 May 15 20:26 config-5.6.12-1-default
-rw-r--r-- 1 root root   232078 May 26 10:31 config-5.6.14-1-default
drwxr-xr-x 2 root root     4096 May 26 10:31 dracut
drwxr-xr-x 5 root root     4096 May 27 18:27 grub2
lrwxrwxrwx 1 root root       23 May 27 18:09 initrd -> initrd-5.6.14-1-default
-rw------- 1 root root 13080180 May 27 18:12 initrd-5.6.12-1-default
-rw------- 1 root root 13217504 May 27 18:27 initrd-5.6.14-1-default
-rw-r--r-- 1 root root   421376 May 13 15:48 message
-rw-r--r-- 1 root root   433893 May 15 21:07 symvers-5.6.12-1-default.gz
-rw-r--r-- 1 root root   434046 May 26 11:13 symvers-5.6.14-1-default.gz
-rw-r--r-- 1 root root      484 May 15 21:07 sysctl.conf-5.6.12-1-default
-rw-r--r-- 1 root root      484 May 26 11:13 sysctl.conf-5.6.14-1-default
-rw-r--r-- 1 root root  9993560 May 15 21:13 vmlinux-5.6.12-1-default.xz
-rw-r--r-- 1 root root  9980448 May 26 11:18 vmlinux-5.6.14-1-default.xz
lrwxrwxrwx 1 root root       24 May 27 18:09 vmlinuz -> vmlinuz-5.6.14-1-default
-rw-r--r-- 1 root root  9168528 May 15 21:56 vmlinuz-5.6.12-1-default
-rw-r--r-- 1 root root  9168528 May 26 11:56 vmlinuz-5.6.14-1-default

Interesting - Virtualbox reports guest additions of 6.0.0 in the good kernel and 6.1.8 in the bad one via Hostkey N.

I found the issue - missing .so file - this was from the VirtualBox website.
It appears that VB 6.1.8 needs a file that is missing. This made it work.

VM14:~ # cd /usr/lib64
VM14:/usr/lib64 # ll libvpx*
lrwxrwxrwx 1 root root      15 Jan 12 16:32 libvpx.so.6 -> libvpx.so.6.2.0
lrwxrwxrwx 1 root root      15 Jan 12 16:32 libvpx.so.6.2 -> libvpx.so.6.2.0
-rwxr-xr-x 1 root root 2357864 Jan 12 16:32 libvpx.so.6
VM14:/usr/lib64 # ln -s  libvpx.so.6 libvpx.so.4
VM14:/usr/lib64 # ll libvpx*
lrwxrwxrwx 1 root root      11 May 27 19:15 libvpx.so.4 -> libvpx.so.6
lrwxrwxrwx 1 root root      15 Jan 12 16:32 libvpx.so.6 -> libvpx.so.6.2.0
lrwxrwxrwx 1 root root      15 Jan 12 16:32 libvpx.so.6.2 -> libvpx.so.6.2.0
-rwxr-xr-x 1 root root 2357864 Jan 12 16:32 libvpx.so.6
VM14:/usr/lib64 #

First,
Any issues related to virtualization more often than not should be posted to the Virtualization forum, issues are frequently related specifically to the virtualization used and only sometimes more broadly related to all installs.

You should also post the following which is relevant to fixing the problem…
And this is partly because simply identify the Desktop installed in your system is insufficient…

  • What is your HostOS?
  • What is your GuestOS?
  • You’ve identified your virtualization as Virtualbox, but on openSUSE you can install Virtualbox from the openSUSE repos or you can install from the Oracle Virtualbox website, and the issues can be very different. You need to clarify.
  • In this case, it might be useful to identify the kernels if one worked and he other doesn’t… Only maybe.

And,
If you found something really useful, I’m sure that others will be greatful if you submit your findings in detail to https://bugzilla.opensuse.org

TSU

  1. Host OpenSUSE 15.1 All repos are Opensuse default except packman, skype, and teamviewer. Guest is 100% Opensuse default with packman.
  2. Was not aware it was a virtualbox issue - it looked like a zypper dup problem with the new kernel to me.
  3. I troubleshot Unix for 40 years - I try to find root cause for any failure. I was good at it - Linux is no different for solving issues.
  4. In comparing what changed from the dup - I saw virtualbox guest additions switched to 6.1.8. The debug for virtualbox says use HOME+N to see what is in use. Thats when I went looking to Virtualbox forum for Tumbleweed issues and found the missing so causes failure.
  5. bugzilla for tumbleweed - I tried to create but bugzilla gives:
    Software error: Can’t connect to the database.
    Error: Host ‘novprvlin1092-suse.bugzilla-priv.suse.de’ is blocked because of many connection errors; unblock with ‘mysqladmin flush-hosts’
    Is your database installed and up and running?
    Do you have the correct username and password selected in localconfig?

For help, please send mail to the webmaster (novbugzilla-dev@forge.provo.novell.com), giving this error message and the time and date of the error.

Hi
Looks like some additional migration is under way with bugzilla…

Bugzilla – Bug 1172238 Submitted

I got that error earlier today. But a little later, I was able to connect to bugzilla without problems.

@larryr,

Cool, and I’m sure openSUSE TW Users running VBox appreciate your find.
TW is always on the leading edge of technology so your contribution benefits more people than you can know.

TSU