#2074 closed defect (fixed)
blue screen xorg error: problems when starting Lubuntu 18.4. or OSGeoLive 12 alpha1 with virtual box
Reported by: | astrid_emde | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | OSGeoLive12.0 |
Component: | OSGeoLive | Keywords: | |
Cc: | osgeolive@… |
Description
when you run OSGeoLive builds with virtual box (without installation) it can happen, that you get stuck in a blue screen. Then it can help to type Right Ctrl F1 & Right Ctrl F7. But in some cases this does not help and you can't start OSGeoLive
- the issue was tested alpha1 (2018-06-11) and http://cdimage.ubuntu.com/lubuntu/releases/18.04/release/
Steps to reproduce
- Download http://aiolos.survey.ntua.gr/gisvm/12.0/
- create a virtual machine with virtual box (Linux/Ubuntu64 bit)
- start and choose the iso
- choose the language
- can see the screen Lubuntu 18.4
- but then the blue screen shows up and nothing else happens
Attachments (5)
Change History (20)
comment:1 by , 6 years ago
by , 6 years ago
Attachment: | Screen Shot 2018-06-23 at 9.16.22 am.png added |
---|
VirtualBox settings with Lubuntu 18.04 image
by , 6 years ago
Attachment: | Screen Shot 2018-06-23 at 9.23.31 am.png added |
---|
Final fuzzy - non-rendered Lubuntu desktop page
comment:2 by , 6 years ago
I've reported this issue upstream at: https://bugs.launchpad.net/lubuntu-artwork/+bug/1778309
comment:3 by , 6 years ago
- tested with beta1.: Error still occurs when you run Lubuntu without installation -> shortcut helps Right Ctrl F3 & Right Ctrl F7.
comment:5 by , 6 years ago
Cc: | added |
---|---|
Priority: | normal → critical |
comment:6 by , 6 years ago
Just confirmed that this issue is not valid with latest Virtual Box (5.2.10) on a Linux host. Can someone please test the latest version of VirtualBox on Windows and Mac?
comment:7 by , 6 years ago
Tested osgeolive-nightly-build200-amd64-34cddf6-master.iso On windows 10 professional machine.
No issues with the iso, no blue screen, window resizing works correctly
It is a intel corei5 machine with intel hd graphics 530 video chipset. so pretty basic Forgot to check the virtualbox version, not the latest as it proposed to update. Probably 4 to 6 months old.
comment:8 by , 6 years ago
The recent beta2 started fine in Virtualbox 5.2.8 on a Windows 7 host. No issues with blue screen. The desktop resized automatically (Vbox additions already installed). Nice...
comment:9 by , 6 years ago
Thanks! We need someone to confirm this works on Mac in order to dismiss this ticket.
comment:10 by , 6 years ago
We still need a volunteer with a Mac to test latest VirtualBox and latest beta.
comment:11 by , 6 years ago
I had the same issue - see mailing list: https://lists.osgeo.org/pipermail/osgeolive/2018-August/013433.html
I needed to "Enable 3D Acceleration" in the settings: https://imgur.com/a/XxaudE0
This was not the case for OSGeoLive 11 so I guess this should be added to the installation notes?
PC details which may be relevant:
Operating System: Windows 10 Pro 64-bit (10.0, Build 17134) (17134.rs4_release.180410-1804) Card name: NVIDIA GeForce GTX 1060 6GB Manufacturer: NVIDIA Chip type: GeForce GTX 1060 6GB Processor: Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz (8 CPUs), ~3.6GHz User DPI Setting: 96 DPI (100 percent) System DPI Setting: 96 DPI (100 percent) DWM DPI Scaling: Disabled
comment:13 by , 6 years ago
Priority: | critical → major |
---|
comment:14 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Could not replicate the issue on 12.0 vm version
comment:15 by , 6 years ago
This issue seems to be Ubuntu related, it appends in Ubuntu MATE as well:
https://ubuntu-mate.org/blog/ubuntu-mate-cosmic-beta/
"This appears to impact Ubuntu (proper) more than Ubuntu MATE. It is an intermitent problem on Ubuntu MATE and simply resetting the VM may work on the next boot. If not, press a key when the initial boot prompt (Man and Keyboard) is displayed, then press F6 and select nomodeset and press ENTER to boot."
Bug report: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1792932
To clarify for external readers, the OSGeo-Live image we use is based upon Lubuntu 18.04, and I have been able to reproduce our problem with a raw Lubuntu 18.04 image, confirming this is an upstream issue with Lubuntu rather than an issue with OSGeo-Live (which is based on Lubuntu). Steps I've used:
Attached are screen shots of this sequence.