Description of problem: I have installed Cauldron using netinstall iso on VirtualBox and installed plasma desktop. The graphical session fails to start with only blank screen shown. This is same for both wayland and x11. Starting X using 'tty' shows the server crashes with error: "(EE) Failed to load module .../vmware_drv.so: undefined symbol: vgaHWGetIndex". I downgraded to version released to Mageia 9 (`x11-driver-video-vmware-13.4.0-1.mga9.rpm`) and that fixes the issue. Version-Release number of selected component (if applicable): x11-driver-video-vmware-13.4.0-2.mga10.rpm How reproducible: Each login attempt fails. Steps to Reproduce: 1. Install cauldron on VirtualBox 2. Install graphical desktop (I installed Plasma) 3. Try to login (wayland and x11 session both fail)
Try again with x11-driver-video-vmware-13.4.0-3 available in mirrors anytime soon.
Thank you Sam for the report, and Jani for the encouraging comment. Sam: please report back when you have tried the update. If it works, you can close the bug.
Assignee: bugsquad => kernelCC: (none) => lewyssmith
It didn't affected the the building, however it remained a typo on top of SPEC file, at line 3, after %global _disable_ld_now 1... https://svnweb.mageia.org/packages/cauldron/x11-driver-video-vmware/current/SPECS/x11-driver-video-vmware.spec?revision=2263744&view=markup#l3
CC: (none) => ghibomgx
(In reply to Giuseppe Ghibò from comment #3) > It didn't affected the the building, however it remained a typo on top of > SPEC file, at line 3, after %global _disable_ld_now 1... > > https://svnweb.mageia.org/packages/cauldron/x11-driver-video-vmware/current/ > SPECS/x11-driver-video-vmware.spec?revision=2263744&view=markup#l3 Typo is now fixed in SVN.
Thanks. As a reminder if someone has time, and since this seems recursive lately, maybe we could add some note for the _disable_ld_now usage either in https://wiki.mageia.org/en/Underlinking_issues_in_packaging and/or https://wiki.mageia.org/en/Overlinking_issues_in_packaging
Hi all, Apologies for late reply. With the latest build the issue is resolved. Thank you very much.
(In reply to Lewis Smith from comment #2) > Thank you Sam for the report, and Jani for the encouraging comment. > > Sam: please report back when you have tried the update. If it works, you can > close the bug. Hi Lewis, Sorry, I tried to close the bug but instead ended up commenting twice. First time, I commented without changing the 'Status'. Second time, I did update the 'Status' before clicking 'Save Changes', but still the status is not updated.
Closing as FIXED.
Resolution: (none) => FIXEDCC: (none) => jani.valimaaStatus: NEW => RESOLVED