[arch-general] VirtualBox crashes when adding choose existing to SATA controller
The VirtualBox gui crashes when you want to add an existing hard disk to a SATA controller. Steps to reproduce: Select a Machine -> Settings -> Storage -> Controller: SATA -> Add hard disk -> Choose existing disk Then you will see the following message when you have started the Oracle VM VirtualBox Manager in a terminal: % VirtualBox Qt WARNING: libpng warning: iCCP: known incorrect sRGB profile (VirtualBox:7254): Gdk-WARNING **: gdkwindow-x11.c:5554 drawable is not a native X11 window [1] 7254 segmentation fault VirtualBox The corresponding machine had no hard disk applied. I guess I have to use some Command line to get the machine up again...
On Fri, 14 Oct 2016 09:29:08 +0200, Peter Bauer wrote:
I guess I have to use some Command line to get the machine up again...
Take a look at the log files. The paths are not necessarily those .VirtualBox/VBoxSVC.log* VirtualBox\ VMs/*/Logs/VBox.log* Regards, Ralf PS: I already wrote a script to backup and restore from an older backup, all settings and the guest, if something fails. VBox is easy to use, but regarding reliability a PITA. Sometimes it takes very long to repair something broken and sometimes it's impossible. Restoring from a backup usually is the better way to go. Btw. regarding to https://bugs.archlinux.org/task/50120 I stay with 5.0.24. [rocketmouse@archlinux ~]$ pacman -Q virtualbox virtualbox 5.0.24-1 [rocketmouse@archlinux ~]$ objdump -p /usr/lib/virtualbox/components/* 2>/dev/null|grep libvpx NEEDED libvpx.so.3 [rocketmouse@archlinux ~]$ pacman -Ql libvpx | grep so libvpx /usr/lib/libvpx.so libvpx /usr/lib/libvpx.so.4 libvpx /usr/lib/libvpx.so.4.0 libvpx /usr/lib/libvpx.so.4.0.0 [rocketmouse@archlinux ~]$ ls -hl /lib/libvpx.so* lrwxrwxrwx 1 root root 15 Aug 1 19:41 /lib/libvpx.so -> libvpx.so.4.0.0 lrwxrwxrwx 1 root root 15 Jan 16 2016 /lib/libvpx.so.3 -> libvpx.so.3.0.0 lrwxrwxrwx 1 root root 15 Jan 16 2016 /lib/libvpx.so.3.0 -> libvpx.so.3.0.0 -rwxr-xr-x 1 root root 3.4M Jan 16 2016 /lib/libvpx.so.3.0.0 lrwxrwxrwx 1 root root 15 Aug 1 19:41 /lib/libvpx.so.4 -> libvpx.so.4.0.0 lrwxrwxrwx 1 root root 15 Aug 1 19:41 /lib/libvpx.so.4.0 -> libvpx.so.4.0.0 -rwxr-xr-x 1 root root 3.3M Aug 1 19:41 /lib/libvpx.so.4.0.0
Am 14.10.2016 um 10:01 schrieb Ralf Mardorf:
On Fri, 14 Oct 2016 09:29:08 +0200, Peter Bauer wrote:
I guess I have to use some Command line to get the machine up again...
Take a look at the log files.
The paths are not necessarily those
.VirtualBox/VBoxSVC.log* VirtualBox\ VMs/*/Logs/VBox.log*
Obviously I was running gnome-shell (mutter) with wayland, not Xorg. I was able to switch to Xorg in the log-in screen (GDM). Now no crash happens. I will try on Monday with wayland again and try to provide logs. The Windows7 32Bit machine was also constantly crashing on wayland. With xorg, it seems stable till now.
Btw. regarding to https://bugs.archlinux.org/task/50120 I stay with 5.0.24.
[rocketmouse@archlinux ~]$ pacman -Q virtualbox virtualbox 5.0.24-1 [rocketmouse@archlinux ~]$ objdump -p /usr/lib/virtualbox/components/* 2>/dev/null|grep libvpx NEEDED libvpx.so.3 [rocketmouse@archlinux ~]$ pacman -Ql libvpx | grep so libvpx /usr/lib/libvpx.so libvpx /usr/lib/libvpx.so.4 libvpx /usr/lib/libvpx.so.4.0 libvpx /usr/lib/libvpx.so.4.0.0 [rocketmouse@archlinux ~]$ ls -hl /lib/libvpx.so* lrwxrwxrwx 1 root root 15 Aug 1 19:41 /lib/libvpx.so -> libvpx.so.4.0.0 lrwxrwxrwx 1 root root 15 Jan 16 2016 /lib/libvpx.so.3 -> libvpx.so.3.0.0 lrwxrwxrwx 1 root root 15 Jan 16 2016 /lib/libvpx.so.3.0 -> libvpx.so.3.0.0 -rwxr-xr-x 1 root root 3.4M Jan 16 2016 /lib/libvpx.so.3.0.0 lrwxrwxrwx 1 root root 15 Aug 1 19:41 /lib/libvpx.so.4 -> libvpx.so.4.0.0 lrwxrwxrwx 1 root root 15 Aug 1 19:41 /lib/libvpx.so.4.0 -> libvpx.so.4.0.0 -rwxr-xr-x 1 root root 3.3M Aug 1 19:41 /lib/libvpx.so.4.0.0
This is a neat info. But I don't care about the look of the mouse pointer. I get things done (TM) even with an ugly cursor. On the other hand, wayland brings down gnome-shell on my multihead setup. I have a lenovo x230t and two external monitors. Spontaneous log-outs, all input devices dead etc. Backups for the win! With Xorg no big problems. At least it's Friday.
This is a known qt5-base issue [1], especially on gnome-wayland. The qgnomeplatform theme, which provides uniform look for QT and GTK apps, doesn't support GTK3 wayland compositor. As temporary workaround, you can tell GTK3 library to use x11 backend (GDK_BACKEND=x11) or by installing qt5ct package and setting QT_QPA_PLATFORMTHEME variable to qt5ct. [1] https://bugs.archlinux.org/task/50013
participants (3)
-
Alive 4ever
-
Peter Bauer
-
Ralf Mardorf