Bug 23022 - mageia 5.1 KDE4 live->6 x86-64 vbox net upgrade results in non starting DM and screen flicker (modprobe: ERROR: could not insert 'vboxvideo': Invalid argument)
Summary: mageia 5.1 KDE4 live->6 x86-64 vbox net upgrade results in non starting DM an...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-12 16:17 CEST by Shlomi Fish
Modified: 2019-06-07 21:45 CEST (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
A screenshot of trying to build vboxvideo (40.40 KB, image/png)
2018-05-12 16:49 CEST, Shlomi Fish
Details

Description Shlomi Fish 2018-05-12 16:17:43 CEST
Description of problem:

I installed mageia 5.1 KDE4 live. installed all updates and then did a command line urpmi upgrade to 6 x86-64, inside a vbox VM and this resulted in non starting DM and screen flicker in Ctrl+alt+f2 and other virtual consoles. I used  this mirror - http://mirror.isoc.org.il/pub/mageia/distrib/6/x86_64/ .

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
Comment 1 Shlomi Fish 2018-05-12 16:49:24 CEST
Created attachment 10143 [details]
A screenshot of trying to build vboxvideo
Comment 2 Shlomi Fish 2018-05-12 18:35:04 CEST
I should also note that startx currently fails.
Marja Van Waes 2018-05-13 13:31:42 CEST

Assignee: bugsquad => kernel
Summary: mageia 5.1 KDE4 live->6 x86-64 vbox net upgrade results in non starting DM and screen flicker => mageia 5.1 KDE4 live->6 x86-64 vbox net upgrade results in non starting DM and screen flicker (modprobe: ERROR: could not insert 'vboxvideo': Invalid argument)
CC: (none) => marja11, tmb

Comment 3 Shlomi Fish 2018-05-18 23:11:02 CEST
A few more discoveries:

1. The vbox guest additions CD exhibits the same problem.

2. Upgrading all packages to updates-testing and rebooting does not fix the problem either.

3. A different VM with mageia 6 x86-64 installed from 6 runs X fine.
Comment 4 Shlomi Fish 2019-06-07 21:45:05 CEST
mageia 5 was EOLed.

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.