| Summary: | VBoxClient segfaults | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Marc Krämer <mageia> |
| Component: | RPM Packages | Assignee: | Thomas Backlund <tmb> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | davidwhodgins, ouaurelien |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | virtualbox-6.1.4-2.mga8.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Marc Krämer
2020-04-16 16:52:57 CEST
OK to assign this directly to you, Thomas? Assignee:
bugsquad =>
tmb What, if anything other then booting is being done to trigger the segfault? On my m7 host running 5.5.15-desktop-3.mga7 using the radeon video kernel module, with an m8 guest running 5.6.4-desktop-1.mga8, no segfault here. Adding audit=0 to the kernel parameters suppresses the audit messages from the journal. Based on the libX11.so.6.3.0 library, I gather the segfault was in the host, but virtualbox rpm package on m7 is virtualbox-6.0.18-1.mga7 Is an cauldron version of the virtualbox package being used on a Mageia 7 system? CC:
(none) =>
davidwhodgins to clarify: Host: mga7, kernel: 5.5.15-desktop-3.mga7, video: intel_drv.so, virtualbox: dkms-virtualbox-6.0.18-1.mga7.noarch virtualbox-6.0.18-1.mga7.x86_64 virtualbox-kernel-5.5.15-desktop-3.mga7-6.0.18-11.mga7.x86_64 Client: mag8, kernel: 5.6.4-desktop-1.mga8, video virtualbox: virtualbox-guest-additions-6.1.4-2.mga8.x86_64 just noticed the above entry be accident in journal. Yeah, I will switch Mageia 7 to the 6.1 branch too in order to get better support / co-existence with Mga7 and Mga8 / Cauldron. It should probably hit testing repos today / tomorrow Fixed. Updated Virtualbox version has landed M7. Status:
NEW =>
RESOLVED |