| Summary: | X won't start in VirtualBox | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Adrien D <email> |
| Component: | RPM Packages | Assignee: | Thomas Backlund <tmb> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | email, geiger.david68210, mageia, mageia, marja11, nicolas.salguero, shlomif, tukozaki |
| Version: | Cauldron | Keywords: | 6sta1 |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | virtualbox-5.0.18-1.mga6.src.rpm (x11-driver-video-vboxvideo) | CVE: | |
| Status comment: | |||
| Attachments: |
Picture to illustrate the problem
xorg.conf generated during installation xorg.conf generated by "Xorg -configure" log file of "Xorg -config xorg.conf.install" log file of "Xorg -config xorg.conf.new" log fine of "Xorg" without config file. |
||
|
Description
Adrien D
2016-04-25 07:58:43 CEST
Hi, I confirm this issue, same here on my Cauldron for x86_64 in a VB. Since I have updated my Cauldron yesterday I get this issue. Probably an xorg or vbox driver problem. CC:
(none) =>
geiger.david68210 I think it's a problem with VirtualBox Video Driver. I have Video if I made that : urpme x11-driver-video-vboxvideo and install vbox additions from official image downloaded from Oracle Website.
Adrien D
2016-04-25 11:33:21 CEST
Assignee:
bugsquad =>
tmb
Adrien D
2016-04-25 11:34:45 CEST
Source RPM:
x11-driver-video-vboxvideo =>
virtualbox-5.0.18-1.mga6.src.rpm (x11-driver-video-vboxvideo)
Rémi Verschelde
2016-04-25 13:18:16 CEST
Summary:
X won't start =>
X won't start in VirtualBox Hi, I had the same problem and found a solution by searching on the web: I had to remove "/etc/X11/xorg.conf" file (actually, I moved that file into "/etc/X11/xorg.conf.save"). Best regards, Nico. CC:
(none) =>
nicolas.salguero Could one of you provide a diff between /etc/X11/xorg.conf.save and /etc/X11/xorg.conf? That might help narrow down the issue. I have no /etc/X11/xorg.conf file anymore (mv /etc/X11/xorg.conf /etc/X11/xorg.conf.save). Ah, I assume a new one would be initialized when booting, but I guess nowadays Xorg can boot without this file. OK. mv /etc/X11/xorg.conf /etc/X11/xorg.conf.old => solve the problem. And [root@localhost ~]# LANG=C diff -rus /etc/X11/xorg.conf.old /etc/X11/xorg.conf diff: /etc/X11/xorg.conf: No such file or directory
Marja Van Waes
2016-05-03 16:13:53 CEST
Keywords:
(none) =>
6sta1 It happens with both 6sta1 x86-64 and 6st1 i586 VMs. (In reply to Nicolas Salguero from comment #6) > I have no /etc/X11/xorg.conf file anymore (mv /etc/X11/xorg.conf > /etc/X11/xorg.conf.save). I can confirm that moving away the file fixes the problam in 6sta1 i586 Classic DVD. However, after that I have a problem that the networking does not work until I do "service shorewall stop" as root. Hi, Thanks for the tip (mv /etc/X11...) to get X to start. For the network issue, another workaround is to go to the Network center, configure the connection, and allow users to manage it. Then I disconnect and reconnect it. And the network is up. CC:
(none) =>
mageia I've encountered the same issue.
Installing from Mageia-Cauldron-netinstall-nonfree-x86_64.iso into VirtualBox results in a system with broken Xorg configuration. The file Xorg.0.log shows some errors.
$ grep EE Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 1040.289] (EE) Failed to load module "vboxmouse" (module does not exist, 0)
[ 1040.308] (EE) No devices detected.
[ 1040.308] (EE)
[ 1040.308] (EE) no screens found(EE)
[ 1040.310] (EE)
[ 1040.310] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 1040.310] (EE)
Executing "Xorg -configure" and then trying to execute "Xorg -config /root/xorg.conf.new" also fails.
Removing the file /etc/X11/xorg.conf and then executing "startx" starts Xorg for a few seconds but then terminates without showing the desktop.
Executing "Xorg" starts Xorg and then to start Plasma I execute "DISPLAY=:0 startkde".
Will attach the following files:
xorg.conf.install - config file generated during installation
xorg.conf.new - config file generated by "Xorg -configure"
Xorg.0.log.install - log file of "Xorg -config xorg.conf.install"
Xorg.0.log.new - log file of "Xorg -config xorg.conf.new"
Xorg.0.log.noconfig - log fine of "Xorg" without config file.
Guest package versions:
# rpm -qa | grep -Ei 'kernel|virtualbox|vbox' | sort
kernel-desktop-4.6.2-1.mga6-1-1.mga6
kernel-desktop-latest-4.6.2-1.mga6
kernel-firmware-20160409-1.mga6
kernel-firmware-nonfree-20160516-1.mga6.nonfree
vboxadditions-kernel-4.6.2-desktop-1.mga6-5.0.22-1.mga6
vboxadditions-kernel-desktop-latest-5.0.22-1.mga6
virtualbox-guest-additions-5.0.22-1.mga6
x11-driver-video-vboxvideo-5.0.22-1.mga6
Host package versions:
$ rpm -qa | grep -Ei 'kernel|virtualbox|vbox' | sort
kernel-desktop-4.4.13-1.mga5-1-1.mga5
kernel-desktop-devel-4.4.13-1.mga5-1-1.mga5
kernel-desktop-devel-latest-4.4.13-1.mga5
kernel-desktop-latest-4.4.13-1.mga5
kernel-firmware-20160409-1.mga5
kernel-firmware-nonfree-20160516-1.mga5.nonfree
kernel-userspace-headers-4.4.13-1.mga5
nvidia340-kernel-desktop-latest-340.96-6.mga5.nonfree
virtualbox-5.0.22-1.mga5
virtualbox-kernel-4.4.13-desktop-1.mga5-5.0.22-1.mga5
virtualbox-kernel-desktop-latest-5.0.22-1.mga5
x11-driver-video-vboxvideo-5.0.22-1.mga5CC:
(none) =>
mageia Created attachment 8021 [details]
xorg.conf generated during installation
Created attachment 8022 [details]
xorg.conf generated by "Xorg -configure"
Created attachment 8023 [details]
log file of "Xorg -config xorg.conf.install"
Created attachment 8024 [details]
log file of "Xorg -config xorg.conf.new"
Created attachment 8025 [details]
log fine of "Xorg" without config file.
Woow, this issue still exists when booting Mageia 6 sta1 Netinstall that I installed yesterday evening in a VM (VESA driver, 1024x768px). Screenshot upon first boot after install : http://pic.al/sHd Solved as per comment #4. CC:
(none) =>
tukozaki Sometimes the "nomodeset" option on the kernel command line helps too. *** This bug has been marked as a duplicate of bug 18724 *** Status:
NEW =>
RESOLVED |