Opened 5 years ago
Last modified 5 years ago
#18679 new defect
Segmentation fault on startup up of `VirtualBox` under sway-wm using Wayland
| Reported by: | tormen | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 6.0.8 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | Linux |
Description
Hi,
ENVIRONMENT & VERSIONS:
I am using sway as wayland compositor on an archlinux system. sway is started with the following environment variables:
QT_QPA_PLATFORM=wayland QT_WAYLAND_DISABLE_WINDOWDECORATION="1" QT_WAYLAND_FORCE_DPI=100 QT_PLUGIN_PATH=/usr/lib/kde4/plugins/ QT_AUTO_SCREEN_SCALE_FACTOR=0 QT_QPA_PLATFORMTHEME=gtk3
community/virtualbox 6.0.8-2 [installed] community/virtualbox-host-dkms 6.0.8-2 [installed] extra/qt5-wayland 5.12.3-1 (qt qt5) [installed]
PROBLEM
VirtualBox segfaults everytime:
VirtualBox [1] 8016 segmentation fault (core dumped) VirtualBox
Please let me know if I can provide anything else.
Tormen
Attachments (1)
Change History (4)
by , 5 years ago
| Attachment: | coredumpctl_gdb_VirtualBox added |
|---|
comment:1 by , 5 years ago
Please see if this happens when you use an Oracle build of VirtualBox. Otherwise you should open a report with Arch Linux. The "extra/qt5-wayland 5.12.3-1" does not look good to me though. We expect Qt to be using X11.
comment:2 by , 5 years ago
I have the same issue.
My environment: Arch Linux + sway-wm (on Wayland), no xwayland.
I have a HiDPI setup and I intentionally don't want to use xwayland because of scalability problems with it.
I can say that VirtualBox works on this setup with xwayland. But it has no value to me, due to scalability issues with xwayland apps (e.g. blurriness).
As for the packages which I have installed:
- qt5-wayland 5.12.4-1
- virtualbox 6.0.8-2
- virtualbox-host-dkms 6.0.8-2
Here is what Arch Linux devs are saying: https://bugs.archlinux.org/task/58761
Particularly this comment:
--- This is a virtualbox bug, not a Qt one. VB is unconditionally using x11 specific code. The reason why this became an issue now is because Qt 5.11 defaults to the Wayland backend on Wayland sessions (eg. Gnome). Either the x11 specific code needs to be properly ifdef'd or, if that's not possible, VB should enforce the xcb backend. ---
I would really appreciate if this gets fixed. Until than, I've lost ability to use VirtualBox =(.
comment:3 by , 5 years ago
We will probably have to support Wayland at some point, but it will not happen just yet, for lack of developer time. I would like to say "patches welcome", but even integrating the patches would be more work than we can currently handle. That said, if anyone does want to speed up the process, looking at what is needed (the vbox-dev mailing list would be a good place) and giving us feedback would be a good way.
For now we will look to see how to enforce the xcb plugin.


coredumpctl gdb VirtualBox