Graphics horribly corrupted on Ubuntu 16.04 in VirtualBox, showing random strips of pixelated colors
up vote
12
down vote
favorite
Inside a VirtualBox VM, I have installed myself an Ubuntu 16.04.1 LTS Server installation. However, when I installed the ubuntu-desktop package and rebooted, this happened:
Exact command I used: sudo apt-get update; sudo apt-get install ubuntu-desktop
..and then a reboot command.
This just seems like a corrupted top-left portion of the screen, as my cursor can appear in view (but corrupted):
This is a purely graphical issue because I can use the keyboard to successfully progress to a desktop:
Note: On startup it shows correct graphics for a split-second then reverts to glitch.
Any help on this?
server apt virtualbox desktop-environments
edited Nov 2 at 4:50
karel
56k11124142
asked Jan 5 '17 at 14:01
Dev
336420
|
show 1 more comment
up vote
12
down vote
favorite
Inside a VirtualBox VM, I have installed myself an Ubuntu 16.04.1 LTS Server installation. However, when I installed the ubuntu-desktop package and rebooted, this happened:
Exact command I used: sudo apt-get update; sudo apt-get install ubuntu-desktop
..and then a reboot command.
This just seems like a corrupted top-left portion of the screen, as my cursor can appear in view (but corrupted):
This is a purely graphical issue because I can use the keyboard to successfully progress to a desktop:
Note: On startup it shows correct graphics for a split-second then reverts to glitch.
Any help on this?
server apt virtualbox desktop-environments
edited Nov 2 at 4:50
karel
56k11124142
asked Jan 5 '17 at 14:01
Dev
336420
Note that the screen is perfectly fine for a split second after the machine starts everything. Then the resolution messes up and the graphics die.
– Dev
Jan 5 '17 at 14:02
The pattern of visual defects in your screenshots is similar defects that are caused by a bad stick of RAM memory in a physical machine. As a troubleshooting device please try to add more RAM to the virtual machine and check if the problem goes away.
– karel
Jan 5 '17 at 14:08
I gave it 128 MB of graphics memory and 12 GB of RAM - for a split second it did show the login screen like before (snagged a screenshot here) but after that, this happened again
– Dev
Jan 5 '17 at 14:12
Possibly. Maybe this is why Google Chrome has been killing random tabs. Let me try giving it less RAM then.
– Dev
Jan 5 '17 at 14:14
Same result. Proper screen for a split-second and then this.
– Dev
Jan 5 '17 at 14:15
|
show 1 more comment
up vote
12
down vote
favorite
up vote
12
down vote
favorite
Inside a VirtualBox VM, I have installed myself an Ubuntu 16.04.1 LTS Server installation. However, when I installed the ubuntu-desktop package and rebooted, this happened:
Exact command I used: sudo apt-get update; sudo apt-get install ubuntu-desktop
..and then a reboot command.
This just seems like a corrupted top-left portion of the screen, as my cursor can appear in view (but corrupted):
This is a purely graphical issue because I can use the keyboard to successfully progress to a desktop:
Note: On startup it shows correct graphics for a split-second then reverts to glitch.
Any help on this?
server apt virtualbox desktop-environments
edited Nov 2 at 4:50
karel
56k11124142
asked Jan 5 '17 at 14:01
Dev
336420
Inside a VirtualBox VM, I have installed myself an Ubuntu 16.04.1 LTS Server installation. However, when I installed the ubuntu-desktop package and rebooted, this happened:
Exact command I used: sudo apt-get update; sudo apt-get install ubuntu-desktop
..and then a reboot command.
This just seems like a corrupted top-left portion of the screen, as my cursor can appear in view (but corrupted):
This is a purely graphical issue because I can use the keyboard to successfully progress to a desktop:
Note: On startup it shows correct graphics for a split-second then reverts to glitch.
Any help on this?
server apt virtualbox desktop-environments
server apt virtualbox desktop-environments
edited Nov 2 at 4:50
karel
56k11124142
asked Jan 5 '17 at 14:01
Dev
336420
edited Nov 2 at 4:50
karel
56k11124142
asked Jan 5 '17 at 14:01
Dev
336420
edited Nov 2 at 4:50
karel
56k11124142
edited Nov 2 at 4:50
karel
56k11124142
edited Nov 2 at 4:50
karel
56k11124142
56k11124142
asked Jan 5 '17 at 14:01
Dev
336420
asked Jan 5 '17 at 14:01
Dev
336420
asked Jan 5 '17 at 14:01
Dev
336420
336420
Note that the screen is perfectly fine for a split second after the machine starts everything. Then the resolution messes up and the graphics die.
– Dev
Jan 5 '17 at 14:02
The pattern of visual defects in your screenshots is similar defects that are caused by a bad stick of RAM memory in a physical machine. As a troubleshooting device please try to add more RAM to the virtual machine and check if the problem goes away.
– karel
Jan 5 '17 at 14:08
I gave it 128 MB of graphics memory and 12 GB of RAM - for a split second it did show the login screen like before (snagged a screenshot here) but after that, this happened again
– Dev
Jan 5 '17 at 14:12
Possibly. Maybe this is why Google Chrome has been killing random tabs. Let me try giving it less RAM then.
– Dev
Jan 5 '17 at 14:14
Same result. Proper screen for a split-second and then this.
– Dev
Jan 5 '17 at 14:15
|
show 1 more comment
Note that the screen is perfectly fine for a split second after the machine starts everything. Then the resolution messes up and the graphics die.
– Dev
Jan 5 '17 at 14:02
The pattern of visual defects in your screenshots is similar defects that are caused by a bad stick of RAM memory in a physical machine. As a troubleshooting device please try to add more RAM to the virtual machine and check if the problem goes away.
– karel
Jan 5 '17 at 14:08
I gave it 128 MB of graphics memory and 12 GB of RAM - for a split second it did show the login screen like before (snagged a screenshot here) but after that, this happened again
– Dev
Jan 5 '17 at 14:12
Possibly. Maybe this is why Google Chrome has been killing random tabs. Let me try giving it less RAM then.
– Dev
Jan 5 '17 at 14:14
Same result. Proper screen for a split-second and then this.
– Dev
Jan 5 '17 at 14:15
Note that the screen is perfectly fine for a split second after the machine starts everything. Then the resolution messes up and the graphics die.
– Dev
Jan 5 '17 at 14:02
Note that the screen is perfectly fine for a split second after the machine starts everything. Then the resolution messes up and the graphics die.
– Dev
Jan 5 '17 at 14:02
The pattern of visual defects in your screenshots is similar defects that are caused by a bad stick of RAM memory in a physical machine. As a troubleshooting device please try to add more RAM to the virtual machine and check if the problem goes away.
– karel
Jan 5 '17 at 14:08
The pattern of visual defects in your screenshots is similar defects that are caused by a bad stick of RAM memory in a physical machine. As a troubleshooting device please try to add more RAM to the virtual machine and check if the problem goes away.
– karel
Jan 5 '17 at 14:08
I gave it 128 MB of graphics memory and 12 GB of RAM - for a split second it did show the login screen like before (snagged a screenshot here) but after that, this happened again
– Dev
Jan 5 '17 at 14:12
I gave it 128 MB of graphics memory and 12 GB of RAM - for a split second it did show the login screen like before (snagged a screenshot here) but after that, this happened again
– Dev
Jan 5 '17 at 14:12
Possibly. Maybe this is why Google Chrome has been killing random tabs. Let me try giving it less RAM then.
– Dev
Jan 5 '17 at 14:14
Possibly. Maybe this is why Google Chrome has been killing random tabs. Let me try giving it less RAM then.
– Dev
Jan 5 '17 at 14:14
Same result. Proper screen for a split-second and then this.
– Dev
Jan 5 '17 at 14:15
Same result. Proper screen for a split-second and then this.
– Dev
Jan 5 '17 at 14:15
|
show 1 more comment
3 Answers
3
active
oldest
votes
up vote
18
down vote
accepted
I have also experienced this problem before and it is easy to work around:
Press CtrlAltF3 to switch to text terminal and then CtrlAltF7 to switch back to GUI (alternatively CtrlAltF1 in the case of some newer Ubuntu versions – simply try it if CtrlAltF7 does not work).
If your host is Linux, too, the mentioned keystrokes will influence the host machine. Use the Host key instead of CtrlAlt to influence the guest.
References:
- https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1443853
- https://www.virtualbox.org/ticket/13615
- How do I switch between console mode and GUI in 17.10 and newer?
answered Jan 5 '17 at 15:11
Melebius
4,22251837
1
I had the same problem with Linux Mint and this works for that too.
– Mark
Dec 20 '17 at 23:26
With an Ubuntu 18.04 or 18.10 Guest, you need to use <CTRL>-<HOST-KEY>-<F2> followed by <CTRL>-<HOST-KEY>-<F1>.
– PJ Singh
Oct 8 at 23:37
add a comment |
up vote
3
down vote
This may be obvious to some, but in my instance (Ubuntu Host), Ctrl+Alt+F1 switched the entire host video mode, and switching back didn't change the status of the guest video. The trick was to use HOST+F1 (e.g. the RIGHT Ctrl key, no ALT), and then HOST+F7 to switch back.
edited Oct 23 at 11:07
Melebius
4,22251837
answered May 24 '17 at 14:57
jpa
311
add a comment |
up vote
1
down vote
Hit this scrambled/distorted screen today with 18.04 installer. I fixed it by increasing the video memory of the VM.
answered Oct 26 at 15:28
jws
1111
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f868347%2fgraphics-horribly-corrupted-on-ubuntu-16-04-in-virtualbox-showing-random-strips%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
18
down vote
accepted
I have also experienced this problem before and it is easy to work around:
Press CtrlAltF3 to switch to text terminal and then CtrlAltF7 to switch back to GUI (alternatively CtrlAltF1 in the case of some newer Ubuntu versions – simply try it if CtrlAltF7 does not work).
If your host is Linux, too, the mentioned keystrokes will influence the host machine. Use the Host key instead of CtrlAlt to influence the guest.
References:
- https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1443853
- https://www.virtualbox.org/ticket/13615
- How do I switch between console mode and GUI in 17.10 and newer?
answered Jan 5 '17 at 15:11
Melebius
4,22251837
1
I had the same problem with Linux Mint and this works for that too.
– Mark
Dec 20 '17 at 23:26
With an Ubuntu 18.04 or 18.10 Guest, you need to use <CTRL>-<HOST-KEY>-<F2> followed by <CTRL>-<HOST-KEY>-<F1>.
– PJ Singh
Oct 8 at 23:37
add a comment |
up vote
18
down vote
accepted
I have also experienced this problem before and it is easy to work around:
Press CtrlAltF3 to switch to text terminal and then CtrlAltF7 to switch back to GUI (alternatively CtrlAltF1 in the case of some newer Ubuntu versions – simply try it if CtrlAltF7 does not work).
If your host is Linux, too, the mentioned keystrokes will influence the host machine. Use the Host key instead of CtrlAlt to influence the guest.
References:
- https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1443853
- https://www.virtualbox.org/ticket/13615
- How do I switch between console mode and GUI in 17.10 and newer?
answered Jan 5 '17 at 15:11
Melebius
4,22251837
1
I had the same problem with Linux Mint and this works for that too.
– Mark
Dec 20 '17 at 23:26
With an Ubuntu 18.04 or 18.10 Guest, you need to use <CTRL>-<HOST-KEY>-<F2> followed by <CTRL>-<HOST-KEY>-<F1>.
– PJ Singh
Oct 8 at 23:37
add a comment |
up vote
18
down vote
accepted
up vote
18
down vote
accepted
I have also experienced this problem before and it is easy to work around:
Press CtrlAltF3 to switch to text terminal and then CtrlAltF7 to switch back to GUI (alternatively CtrlAltF1 in the case of some newer Ubuntu versions – simply try it if CtrlAltF7 does not work).
If your host is Linux, too, the mentioned keystrokes will influence the host machine. Use the Host key instead of CtrlAlt to influence the guest.
References:
- https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1443853
- https://www.virtualbox.org/ticket/13615
- How do I switch between console mode and GUI in 17.10 and newer?
answered Jan 5 '17 at 15:11
Melebius
4,22251837
I have also experienced this problem before and it is easy to work around:
Press CtrlAltF3 to switch to text terminal and then CtrlAltF7 to switch back to GUI (alternatively CtrlAltF1 in the case of some newer Ubuntu versions – simply try it if CtrlAltF7 does not work).
If your host is Linux, too, the mentioned keystrokes will influence the host machine. Use the Host key instead of CtrlAlt to influence the guest.
References:
- https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1443853
- https://www.virtualbox.org/ticket/13615
- How do I switch between console mode and GUI in 17.10 and newer?
answered Jan 5 '17 at 15:11
Melebius
4,22251837
edited Dec 10 at 7:37
answered Jan 5 '17 at 15:11
Melebius
4,22251837
answered Jan 5 '17 at 15:11
Melebius
4,22251837
answered Jan 5 '17 at 15:11
Melebius
4,22251837
4,22251837
1
I had the same problem with Linux Mint and this works for that too.
– Mark
Dec 20 '17 at 23:26
With an Ubuntu 18.04 or 18.10 Guest, you need to use <CTRL>-<HOST-KEY>-<F2> followed by <CTRL>-<HOST-KEY>-<F1>.
– PJ Singh
Oct 8 at 23:37
add a comment |
1
I had the same problem with Linux Mint and this works for that too.
– Mark
Dec 20 '17 at 23:26
With an Ubuntu 18.04 or 18.10 Guest, you need to use <CTRL>-<HOST-KEY>-<F2> followed by <CTRL>-<HOST-KEY>-<F1>.
– PJ Singh
Oct 8 at 23:37
1
1
I had the same problem with Linux Mint and this works for that too.
– Mark
Dec 20 '17 at 23:26
I had the same problem with Linux Mint and this works for that too.
– Mark
Dec 20 '17 at 23:26
With an Ubuntu 18.04 or 18.10 Guest, you need to use <CTRL>-<HOST-KEY>-<F2> followed by <CTRL>-<HOST-KEY>-<F1>.
– PJ Singh
Oct 8 at 23:37
With an Ubuntu 18.04 or 18.10 Guest, you need to use <CTRL>-<HOST-KEY>-<F2> followed by <CTRL>-<HOST-KEY>-<F1>.
– PJ Singh
Oct 8 at 23:37
add a comment |
up vote
3
down vote
This may be obvious to some, but in my instance (Ubuntu Host), Ctrl+Alt+F1 switched the entire host video mode, and switching back didn't change the status of the guest video. The trick was to use HOST+F1 (e.g. the RIGHT Ctrl key, no ALT), and then HOST+F7 to switch back.
edited Oct 23 at 11:07
Melebius
4,22251837
answered May 24 '17 at 14:57
jpa
311
add a comment |
up vote
3
down vote
This may be obvious to some, but in my instance (Ubuntu Host), Ctrl+Alt+F1 switched the entire host video mode, and switching back didn't change the status of the guest video. The trick was to use HOST+F1 (e.g. the RIGHT Ctrl key, no ALT), and then HOST+F7 to switch back.
edited Oct 23 at 11:07
Melebius
4,22251837
answered May 24 '17 at 14:57
jpa
311
add a comment |
up vote
3
down vote
up vote
3
down vote
This may be obvious to some, but in my instance (Ubuntu Host), Ctrl+Alt+F1 switched the entire host video mode, and switching back didn't change the status of the guest video. The trick was to use HOST+F1 (e.g. the RIGHT Ctrl key, no ALT), and then HOST+F7 to switch back.
edited Oct 23 at 11:07
Melebius
4,22251837
answered May 24 '17 at 14:57
jpa
311
This may be obvious to some, but in my instance (Ubuntu Host), Ctrl+Alt+F1 switched the entire host video mode, and switching back didn't change the status of the guest video. The trick was to use HOST+F1 (e.g. the RIGHT Ctrl key, no ALT), and then HOST+F7 to switch back.
edited Oct 23 at 11:07
Melebius
4,22251837
answered May 24 '17 at 14:57
jpa
311
edited Oct 23 at 11:07
Melebius
4,22251837
edited Oct 23 at 11:07
Melebius
4,22251837
edited Oct 23 at 11:07
Melebius
4,22251837
4,22251837
answered May 24 '17 at 14:57
jpa
311
answered May 24 '17 at 14:57
jpa
311
answered May 24 '17 at 14:57
jpa
311
311
add a comment |
add a comment |
up vote
1
down vote
Hit this scrambled/distorted screen today with 18.04 installer. I fixed it by increasing the video memory of the VM.
answered Oct 26 at 15:28
jws
1111
add a comment |
up vote
1
down vote
Hit this scrambled/distorted screen today with 18.04 installer. I fixed it by increasing the video memory of the VM.
answered Oct 26 at 15:28
jws
1111
add a comment |
up vote
1
down vote
up vote
1
down vote
Hit this scrambled/distorted screen today with 18.04 installer. I fixed it by increasing the video memory of the VM.
answered Oct 26 at 15:28
jws
1111
Hit this scrambled/distorted screen today with 18.04 installer. I fixed it by increasing the video memory of the VM.
answered Oct 26 at 15:28
jws
1111
answered Oct 26 at 15:28
jws
1111
answered Oct 26 at 15:28
jws
1111
answered Oct 26 at 15:28
jws
1111
1111
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f868347%2fgraphics-horribly-corrupted-on-ubuntu-16-04-in-virtualbox-showing-random-strips%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Note that the screen is perfectly fine for a split second after the machine starts everything. Then the resolution messes up and the graphics die.
– Dev
Jan 5 '17 at 14:02
The pattern of visual defects in your screenshots is similar defects that are caused by a bad stick of RAM memory in a physical machine. As a troubleshooting device please try to add more RAM to the virtual machine and check if the problem goes away.
– karel
Jan 5 '17 at 14:08
I gave it 128 MB of graphics memory and 12 GB of RAM - for a split second it did show the login screen like before (snagged a screenshot here) but after that, this happened again
– Dev
Jan 5 '17 at 14:12
Possibly. Maybe this is why Google Chrome has been killing random tabs. Let me try giving it less RAM then.
– Dev
Jan 5 '17 at 14:14
Same result. Proper screen for a split-second and then this.
– Dev
Jan 5 '17 at 14:15