Bug 18802

Summary: X11 server cannot start in VBox - No devices detected - no screens found
Product: Mageia Reporter: Christian C <bugzzzz>
Component: RPM PackagesAssignee: Thomas Backlund <tmb>
Status: RESOLVED DUPLICATE QA Contact:
Severity: critical    
Priority: Normal CC: comptes.tsgeek, marja11, paulo, tmb
Version: Cauldron   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: virtualbox CVE:
Status comment:
Attachments: Xorg log file when the X11 server cannot start
/root/drakx/report.bug.xz when the X11 server cannot start
message à start up

Description Christian C 2016-06-27 23:45:37 CEST 
Description of problem:
After installing all the updates on a fresh install, the X11 server cannot start.

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


How reproducible:


Steps to Reproduce:
1. Install Mageia 6.dev1 into a VirtualBox VM.
2. Install all the update packages
3. Reboot
Comment 1 Christian C 2016-06-27 23:47:45 CEST 
Created attachment 8078 [details]
Xorg log file when the X11 server cannot start
Thierry Vignaud 2016-06-28 01:28:59 CEST

CC: (none) => tmb
Source RPM: (none) => x11-driver-video-vboxvideo

Comment 2 Marja Van Waes 2016-06-29 16:58:16 CEST 
Please attach /root/drakx/report.bug.xz of that install

CC: (none) => marja11
Assignee: bugsquad => tmb
Summary: X11 server cannot start => X11 server cannot start in VBox - No devices detected - no screens found
Source RPM: x11-driver-video-vboxvideo => virtualbox

Comment 3 Christian C 2016-06-29 17:31:52 CEST 
Created attachment 8090 [details]
/root/drakx/report.bug.xz when the X11 server cannot start
Comment 4 Marja Van Waes 2016-06-29 20:17:29 CEST 
I don't know why I assumed that the host runs Mageia, too. Does it? If so: which version?
Comment 5 Christian C 2016-06-29 20:25:31 CEST 
$ uname -a
Linux station 4.4.13-desktop-1.mga5 #1 SMP Fri Jun 10 12:16:55 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
$ rpm -qa | grep virtualbox
virtualbox-kernel-4.4.13-desktop-1.mga5-5.0.20-3.mga5
dkms-virtualbox-5.0.20-1.1.mga5
virtualbox-kernel-4.1.13-desktop-2.mga5-5.0.10-1.mga5
virtualbox-guest-additions-5.0.20-1.1.mga5
virtualbox-kernel-4.1.12-desktop-1.mga5-5.0.8-2.mga5
virtualbox-5.0.20-1.1.mga5
virtualbox-kernel-desktop-latest-5.0.20-3.mga5
Comment 6 Paulo Silva 2016-07-04 22:07:26 CEST 
The same with Mageia 6 sta1 i586.

I tried with fresh install and tried again after updates.

The host is Mageia 5 x86_64.

CC: (none) => paulo

Comment 7 David Walser 2016-07-06 21:05:13 CEST 
Duplicate.

Try removing /etc/X11/xorg.conf and/or adding the "nomodeset" option at the kernel command-line.

*** This bug has been marked as a duplicate of bug 18724 ***

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

Comment 8 Christian C 2016-07-07 00:19:35 CEST 
It seems that removing /etc/X11/xorg.conf resolves the problem
Comment 9 Christian C 2016-07-15 19:01:50 CEST 
The problem is not resolved in Mageia 6.sta1.
removing /etc/X11/xorg.conf resolves nothing.
"nomodeset" option resolves the problem.

Status: RESOLVED => REOPENED
Resolution: DUPLICATE => (none)

Comment 10 Christian C 2016-07-15 19:38:01 CEST 
but every time i reboot, the message in attachement is displayed.
Comment 11 Christian C 2016-07-15 19:39:07 CEST 
Created attachment 8184 [details]
message à start up
Comment 12 Thomas Backlund 2016-07-16 11:48:09 CEST 
can you as root do a:

echo "blacklist vboxvideo" >/etc/modprobe.d/vboxvideo.conf

and reboot...

does it boot up properly then without using "nomodeset" ?
Comment 13 Christian C 2016-07-16 12:51:32 CEST 
yes, this time, it boots properly
Comment 14 David Walser 2016-07-22 15:52:55 CEST 
Still a dup.

*** This bug has been marked as a duplicate of bug 18724 ***

Status: REOPENED => RESOLVED
Resolution: (none) => DUPLICATE

Comment 15 TheSuperGeek 2016-12-09 18:11:29 CET 
*** Bug 19919 has been marked as a duplicate of this bug. ***

CC: (none) => comptes.tsgeek