Black screen after installing virtualbox-guest-x11

Bug #1683043 reported by Ganton
60
This bug affects 10 people
Affects Status Importance Assigned to Milestone
virtualbox-guest-additions (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Congratulations for the 17.04 version. Using it in a Virtualbox virtual machine, if the virtualbox-guest-x11 package is installed: then, after rebooting the virtual machine, only a "black screen" is seen.

Then Host key + F1 works and programs can be executed there, although Host key + F7 keeps showing a "black screen".

The problem happens using a virtual machine with Ubuntu 17.04 or Kubuntu 17.04.

Revision history for this message
Ganton (ganton) wrote :
Revision history for this message
Ganton (ganton) wrote :
Ganton (ganton)
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in virtualbox-guest-additions (Ubuntu):
status: New → Confirmed
Revision history for this message
Mike (michbu) wrote :

Same problem here. The same problem also occurs, when installing the guest addons from the guest addons iso of the host.

I had the same problem in a machine after the update from a working 16.10.

Revision history for this message
Fernando (fmfzide) wrote :

Same error here after upgrading from 16.10 to 17.04:

$ cat Xorg.1.log | grep EE
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 102.177] (EE) Failed to load module "vboxvideo" (module does not exist, 0)
[ 102.178] (EE) Failed to load module "vboxvideo" (module does not exist, 0)
[ 102.180] (EE) open /dev/dri/card0: No such file or directory
[ 102.180] (EE) open /dev/dri/card0: No such file or directory
[ 102.180] (EE) open /dev/fb0: Permission denied
[ 102.180] (EE) open /dev/fb0: Permission denied
[ 102.180] (EE) Screen 0 deleted because of no matching config section.
[ 102.180] (EE) Screen 0 deleted because of no matching config section.
[ 102.205] (EE) VESA(0): Cannot read int vect
[ 102.205] (EE) Screen(s) found, but none have a usable configuration.
[ 102.205] (EE)
[ 102.205] (EE) no screens found(EE)
[ 102.206] (EE)
[ 102.206] (EE) Please also check the log file at "/home/millan/.local/share/xorg/Xorg.1.log" for additional information.
[ 102.206] (EE)
[ 102.217] (EE) Server terminated with error (1). Closing log file.

However, I have installed Kubuntu 17.04 in a new virtual machine and it works perfectly.

Revision history for this message
Fernando (fmfzide) wrote :

Sorry, I was wrong in my previous post and it seems I cannot edit it...

I uninstalled virtualbox-guest-x11 after upgrading and I wasn't able to use the full-screen mode and also I have some graphical glitches. I installed a new virtual machine and there are no graphical glitches and it works in full-screen mode. I supposed that the virtualbox-guest-x11 was installed but is not but the module vboxvideo is loaded.

Revision history for this message
Alexey Ivanov (alexey-ivanov) wrote :

VirtualBox 5.1.22 don't support xserver-xorg 1.19, only 1.18 at most, but somehow it loads on lightdm/unity, but not on gdm3 or gnome-session.

Revision history for this message
Alexey Ivanov (alexey-ivanov) wrote :

grep video /var/log/lightdm/x-0.log
(EE) vboxvideo: module ABI major version (20) doesn't match the server's version (23)

Revision history for this message
KIAaze (zohn-joidberg) wrote :

This also affects real machines, not only virtual ones.

After installing virtualbox-guest-x11:

At first I encountered this bug: https://forums.opensuse.org/showthread.php/518831-The-screen-locker-is-broken-and-unlocking-is-not-possible-anymore
I also noticed that "konsole" would not start anymore.
After logging out completely, I got the black screen.
The same happened after rebooting. Just a black screen, but the virtual terminals worked.

I fixed it by simply removing the package:
sudo apt purge virtualbox-guest-x11

Revision history for this message
KIAaze (zohn-joidberg) wrote :
Revision history for this message
KIAaze (zohn-joidberg) wrote :

grep EE /var/log/Xorg.* output

Revision history for this message
leonardo (leonardoapolinario) wrote :

The same here. Using Kubuntu 17.10 on a VirtualBox Machine. After install virtualbox-guest-x11 only "black" screen is seen. If I use alt+ f2 I can use Konsole (terminal). If I uninstall virtualbox-guest-x11 the system loads normally.

Revision history for this message
leonardo (leonardoapolinario) wrote :

grep EE /var/log/Xorg.* output

output
/var/log/Xorg.0.log: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
/var/log/Xorg.0.log:[ 53.688] (EE) Failed to load module "vboxvideo" (module does not exist, 0)
/var/log/Xorg.0.log:[ 53.884] (EE) Failed to load module "vboxvideo" (module does not exist, 0)
/var/log/Xorg.0.log:[ 60.882] (EE) modeset(0): glamor initialization failed
/var/log/Xorg.0.log:[ 60.963] (EE) AIGLX: reverting to software rendering
/var/log/Xorg.0.log:[ 62.113] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb2/2-1/2-1:1.0/0003:80EE:0021.0001/input/input6/event5"
/var/log/Xorg.0.log.old: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
/var/log/Xorg.0.log.old:[ 1508.580] (EE) Failed to load module "vboxvideo" (module does not exist, 0)
/var/log/Xorg.0.log.old:[ 1508.655] (EE) Failed to load module "vboxvideo" (module does not exist, 0)
/var/log/Xorg.0.log.old:[ 1508.817] (EE) modeset(0): glamor initialization failed
/var/log/Xorg.0.log.old:[ 1508.828] (EE) AIGLX: reverting to software rendering
/var/log/Xorg.0.log.old:[ 1509.176] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb2/2-1/2-1:1.0/0003:80EE:0021.0001/input/input6/event5"
grep: output: No such file or directory

Revision history for this message
Tony Middleton (ximera) wrote :

This problem seems to have gone away on 18.04.

Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

lets close it, I already fixed it

Changed in virtualbox-guest-additions (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Tony Middleton (ximera) wrote :

This problem now seems to have arisen in a recently updated 16.04 system.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.