Ticket #18767 (new defect)

Opened 18 months ago

Last modified 18 months ago

VirtualBox 6.0.10 segfaults at startup on CentOS 7.6

Reported by: gottschalk_maria Owned by:
Component: other Version: VirtualBox 6.0.10
Keywords: Cc:
Guest type: other Host type: Linux


> VirtualBox
Segmentation fault

Kernel logs this:

UINetworkReplyP[15063]: segfault at 2ad601cd1550 ip 00002ad629dc4f7e sp 00002ad6296ee2f8 error 7 in[2ad629d20000+2b9000]

My understanding is that 6.0.10 now somehow manages to load which is from KDE4. (I'm not using KDE4, I just have some KDE programs installed.)

First guess is it's triggered from here:

Downgrading to 6.0.8 makes Virtualbox work again.

Change History

comment:1 Changed 18 months ago by gottschalk_maria

It seems VirtualBox is now using libproxy, which contains a KDE4 module. This KDE4 module depends on Qt4 and loading it into a Qt5 program results in a segfault.

Workaround: yum remove libproxy-kde

comment:2 Changed 18 months ago by michael

I wonder whether this should be considered a bug in CentOS? EPEL seems to contain Qt5, so it is use case which ought to work.

comment:3 Changed 18 months ago by michael

comment:4 Changed 18 months ago by gottschalk_maria

RHEL/CentOS/OL have both qt4 and qt5 which can be installed in parallel. But there is only KDE4 which is qt4-based. Hence the KDE4 module for libproxy is also qt4-based. Loading it in a qt5 program results in the crash mentioned. One could argue this is a libproxy bug. But VirtualBox could live without libproxy until 6.0.10.

I'm using the official rpm for RHEL/CentOS/OL. It includes its own copy of qt5-5.6.x.

Last edited 18 months ago by gottschalk_maria (previous) (diff)
Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use