Terminal won't launch after upgrading
After upgrading my laptop from 14.10 to 15.04, the terminal wont' launch. Ctrl+Alt+T does nothing. neither will terminal run from dash. I tried launching gnome-terminal from xterm, but nothing happens. Running htop from xterm shows many instances of gnome-terminal. Any advice anyone?
gnome-terminal locale 15.04
edited Oct 22 '15 at 9:40
Rinzwind
206k28395527
asked Apr 24 '15 at 21:44
KarhuKarhu
396139
add a comment |
After upgrading my laptop from 14.10 to 15.04, the terminal wont' launch. Ctrl+Alt+T does nothing. neither will terminal run from dash. I tried launching gnome-terminal from xterm, but nothing happens. Running htop from xterm shows many instances of gnome-terminal. Any advice anyone?
gnome-terminal locale 15.04
edited Oct 22 '15 at 9:40
Rinzwind
206k28395527
asked Apr 24 '15 at 21:44
KarhuKarhu
396139
1
Answering your own question is a thing here and it'll help mark this question as resolved.
– Huey
Jun 3 '15 at 12:10
I guess that there is no answer to this question, except that Nautilus gnome is just poor quality. I have a hanging terminal at one user and not at an other, with both the same extremely simple .profile and no .bashrc . It is like having a decease and the doctor has nothing to go on except "I'm in pain". Albert
– Albert van der Horst
Jan 24 at 11:34
add a comment |
After upgrading my laptop from 14.10 to 15.04, the terminal wont' launch. Ctrl+Alt+T does nothing. neither will terminal run from dash. I tried launching gnome-terminal from xterm, but nothing happens. Running htop from xterm shows many instances of gnome-terminal. Any advice anyone?
gnome-terminal locale 15.04
edited Oct 22 '15 at 9:40
Rinzwind
206k28395527
asked Apr 24 '15 at 21:44
KarhuKarhu
396139
After upgrading my laptop from 14.10 to 15.04, the terminal wont' launch. Ctrl+Alt+T does nothing. neither will terminal run from dash. I tried launching gnome-terminal from xterm, but nothing happens. Running htop from xterm shows many instances of gnome-terminal. Any advice anyone?
gnome-terminal locale 15.04
gnome-terminal locale 15.04
edited Oct 22 '15 at 9:40
Rinzwind
206k28395527
asked Apr 24 '15 at 21:44
KarhuKarhu
396139
edited Oct 22 '15 at 9:40
Rinzwind
206k28395527
asked Apr 24 '15 at 21:44
KarhuKarhu
396139
edited Oct 22 '15 at 9:40
Rinzwind
206k28395527
edited Oct 22 '15 at 9:40
Rinzwind
206k28395527
edited Oct 22 '15 at 9:40
Rinzwind
206k28395527
206k28395527
asked Apr 24 '15 at 21:44
KarhuKarhu
396139
asked Apr 24 '15 at 21:44
KarhuKarhu
396139
asked Apr 24 '15 at 21:44
KarhuKarhu
396139
396139
1
Answering your own question is a thing here and it'll help mark this question as resolved.
– Huey
Jun 3 '15 at 12:10
I guess that there is no answer to this question, except that Nautilus gnome is just poor quality. I have a hanging terminal at one user and not at an other, with both the same extremely simple .profile and no .bashrc . It is like having a decease and the doctor has nothing to go on except "I'm in pain". Albert
– Albert van der Horst
Jan 24 at 11:34
add a comment |
1
Answering your own question is a thing here and it'll help mark this question as resolved.
– Huey
Jun 3 '15 at 12:10
I guess that there is no answer to this question, except that Nautilus gnome is just poor quality. I have a hanging terminal at one user and not at an other, with both the same extremely simple .profile and no .bashrc . It is like having a decease and the doctor has nothing to go on except "I'm in pain". Albert
– Albert van der Horst
Jan 24 at 11:34
1
1
Answering your own question is a thing here and it'll help mark this question as resolved.
– Huey
Jun 3 '15 at 12:10
Answering your own question is a thing here and it'll help mark this question as resolved.
– Huey
Jun 3 '15 at 12:10
I guess that there is no answer to this question, except that Nautilus gnome is just poor quality. I have a hanging terminal at one user and not at an other, with both the same extremely simple .profile and no .bashrc . It is like having a decease and the doctor has nothing to go on except "I'm in pain". Albert
– Albert van der Horst
Jan 24 at 11:34
I guess that there is no answer to this question, except that Nautilus gnome is just poor quality. I have a hanging terminal at one user and not at an other, with both the same extremely simple .profile and no .bashrc . It is like having a decease and the doctor has nothing to go on except "I'm in pain". Albert
– Albert van der Horst
Jan 24 at 11:34
add a comment |
7 Answers
7
active
oldest
votes
I guess this is how you fix this.
You can change the locale in /etc/default/locale. You can try setting
the contents of that file to:
LANG="en_US.UTF-8"
LANGUAGE="en_US"
source
Blog post
edited Apr 13 '17 at 12:24
Community♦
1
answered Jun 9 '15 at 12:03
dvergurdvergur
216
I find it infuriating that it just hangs without given even the slightest indication of what the heck is wrong. Albert
– Albert van der Horst
Jan 24 at 11:30
add a comment |
OPs answer
Problem was a custom locale. Now using
standard en_US.utf8 and gnome-terminal
works normally.
add a comment |
I had the same issue upgrading to 15.04. I also went from 32-bit to 64-bit.
Just changing /etc/default/locale did not fix the issue.
Opening Language Support (in System Settings) and trying to change the default language gave the error that internationalisation was not fully installed. Clicking OK to install it gave an error.
The issue was that the boot partition (/boot) was full, blocking the download of the required packages. Search "cleaning the boot partition" for details - note that dpkg will not list all kernels from previous (32bit) versions so use the options to list what is installed in /boot.
After cleaning the boot partition, go into Language Support, change the default language, and accept the updates. That fixed the issue for me.
edited Sep 30 '16 at 21:28
wjandrea
9,09542362
answered Oct 6 '15 at 20:36
David RobsonDavid Robson
211
add a comment |
Language support and internationalisation was not fully installed, was my problem, too. After running the installation, Terminal started running normally! I had no problem with "/boot" or anything else.
edited Oct 22 '15 at 9:32
Karl Richter
2,43483569
answered Oct 22 '15 at 8:35
BatriqBatriq
11
add a comment |
I have read a lot of advice about missing terminals, and it was frustrating when people gave me all these commands, which I cannot enter without my terminal...
Another frustration was not knowing that the terminal is properly called gnome-terminal in Ubuntu.
So to open a console, press Ctrl+Alt+F1 and you can log in to a text-only session.
Then try this command which will try to analyze and fix dependencies:
sudo apt-get build-dep gnome-terminal
With my present problem, it first asked me to put some source repos into my repository list. When I fixed that and repeated the build-dep command, it pointed out some 60 unresolved dependencies and offered to fix them, which I accepted.
For getting out of the console and back into your graphical environment, use Ctrl+Alt+F7.
There I found a message telling me to restart the computer which I did.
Either you will now have a working terminal or you might be several steps closer to a solution or at least you have received more information about your system and potential problem.
In my case I needed two more things:
I tried launching gnome-terminal from my console with this command:
/usr/bin/python3 /usr/bin/gnome-terminal
But I kept getting an error about not being able to connect to Mir (which supposedly is the name of a display server for Linux, being developed for Ubuntu, as a replacement for X11.
So first I entered this into my console:
export DISPLAY=:0
and again:
/usr/bin/python3 /usr/bin/gnome-terminal
When I returned to the GUI using Ctrl+Alt+F7, I found a running terminal!
I will still not launch directly from the GUI by clicking, but at least I know that all needed elements are now installed and I can do more research.
Hope that helps.
edited Sep 30 '16 at 21:28
wjandrea
9,09542362
answered Sep 1 '16 at 16:53
Martin ZaskeMartin Zaske
1012
You don't need toexport DISPLAY=:0, you don't have to use python, and you don't need to use the full pathname. You can just runDISPLAY=:0 gnome-terminal.
– wjandrea
Sep 30 '16 at 20:03
Thank you wjandrea; I tried your command after a fresh boot and it works. Very nice, very helpful.
– Martin Zaske
Jan 21 '17 at 19:05
add a comment |
It happened to me as well. Resetting desktop configuration to default solved my problem. Here's how you can reset it:-
dconf reset -f /
Source(s):
- https://www.omgubuntu.co.uk/2017/10/how-to-reset-ubuntu-desktop-to-default
answered Jul 28 '18 at 17:17
Devesh SainiDevesh Saini
1254
add a comment |
I had the same problem after messing with the language configuration files. What did the trick for me was running
dpkg-reconfigure locales
as root, and then selecting the languages I wanted to fix. Hope that helps.
answered Jan 8 at 11:13
DavidDavid
1
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',
autoActivateHeartbeat: false,
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%2f613582%2fterminal-wont-launch-after-upgrading%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
7 Answers
7
active
oldest
votes
7 Answers
7
active
oldest
votes
active
oldest
votes
active
oldest
votes
I guess this is how you fix this.
You can change the locale in /etc/default/locale. You can try setting
the contents of that file to:
LANG="en_US.UTF-8"
LANGUAGE="en_US"
source
Blog post
edited Apr 13 '17 at 12:24
Community♦
1
answered Jun 9 '15 at 12:03
dvergurdvergur
216
I find it infuriating that it just hangs without given even the slightest indication of what the heck is wrong. Albert
– Albert van der Horst
Jan 24 at 11:30
add a comment |
I guess this is how you fix this.
You can change the locale in /etc/default/locale. You can try setting
the contents of that file to:
LANG="en_US.UTF-8"
LANGUAGE="en_US"
source
Blog post
edited Apr 13 '17 at 12:24
Community♦
1
answered Jun 9 '15 at 12:03
dvergurdvergur
216
I find it infuriating that it just hangs without given even the slightest indication of what the heck is wrong. Albert
– Albert van der Horst
Jan 24 at 11:30
add a comment |
I guess this is how you fix this.
You can change the locale in /etc/default/locale. You can try setting
the contents of that file to:
LANG="en_US.UTF-8"
LANGUAGE="en_US"
source
Blog post
edited Apr 13 '17 at 12:24
Community♦
1
answered Jun 9 '15 at 12:03
dvergurdvergur
216
I guess this is how you fix this.
You can change the locale in /etc/default/locale. You can try setting
the contents of that file to:
LANG="en_US.UTF-8"
LANGUAGE="en_US"
source
Blog post
edited Apr 13 '17 at 12:24
Community♦
1
answered Jun 9 '15 at 12:03
dvergurdvergur
216
edited Apr 13 '17 at 12:24
Community♦
1
edited Apr 13 '17 at 12:24
Community♦
1
edited Apr 13 '17 at 12:24
Community♦
1
1
answered Jun 9 '15 at 12:03
dvergurdvergur
216
answered Jun 9 '15 at 12:03
dvergurdvergur
216
answered Jun 9 '15 at 12:03
dvergurdvergur
216
216
I find it infuriating that it just hangs without given even the slightest indication of what the heck is wrong. Albert
– Albert van der Horst
Jan 24 at 11:30
add a comment |
I find it infuriating that it just hangs without given even the slightest indication of what the heck is wrong. Albert
– Albert van der Horst
Jan 24 at 11:30
I find it infuriating that it just hangs without given even the slightest indication of what the heck is wrong. Albert
– Albert van der Horst
Jan 24 at 11:30
I find it infuriating that it just hangs without given even the slightest indication of what the heck is wrong. Albert
– Albert van der Horst
Jan 24 at 11:30
add a comment |
OPs answer
Problem was a custom locale. Now using
standard en_US.utf8 and gnome-terminal
works normally.
add a comment |
OPs answer
Problem was a custom locale. Now using
standard en_US.utf8 and gnome-terminal
works normally.
add a comment |
OPs answer
Problem was a custom locale. Now using
standard en_US.utf8 and gnome-terminal
works normally.
OPs answer
Problem was a custom locale. Now using
standard en_US.utf8 and gnome-terminal
works normally.
answered Jun 19 '15 at 4:43
community wiki
A.B.
add a comment |
add a comment |
I had the same issue upgrading to 15.04. I also went from 32-bit to 64-bit.
Just changing /etc/default/locale did not fix the issue.
Opening Language Support (in System Settings) and trying to change the default language gave the error that internationalisation was not fully installed. Clicking OK to install it gave an error.
The issue was that the boot partition (/boot) was full, blocking the download of the required packages. Search "cleaning the boot partition" for details - note that dpkg will not list all kernels from previous (32bit) versions so use the options to list what is installed in /boot.
After cleaning the boot partition, go into Language Support, change the default language, and accept the updates. That fixed the issue for me.
edited Sep 30 '16 at 21:28
wjandrea
9,09542362
answered Oct 6 '15 at 20:36
David RobsonDavid Robson
211
add a comment |
I had the same issue upgrading to 15.04. I also went from 32-bit to 64-bit.
Just changing /etc/default/locale did not fix the issue.
Opening Language Support (in System Settings) and trying to change the default language gave the error that internationalisation was not fully installed. Clicking OK to install it gave an error.
The issue was that the boot partition (/boot) was full, blocking the download of the required packages. Search "cleaning the boot partition" for details - note that dpkg will not list all kernels from previous (32bit) versions so use the options to list what is installed in /boot.
After cleaning the boot partition, go into Language Support, change the default language, and accept the updates. That fixed the issue for me.
edited Sep 30 '16 at 21:28
wjandrea
9,09542362
answered Oct 6 '15 at 20:36
David RobsonDavid Robson
211
add a comment |
I had the same issue upgrading to 15.04. I also went from 32-bit to 64-bit.
Just changing /etc/default/locale did not fix the issue.
Opening Language Support (in System Settings) and trying to change the default language gave the error that internationalisation was not fully installed. Clicking OK to install it gave an error.
The issue was that the boot partition (/boot) was full, blocking the download of the required packages. Search "cleaning the boot partition" for details - note that dpkg will not list all kernels from previous (32bit) versions so use the options to list what is installed in /boot.
After cleaning the boot partition, go into Language Support, change the default language, and accept the updates. That fixed the issue for me.
edited Sep 30 '16 at 21:28
wjandrea
9,09542362
answered Oct 6 '15 at 20:36
David RobsonDavid Robson
211
I had the same issue upgrading to 15.04. I also went from 32-bit to 64-bit.
Just changing /etc/default/locale did not fix the issue.
Opening Language Support (in System Settings) and trying to change the default language gave the error that internationalisation was not fully installed. Clicking OK to install it gave an error.
The issue was that the boot partition (/boot) was full, blocking the download of the required packages. Search "cleaning the boot partition" for details - note that dpkg will not list all kernels from previous (32bit) versions so use the options to list what is installed in /boot.
After cleaning the boot partition, go into Language Support, change the default language, and accept the updates. That fixed the issue for me.
edited Sep 30 '16 at 21:28
wjandrea
9,09542362
answered Oct 6 '15 at 20:36
David RobsonDavid Robson
211
edited Sep 30 '16 at 21:28
wjandrea
9,09542362
edited Sep 30 '16 at 21:28
wjandrea
9,09542362
edited Sep 30 '16 at 21:28
wjandrea
9,09542362
9,09542362
answered Oct 6 '15 at 20:36
David RobsonDavid Robson
211
answered Oct 6 '15 at 20:36
David RobsonDavid Robson
211
answered Oct 6 '15 at 20:36
David RobsonDavid Robson
211
211
add a comment |
add a comment |
Language support and internationalisation was not fully installed, was my problem, too. After running the installation, Terminal started running normally! I had no problem with "/boot" or anything else.
edited Oct 22 '15 at 9:32
Karl Richter
2,43483569
answered Oct 22 '15 at 8:35
BatriqBatriq
11
add a comment |
Language support and internationalisation was not fully installed, was my problem, too. After running the installation, Terminal started running normally! I had no problem with "/boot" or anything else.
edited Oct 22 '15 at 9:32
Karl Richter
2,43483569
answered Oct 22 '15 at 8:35
BatriqBatriq
11
add a comment |
Language support and internationalisation was not fully installed, was my problem, too. After running the installation, Terminal started running normally! I had no problem with "/boot" or anything else.
edited Oct 22 '15 at 9:32
Karl Richter
2,43483569
answered Oct 22 '15 at 8:35
BatriqBatriq
11
Language support and internationalisation was not fully installed, was my problem, too. After running the installation, Terminal started running normally! I had no problem with "/boot" or anything else.
edited Oct 22 '15 at 9:32
Karl Richter
2,43483569
answered Oct 22 '15 at 8:35
BatriqBatriq
11
edited Oct 22 '15 at 9:32
Karl Richter
2,43483569
edited Oct 22 '15 at 9:32
Karl Richter
2,43483569
edited Oct 22 '15 at 9:32
Karl Richter
2,43483569
2,43483569
answered Oct 22 '15 at 8:35
BatriqBatriq
11
answered Oct 22 '15 at 8:35
BatriqBatriq
11
answered Oct 22 '15 at 8:35
BatriqBatriq
11
11
add a comment |
add a comment |
I have read a lot of advice about missing terminals, and it was frustrating when people gave me all these commands, which I cannot enter without my terminal...
Another frustration was not knowing that the terminal is properly called gnome-terminal in Ubuntu.
So to open a console, press Ctrl+Alt+F1 and you can log in to a text-only session.
Then try this command which will try to analyze and fix dependencies:
sudo apt-get build-dep gnome-terminal
With my present problem, it first asked me to put some source repos into my repository list. When I fixed that and repeated the build-dep command, it pointed out some 60 unresolved dependencies and offered to fix them, which I accepted.
For getting out of the console and back into your graphical environment, use Ctrl+Alt+F7.
There I found a message telling me to restart the computer which I did.
Either you will now have a working terminal or you might be several steps closer to a solution or at least you have received more information about your system and potential problem.
In my case I needed two more things:
I tried launching gnome-terminal from my console with this command:
/usr/bin/python3 /usr/bin/gnome-terminal
But I kept getting an error about not being able to connect to Mir (which supposedly is the name of a display server for Linux, being developed for Ubuntu, as a replacement for X11.
So first I entered this into my console:
export DISPLAY=:0
and again:
/usr/bin/python3 /usr/bin/gnome-terminal
When I returned to the GUI using Ctrl+Alt+F7, I found a running terminal!
I will still not launch directly from the GUI by clicking, but at least I know that all needed elements are now installed and I can do more research.
Hope that helps.
edited Sep 30 '16 at 21:28
wjandrea
9,09542362
answered Sep 1 '16 at 16:53
Martin ZaskeMartin Zaske
1012
You don't need toexport DISPLAY=:0, you don't have to use python, and you don't need to use the full pathname. You can just runDISPLAY=:0 gnome-terminal.
– wjandrea
Sep 30 '16 at 20:03
Thank you wjandrea; I tried your command after a fresh boot and it works. Very nice, very helpful.
– Martin Zaske
Jan 21 '17 at 19:05
add a comment |
I have read a lot of advice about missing terminals, and it was frustrating when people gave me all these commands, which I cannot enter without my terminal...
Another frustration was not knowing that the terminal is properly called gnome-terminal in Ubuntu.
So to open a console, press Ctrl+Alt+F1 and you can log in to a text-only session.
Then try this command which will try to analyze and fix dependencies:
sudo apt-get build-dep gnome-terminal
With my present problem, it first asked me to put some source repos into my repository list. When I fixed that and repeated the build-dep command, it pointed out some 60 unresolved dependencies and offered to fix them, which I accepted.
For getting out of the console and back into your graphical environment, use Ctrl+Alt+F7.
There I found a message telling me to restart the computer which I did.
Either you will now have a working terminal or you might be several steps closer to a solution or at least you have received more information about your system and potential problem.
In my case I needed two more things:
I tried launching gnome-terminal from my console with this command:
/usr/bin/python3 /usr/bin/gnome-terminal
But I kept getting an error about not being able to connect to Mir (which supposedly is the name of a display server for Linux, being developed for Ubuntu, as a replacement for X11.
So first I entered this into my console:
export DISPLAY=:0
and again:
/usr/bin/python3 /usr/bin/gnome-terminal
When I returned to the GUI using Ctrl+Alt+F7, I found a running terminal!
I will still not launch directly from the GUI by clicking, but at least I know that all needed elements are now installed and I can do more research.
Hope that helps.
edited Sep 30 '16 at 21:28
wjandrea
9,09542362
answered Sep 1 '16 at 16:53
Martin ZaskeMartin Zaske
1012
You don't need toexport DISPLAY=:0, you don't have to use python, and you don't need to use the full pathname. You can just runDISPLAY=:0 gnome-terminal.
– wjandrea
Sep 30 '16 at 20:03
Thank you wjandrea; I tried your command after a fresh boot and it works. Very nice, very helpful.
– Martin Zaske
Jan 21 '17 at 19:05
add a comment |
I have read a lot of advice about missing terminals, and it was frustrating when people gave me all these commands, which I cannot enter without my terminal...
Another frustration was not knowing that the terminal is properly called gnome-terminal in Ubuntu.
So to open a console, press Ctrl+Alt+F1 and you can log in to a text-only session.
Then try this command which will try to analyze and fix dependencies:
sudo apt-get build-dep gnome-terminal
With my present problem, it first asked me to put some source repos into my repository list. When I fixed that and repeated the build-dep command, it pointed out some 60 unresolved dependencies and offered to fix them, which I accepted.
For getting out of the console and back into your graphical environment, use Ctrl+Alt+F7.
There I found a message telling me to restart the computer which I did.
Either you will now have a working terminal or you might be several steps closer to a solution or at least you have received more information about your system and potential problem.
In my case I needed two more things:
I tried launching gnome-terminal from my console with this command:
/usr/bin/python3 /usr/bin/gnome-terminal
But I kept getting an error about not being able to connect to Mir (which supposedly is the name of a display server for Linux, being developed for Ubuntu, as a replacement for X11.
So first I entered this into my console:
export DISPLAY=:0
and again:
/usr/bin/python3 /usr/bin/gnome-terminal
When I returned to the GUI using Ctrl+Alt+F7, I found a running terminal!
I will still not launch directly from the GUI by clicking, but at least I know that all needed elements are now installed and I can do more research.
Hope that helps.
edited Sep 30 '16 at 21:28
wjandrea
9,09542362
answered Sep 1 '16 at 16:53
Martin ZaskeMartin Zaske
1012
I have read a lot of advice about missing terminals, and it was frustrating when people gave me all these commands, which I cannot enter without my terminal...
Another frustration was not knowing that the terminal is properly called gnome-terminal in Ubuntu.
So to open a console, press Ctrl+Alt+F1 and you can log in to a text-only session.
Then try this command which will try to analyze and fix dependencies:
sudo apt-get build-dep gnome-terminal
With my present problem, it first asked me to put some source repos into my repository list. When I fixed that and repeated the build-dep command, it pointed out some 60 unresolved dependencies and offered to fix them, which I accepted.
For getting out of the console and back into your graphical environment, use Ctrl+Alt+F7.
There I found a message telling me to restart the computer which I did.
Either you will now have a working terminal or you might be several steps closer to a solution or at least you have received more information about your system and potential problem.
In my case I needed two more things:
I tried launching gnome-terminal from my console with this command:
/usr/bin/python3 /usr/bin/gnome-terminal
But I kept getting an error about not being able to connect to Mir (which supposedly is the name of a display server for Linux, being developed for Ubuntu, as a replacement for X11.
So first I entered this into my console:
export DISPLAY=:0
and again:
/usr/bin/python3 /usr/bin/gnome-terminal
When I returned to the GUI using Ctrl+Alt+F7, I found a running terminal!
I will still not launch directly from the GUI by clicking, but at least I know that all needed elements are now installed and I can do more research.
Hope that helps.
edited Sep 30 '16 at 21:28
wjandrea
9,09542362
answered Sep 1 '16 at 16:53
Martin ZaskeMartin Zaske
1012
edited Sep 30 '16 at 21:28
wjandrea
9,09542362
edited Sep 30 '16 at 21:28
wjandrea
9,09542362
edited Sep 30 '16 at 21:28
wjandrea
9,09542362
9,09542362
answered Sep 1 '16 at 16:53
Martin ZaskeMartin Zaske
1012
answered Sep 1 '16 at 16:53
Martin ZaskeMartin Zaske
1012
answered Sep 1 '16 at 16:53
Martin ZaskeMartin Zaske
1012
1012
You don't need toexport DISPLAY=:0, you don't have to use python, and you don't need to use the full pathname. You can just runDISPLAY=:0 gnome-terminal.
– wjandrea
Sep 30 '16 at 20:03
Thank you wjandrea; I tried your command after a fresh boot and it works. Very nice, very helpful.
– Martin Zaske
Jan 21 '17 at 19:05
add a comment |
You don't need toexport DISPLAY=:0, you don't have to use python, and you don't need to use the full pathname. You can just runDISPLAY=:0 gnome-terminal.
– wjandrea
Sep 30 '16 at 20:03
Thank you wjandrea; I tried your command after a fresh boot and it works. Very nice, very helpful.
– Martin Zaske
Jan 21 '17 at 19:05
You don't need to
export DISPLAY=:0, you don't have to use python, and you don't need to use the full pathname. You can just run DISPLAY=:0 gnome-terminal.– wjandrea
Sep 30 '16 at 20:03
You don't need to
export DISPLAY=:0, you don't have to use python, and you don't need to use the full pathname. You can just run DISPLAY=:0 gnome-terminal.– wjandrea
Sep 30 '16 at 20:03
Thank you wjandrea; I tried your command after a fresh boot and it works. Very nice, very helpful.
– Martin Zaske
Jan 21 '17 at 19:05
Thank you wjandrea; I tried your command after a fresh boot and it works. Very nice, very helpful.
– Martin Zaske
Jan 21 '17 at 19:05
add a comment |
It happened to me as well. Resetting desktop configuration to default solved my problem. Here's how you can reset it:-
dconf reset -f /
Source(s):
- https://www.omgubuntu.co.uk/2017/10/how-to-reset-ubuntu-desktop-to-default
answered Jul 28 '18 at 17:17
Devesh SainiDevesh Saini
1254
add a comment |
It happened to me as well. Resetting desktop configuration to default solved my problem. Here's how you can reset it:-
dconf reset -f /
Source(s):
- https://www.omgubuntu.co.uk/2017/10/how-to-reset-ubuntu-desktop-to-default
answered Jul 28 '18 at 17:17
Devesh SainiDevesh Saini
1254
add a comment |
It happened to me as well. Resetting desktop configuration to default solved my problem. Here's how you can reset it:-
dconf reset -f /
Source(s):
- https://www.omgubuntu.co.uk/2017/10/how-to-reset-ubuntu-desktop-to-default
answered Jul 28 '18 at 17:17
Devesh SainiDevesh Saini
1254
It happened to me as well. Resetting desktop configuration to default solved my problem. Here's how you can reset it:-
dconf reset -f /
Source(s):
- https://www.omgubuntu.co.uk/2017/10/how-to-reset-ubuntu-desktop-to-default
answered Jul 28 '18 at 17:17
Devesh SainiDevesh Saini
1254
edited Jul 28 '18 at 18:42
answered Jul 28 '18 at 17:17
Devesh SainiDevesh Saini
1254
answered Jul 28 '18 at 17:17
Devesh SainiDevesh Saini
1254
answered Jul 28 '18 at 17:17
Devesh SainiDevesh Saini
1254
1254
add a comment |
add a comment |
I had the same problem after messing with the language configuration files. What did the trick for me was running
dpkg-reconfigure locales
as root, and then selecting the languages I wanted to fix. Hope that helps.
answered Jan 8 at 11:13
DavidDavid
1
add a comment |
I had the same problem after messing with the language configuration files. What did the trick for me was running
dpkg-reconfigure locales
as root, and then selecting the languages I wanted to fix. Hope that helps.
answered Jan 8 at 11:13
DavidDavid
1
add a comment |
I had the same problem after messing with the language configuration files. What did the trick for me was running
dpkg-reconfigure locales
as root, and then selecting the languages I wanted to fix. Hope that helps.
answered Jan 8 at 11:13
DavidDavid
1
I had the same problem after messing with the language configuration files. What did the trick for me was running
dpkg-reconfigure locales
as root, and then selecting the languages I wanted to fix. Hope that helps.
answered Jan 8 at 11:13
DavidDavid
1
answered Jan 8 at 11:13
DavidDavid
1
answered Jan 8 at 11:13
DavidDavid
1
answered Jan 8 at 11:13
DavidDavid
1
1
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.
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%2f613582%2fterminal-wont-launch-after-upgrading%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
1
Answering your own question is a thing here and it'll help mark this question as resolved.
– Huey
Jun 3 '15 at 12:10
I guess that there is no answer to this question, except that Nautilus gnome is just poor quality. I have a hanging terminal at one user and not at an other, with both the same extremely simple .profile and no .bashrc . It is like having a decease and the doctor has nothing to go on except "I'm in pain". Albert
– Albert van der Horst
Jan 24 at 11:34