Score:53

Terminal not opening on Ubuntu 22.04 on Virtual box 7.0.0

nl flag
yun

I'm using windows 10 and I installed Ubuntu 22.04 on Virtual box 7.0.0.

When I click the terminal icon, the upper left side of the screen(where is the executing application name view), there is the title 'Terminal' and a turning arrow that indicates it's launching.

enter image description here

But somehow it blows away and the terminal is not opening and really executing.

I'm not sure it's about Ubuntu or Virtual machine too. How can I fix this?

David avatar
cn flag
From your question "But somehow it blows away and the terminal is not opening and really executing." can you explain what this means?
yun avatar
nl flag
yun
David, sorry for the confusing writing. I meant the 'terminal' letter and arrow disappear while the terminal is not opening and not executing.
yun avatar
nl flag
yun
ChanganAuto, I tried CTRL+ALT+T but it didn't work. My Ubuntu and Virtualbox are up to date. The extension pack and guest additions are also installed.
ChanganAuto avatar
us flag
So, what exactly you've done since installing Ubuntu? Did you perhaps tried to change the phyton version?
yun avatar
nl flag
yun
ChanganAuto, I did change nothing after installing Ubuntu. After installing it, I started the terminal right away, but the situation above happened. So I updated the Ubuntu through GUI and installed the lastest extention package of Virtual box that is for my version, but nothing changed.
ozeray avatar
ru flag
Simplest solution: https://www.youtube.com/watch?v=NvTMQBxGqDw
Taha Malik avatar
au flag
Creating another administrator account solved my problem.
Score:32
li flag

Same on vbox 7.0, I had fixed it adding en_US.UTF-8 instead of en_US to the /etc/default/locale then sudo locale-gen --purge and reboot.

MargaretM avatar
al flag
Method of Mike Lugin works. I changed the language (just to another one, I chose UK) in the UI Settings -> Language and Region, the VM restarted and Terminal works.
nicodp avatar
bw flag
@MargaretM Thanks, this worked!
Alex avatar
uz flag
I can not open a terminal -> Go open a terminal and do the following XD
LandonZeKepitelOfGreytBritn avatar
cn flag
Did not work for me
FlorianH avatar
vn flag
How to edit /etc/default/locale when I don't have Terminal to run, e.g., `sudo gedit /etc/default/locale` ? I can launch gedit from the menu, but then seem to lack the 'sudo' rights required to save the changes to /etc/default/locale
Mike Lugin avatar
li flag
Hi @FlorianH, try to switch session using (CTRL+ALT+F3), it will promt you to a cli where you can use sudo, then you can edit locale using nano and switch back to GUI using (CTRL+ALT+F1).
FlorianH avatar
vn flag
Thanks @Mike Lugin, sounds like it might have worked. In the meantime instead I simply evaded the issue by re-installing my Virtualbox@Win10 installation of Ubuntu16.04 first _without Guest Additions_, before adding them post-hoc.
orique avatar
ru flag
I could do the change using GUI by going to Settings > Region & Language, then setting all to US.
tutiplain avatar
mt flag
This worked. I just can't believe that Ubuntu would ship out a build with such obviously wrong configurations.
mLstudent33 avatar
ph flag
How do you do this without terminal?
in flag
As suggested, changing the language from Settings menu fixed the problem. The default was en-US, I have changed to Türkçe.
Score:21
cx flag

I got this issue with VB 7.2 on Windows 11, My findings:

  1. If you use unattended, created user will not even has sudo rights so that you can not update/edit "/usr/bin/gnome-terminal" with python version or purge gnome-terminal. Even updates doe not work with the created user.
  2. As suggested above, skip the unattended As shown in snip below

After installation all worked. Terminal worked

envs_h_gang_5 avatar
ch flag
Did the bidirectional copy and paste function works with `Skip Unattended Installation` checked?
Score:13
ng flag

I've spent 3h to fix this problem (Win 10 Pro, Vbox 7.0) and finally, I've decided to re-install a new guest OS with Skip Unattended Installation checked

envs_h_gang_5 avatar
ch flag
Did the bidirectional copy and paste function works with `Skip Unattended Installation` checked?
ng flag
bidirectional copy and paste function works well as usual
luisa rosi avatar
jp flag
by reinstalling Ubuntu on VB as suggested, I get the terminal running, the keyboard recognized correctly and VM User Interface showed. Thank you.
Score:11
vu flag

I had the same problem. The first thing I tried after installing Ubuntu 22.04 in VirtualBox 7.0 was to start the terminal. But it didn't work.

My solution was to create a new VM with a new installation. This time I selected "Skip unattended installation" when I created the VM, so that the Guest Additions was not automatically installed. Now I could start the terminal! After this I installed the Guest Additions using sudo apt-get install virtualbox-guest-additions-iso. In this way I got an old version of the Guest Additions, but that version seems to work fine.

So obviously the problem is related to the Guest Additions.

envs_h_gang_5 avatar
ch flag
Did the bidirectional copy and paste function works with `Skip Unattended Installation` checked?
envs_h_gang_5 avatar
ch flag
Yes, it works now after one and a half months but I could not figure out the reason.
Score:4
ec flag

I've been cracking my brain all day with the same problem. The only solution was to install a version of VB lower than 7.0

Score:1
cn flag

Switch Ubuntu to X11 instead of Wayland.

Also you can try to switch off 3d acceleration in the machine settings.

I just installed VB 7.0.2 and also had some trouble with graphics.

Finally all works with X11 and 3D enabled.

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.