FS#58761 - [virtualbox] Can't launch virtualbox on wayland - segmentation fault
Attached to Project:
Community Packages
Opened by yurick gomes (yurick.gomes) - Monday, 28 May 2018, 16:10 GMT
Last edited by Toolybird (Toolybird) - Sunday, 16 April 2023, 01:59 GMT
Opened by yurick gomes (yurick.gomes) - Monday, 28 May 2018, 16:10 GMT
Last edited by Toolybird (Toolybird) - Sunday, 16 April 2023, 01:59 GMT
|
Details
Description:
Hello, i can't launch virtualbox since my latest system upgrade, it only shows a "segmentation fault" message. I tried to reinstall virtualbox packages but no luck, Additional info: * package version(s) virtualbox 5.2.12-1 virtualbox-host-dkms 5.2.12-1 linux 4.16.11-1-ARCH * config and/or log files etc. VirtualBox XPCOM Server 5.2.12 r122571 linux.amd64 (May 11 2018 09:07:05) release log 00:00:00.000157 main Log opened 2018-05-28T15:48:55.456746000Z 00:00:00.000158 main Build Type: release 00:00:00.000160 main OS Product: Linux 00:00:00.000161 main OS Release: 4.16.11-1-ARCH 00:00:00.000161 main OS Version: #1 SMP PREEMPT Tue May 22 21:40:27 UTC 2018 00:00:00.000176 main DMI Product Name: 80RS 00:00:00.000182 main DMI Product Version: Lenovo ideapad 300-15ISK 00:00:00.000210 main Host RAM: 15903MB (15.5GB) total, 12098MB (11.8GB) available 00:00:00.000212 main Executable: /usr/lib/virtualbox/VBoxSVC 00:00:00.000213 main Process ID: 7078 00:00:00.000213 main Package type: LINUX_64BITS_GENERIC (OSE) 00:00:00.001600 main IPC socket path: /tmp/.vbox-yurick-ipc/ipcd 00:00:00.109793 nspr-2 VirtualBox: object creation starts 00:00:00.110148 nspr-2 Home directory: '/home/yurick/.config/VirtualBox' 00:00:00.134852 nspr-2 Failed to retrive disk info: getDiskName(/dev/mapper/cryptroot) --> cryptroot 00:00:00.147366 nspr-2 NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for docker0: VBoxNetAdpCtl: ioctl failed: Operation not supported 00:00:00.167316 nspr-2 NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for wlp2s0: VBoxNetAdpCtl: ioctl failed: Operation not supported 00:00:00.168449 nspr-2 NAT: resolv.conf: nameserver 201.82.0.63 00:00:00.168468 nspr-2 NAT: resolv.conf: nameserver 201.82.0.68 00:00:00.168476 nspr-2 NAT: resolv.conf: nameserver 2804:14c:414:672:201:82:0:51 00:00:00.168483 nspr-2 NAT: resolv.conf: too many nameserver lines, ignoring 2804:14c:417:672:201:82:0:56 00:00:00.168497 nspr-2 HostDnsMonitor: old information 00:00:00.168501 nspr-2 no server entries 00:00:00.168505 nspr-2 no domain set 00:00:00.168509 nspr-2 no search string entries 00:00:00.168513 nspr-2 HostDnsMonitor: new information 00:00:00.168516 nspr-2 server 1: 201.82.0.63 00:00:00.168521 nspr-2 server 2: 201.82.0.68 00:00:00.168525 nspr-2 server 3: 2804:14c:414:672:201:82:0:51 00:00:00.168529 nspr-2 no domain set 00:00:00.168532 nspr-2 no search string entries 00:00:00.168538 nspr-2 HostDnsMonitorProxy::notify 00:00:00.173217 nspr-2 VD: VDInit finished with VINF_SUCCESS 00:00:00.173350 nspr-2 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={0eb668d2-495e-5a36-8890-29999b5f030c} aComponent={SystemPropertiesWrap} aText={Cannot determine default Guest Additions ISO location. Most likely they are not available}, preserve=false aResultDetail=0 00:00:00.177183 nspr-2 VirtualBox: object created 00:00:05.206037 main VirtualBox: object deletion starts 00:00:05.679427 Watcher ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={9570b9d5-f1a1-448a-10c5-e12f5285adad} aComponent={VirtualBoxWrap} aText={The object is not ready}, preserve=false aResultDetail=0 00:00:10.207025 main {00007f2dd4017c00} HostPowerServiceLinux::~HostPowerServiceLinux: RTThreadWait() for 5000 ms failed with VERR_TIMEOUT 00:00:10.208926 main VirtualBox: object deleted Steps to reproduce: Just try to launch virtualbox from console or by gnome menu |
This task depends upon
Closed by Toolybird (Toolybird)
Sunday, 16 April 2023, 01:59 GMT
Reason for closing: Fixed
Additional comments about closing: See comments
Sunday, 16 April 2023, 01:59 GMT
Reason for closing: Fixed
Additional comments about closing: See comments
As discussed in the https://bbs.archlinux.org/viewtopic.php?id=237449,
it's a bug with Qt5
Just removing the package 'qt5-wayland' makes virtualbox work again.
I hope it helps.
https://cgit.kde.org/krita.git/tree/krita/main.cc#n148
Since VB only works with xcb anyway this shouldn't cause problems for anyone.
$ QT_FONT_DPI=96 QT_QPA_PLATFORM=xcb VirtualBox
/* Force using Qt platform module 'xcb', we have X11 specific code: */
RTEnvSet("QT_QPA_PLATFORM", "xcb");
Therefore I assume the original crash is fixed.