Reset terminal profile preferences (Without using terminal)
I am running Ubuntu 16.04 LTS
I opened up terminal and went Preferences > Profiles > Command, and checked both Run command as a login shell and Run a custom command instead of my shell and I changed the drop-down menu to Exit the terminal.
My problem is now every time I open terminal, it closes before I can open the preferences again and I couldn't find anything on the Internet about how to fix it. I have the ability to connect through SSH if I need to run any commands and I'm wondering if there is any files I can modify to fix this. Thanks!
gnome-terminal
edited Apr 24 '17 at 23:20
Gilles
532k12810651592
asked Apr 24 '17 at 3:42
BradleyBradley
1115
|
show 4 more comments
I am running Ubuntu 16.04 LTS
I opened up terminal and went Preferences > Profiles > Command, and checked both Run command as a login shell and Run a custom command instead of my shell and I changed the drop-down menu to Exit the terminal.
My problem is now every time I open terminal, it closes before I can open the preferences again and I couldn't find anything on the Internet about how to fix it. I have the ability to connect through SSH if I need to run any commands and I'm wondering if there is any files I can modify to fix this. Thanks!
gnome-terminal
edited Apr 24 '17 at 23:20
Gilles
532k12810651592
asked Apr 24 '17 at 3:42
BradleyBradley
1115
Are you usinggnome-terminal(i.e. the default one from Ubuntu)? If so, one idea would be to search inside your$HOMEdirectory for its settings. Maybe with afind $HOME -iname '*terminal*'
– thiagowfx
Apr 24 '17 at 3:48
A second idea would be to find its settings with eitherdconforgsettings.
– thiagowfx
Apr 24 '17 at 3:49
1
Thanks for the quick reply. I used XTerm to use the command 'dconf reset -f /org/gnome/terminal/legacy/profiles:/' (Sorry commented too soon there before). Thanks for the help :) @thiagowfx
– Bradley
Apr 24 '17 at 4:57
This does not really fix your problem, right? You are just using a different terminal. Anyway, at least you can be productive meanwhile :)
– thiagowfx
Apr 24 '17 at 4:59
It did fix the problem just commented too soon :P
– Bradley
Apr 24 '17 at 5:01
|
show 4 more comments
I am running Ubuntu 16.04 LTS
I opened up terminal and went Preferences > Profiles > Command, and checked both Run command as a login shell and Run a custom command instead of my shell and I changed the drop-down menu to Exit the terminal.
My problem is now every time I open terminal, it closes before I can open the preferences again and I couldn't find anything on the Internet about how to fix it. I have the ability to connect through SSH if I need to run any commands and I'm wondering if there is any files I can modify to fix this. Thanks!
gnome-terminal
edited Apr 24 '17 at 23:20
Gilles
532k12810651592
asked Apr 24 '17 at 3:42
BradleyBradley
1115
I am running Ubuntu 16.04 LTS
I opened up terminal and went Preferences > Profiles > Command, and checked both Run command as a login shell and Run a custom command instead of my shell and I changed the drop-down menu to Exit the terminal.
My problem is now every time I open terminal, it closes before I can open the preferences again and I couldn't find anything on the Internet about how to fix it. I have the ability to connect through SSH if I need to run any commands and I'm wondering if there is any files I can modify to fix this. Thanks!
gnome-terminal
gnome-terminal
edited Apr 24 '17 at 23:20
Gilles
532k12810651592
asked Apr 24 '17 at 3:42
BradleyBradley
1115
edited Apr 24 '17 at 23:20
Gilles
532k12810651592
asked Apr 24 '17 at 3:42
BradleyBradley
1115
edited Apr 24 '17 at 23:20
Gilles
532k12810651592
edited Apr 24 '17 at 23:20
Gilles
532k12810651592
edited Apr 24 '17 at 23:20
Gilles
532k12810651592
532k12810651592
asked Apr 24 '17 at 3:42
BradleyBradley
1115
asked Apr 24 '17 at 3:42
BradleyBradley
1115
asked Apr 24 '17 at 3:42
BradleyBradley
1115
1115
Are you usinggnome-terminal(i.e. the default one from Ubuntu)? If so, one idea would be to search inside your$HOMEdirectory for its settings. Maybe with afind $HOME -iname '*terminal*'
– thiagowfx
Apr 24 '17 at 3:48
A second idea would be to find its settings with eitherdconforgsettings.
– thiagowfx
Apr 24 '17 at 3:49
1
Thanks for the quick reply. I used XTerm to use the command 'dconf reset -f /org/gnome/terminal/legacy/profiles:/' (Sorry commented too soon there before). Thanks for the help :) @thiagowfx
– Bradley
Apr 24 '17 at 4:57
This does not really fix your problem, right? You are just using a different terminal. Anyway, at least you can be productive meanwhile :)
– thiagowfx
Apr 24 '17 at 4:59
It did fix the problem just commented too soon :P
– Bradley
Apr 24 '17 at 5:01
|
show 4 more comments
Are you usinggnome-terminal(i.e. the default one from Ubuntu)? If so, one idea would be to search inside your$HOMEdirectory for its settings. Maybe with afind $HOME -iname '*terminal*'
– thiagowfx
Apr 24 '17 at 3:48
A second idea would be to find its settings with eitherdconforgsettings.
– thiagowfx
Apr 24 '17 at 3:49
1
Thanks for the quick reply. I used XTerm to use the command 'dconf reset -f /org/gnome/terminal/legacy/profiles:/' (Sorry commented too soon there before). Thanks for the help :) @thiagowfx
– Bradley
Apr 24 '17 at 4:57
This does not really fix your problem, right? You are just using a different terminal. Anyway, at least you can be productive meanwhile :)
– thiagowfx
Apr 24 '17 at 4:59
It did fix the problem just commented too soon :P
– Bradley
Apr 24 '17 at 5:01
Are you using
gnome-terminal (i.e. the default one from Ubuntu)? If so, one idea would be to search inside your $HOME directory for its settings. Maybe with a find $HOME -iname '*terminal*'– thiagowfx
Apr 24 '17 at 3:48
Are you using
gnome-terminal (i.e. the default one from Ubuntu)? If so, one idea would be to search inside your $HOME directory for its settings. Maybe with a find $HOME -iname '*terminal*'– thiagowfx
Apr 24 '17 at 3:48
A second idea would be to find its settings with either
dconf or gsettings.– thiagowfx
Apr 24 '17 at 3:49
A second idea would be to find its settings with either
dconf or gsettings.– thiagowfx
Apr 24 '17 at 3:49
1
1
Thanks for the quick reply. I used XTerm to use the command 'dconf reset -f /org/gnome/terminal/legacy/profiles:/' (Sorry commented too soon there before). Thanks for the help :) @thiagowfx
– Bradley
Apr 24 '17 at 4:57
Thanks for the quick reply. I used XTerm to use the command 'dconf reset -f /org/gnome/terminal/legacy/profiles:/' (Sorry commented too soon there before). Thanks for the help :) @thiagowfx
– Bradley
Apr 24 '17 at 4:57
This does not really fix your problem, right? You are just using a different terminal. Anyway, at least you can be productive meanwhile :)
– thiagowfx
Apr 24 '17 at 4:59
This does not really fix your problem, right? You are just using a different terminal. Anyway, at least you can be productive meanwhile :)
– thiagowfx
Apr 24 '17 at 4:59
It did fix the problem just commented too soon :P
– Bradley
Apr 24 '17 at 5:01
It did fix the problem just commented too soon :P
– Bradley
Apr 24 '17 at 5:01
|
show 4 more comments
5 Answers
5
active
oldest
votes
You won't have to install any program or remove any file.
To edit your gnome-terminal preferences, without actually opening or using gnome-terminal:
Go to:
root/usr/share/applicationslocate Terminal in the folder.
- Then open its properties by right clicking on Terminal. You'll then see the command.
This is actually what happens when you open terminal.
So to edit the preferences; change the command gnome-terminal to gnome-terminal --preferences... Voila!
After "repairing" the settings. Just close the preferences and then remove --preferences from the command in the properties window. Now just open the terminal as you would.
edited Jun 1 '18 at 8:27
Kevdog777
2,097123259
answered Jun 1 '18 at 8:00
Archit AgarwalArchit Agarwal
212
add a comment |
I had the same problem. I found this solution:
open xterm
type this command: gnome-terminal -e -ls [the bash shell (gnome-terminal) will be open (instead close), because it try to execute another command then the other established in the profile configuration]
- change the profile configuration.
edited Sep 14 '17 at 6:04
Anthon
60.4k17102165
answered Sep 14 '17 at 0:49
Alessandro SenoAlessandro Seno
111
add a comment |
No necro-posting here (OP is already 6 months old) but I had the same issue and was locked out of my one available desktop gnome-terminal, with no way to download and install another one, apart from dropping to console. Similarly to OP I had set gnome-terminal up and ran an invalid custom command instead of my shell.
My "desktop" solution was to reset gnome-terminal's settings by way of dconf.
Just navigate to /org/gnome/terminal, highlight "legacy", right click and choose "reset recursively" ... (in the end, a very minor case of cold sweat).
In the process you will lose yr gnome-terminal settings and any profile you had. However relaunching terminal and starting again from scratch becomes immediately possible.
HTH future lx apprentice sorcerers.
answered Oct 12 '17 at 18:00
CbhiheCbhihe
3031316
add a comment |
I used dconf tool to work on my way to /org/gnome/terminal/profiles/xxxprofile. Cleared the entry in "custom-command" box, unchecked "use-custom-command" checkbox and cleared the entry in the "visible-name" box.
Terminal function returned to normal.
edited Mar 30 '18 at 15:19
Yurij Goncharuk
2,3232522
answered Mar 30 '18 at 13:41
GordKGordK
11
add a comment |
What I actually did was to install dconf then open dconf-editor and going to org/gnome/terminal/legacy/keybindings/preferences, setting the shortcut to <Ctrl><Shift>r (any other not used would do as well) and pressing it before the terminal closes. I went on from there and removed the preference I had made. Having tried everything else, this was my last idea and it worked.
answered 51 mins ago
SteliosKSteliosK
1
New contributor
SteliosK is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f360873%2freset-terminal-profile-preferences-without-using-terminal%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
You won't have to install any program or remove any file.
To edit your gnome-terminal preferences, without actually opening or using gnome-terminal:
Go to:
root/usr/share/applicationslocate Terminal in the folder.
- Then open its properties by right clicking on Terminal. You'll then see the command.
This is actually what happens when you open terminal.
So to edit the preferences; change the command gnome-terminal to gnome-terminal --preferences... Voila!
After "repairing" the settings. Just close the preferences and then remove --preferences from the command in the properties window. Now just open the terminal as you would.
edited Jun 1 '18 at 8:27
Kevdog777
2,097123259
answered Jun 1 '18 at 8:00
Archit AgarwalArchit Agarwal
212
add a comment |
You won't have to install any program or remove any file.
To edit your gnome-terminal preferences, without actually opening or using gnome-terminal:
Go to:
root/usr/share/applicationslocate Terminal in the folder.
- Then open its properties by right clicking on Terminal. You'll then see the command.
This is actually what happens when you open terminal.
So to edit the preferences; change the command gnome-terminal to gnome-terminal --preferences... Voila!
After "repairing" the settings. Just close the preferences and then remove --preferences from the command in the properties window. Now just open the terminal as you would.
edited Jun 1 '18 at 8:27
Kevdog777
2,097123259
answered Jun 1 '18 at 8:00
Archit AgarwalArchit Agarwal
212
add a comment |
You won't have to install any program or remove any file.
To edit your gnome-terminal preferences, without actually opening or using gnome-terminal:
Go to:
root/usr/share/applicationslocate Terminal in the folder.
- Then open its properties by right clicking on Terminal. You'll then see the command.
This is actually what happens when you open terminal.
So to edit the preferences; change the command gnome-terminal to gnome-terminal --preferences... Voila!
After "repairing" the settings. Just close the preferences and then remove --preferences from the command in the properties window. Now just open the terminal as you would.
edited Jun 1 '18 at 8:27
Kevdog777
2,097123259
answered Jun 1 '18 at 8:00
Archit AgarwalArchit Agarwal
212
You won't have to install any program or remove any file.
To edit your gnome-terminal preferences, without actually opening or using gnome-terminal:
Go to:
root/usr/share/applicationslocate Terminal in the folder.
- Then open its properties by right clicking on Terminal. You'll then see the command.
This is actually what happens when you open terminal.
So to edit the preferences; change the command gnome-terminal to gnome-terminal --preferences... Voila!
After "repairing" the settings. Just close the preferences and then remove --preferences from the command in the properties window. Now just open the terminal as you would.
edited Jun 1 '18 at 8:27
Kevdog777
2,097123259
answered Jun 1 '18 at 8:00
Archit AgarwalArchit Agarwal
212
edited Jun 1 '18 at 8:27
Kevdog777
2,097123259
edited Jun 1 '18 at 8:27
Kevdog777
2,097123259
edited Jun 1 '18 at 8:27
Kevdog777
2,097123259
2,097123259
answered Jun 1 '18 at 8:00
Archit AgarwalArchit Agarwal
212
answered Jun 1 '18 at 8:00
Archit AgarwalArchit Agarwal
212
answered Jun 1 '18 at 8:00
Archit AgarwalArchit Agarwal
212
212
add a comment |
add a comment |
I had the same problem. I found this solution:
open xterm
type this command: gnome-terminal -e -ls [the bash shell (gnome-terminal) will be open (instead close), because it try to execute another command then the other established in the profile configuration]
- change the profile configuration.
edited Sep 14 '17 at 6:04
Anthon
60.4k17102165
answered Sep 14 '17 at 0:49
Alessandro SenoAlessandro Seno
111
add a comment |
I had the same problem. I found this solution:
open xterm
type this command: gnome-terminal -e -ls [the bash shell (gnome-terminal) will be open (instead close), because it try to execute another command then the other established in the profile configuration]
- change the profile configuration.
edited Sep 14 '17 at 6:04
Anthon
60.4k17102165
answered Sep 14 '17 at 0:49
Alessandro SenoAlessandro Seno
111
add a comment |
I had the same problem. I found this solution:
open xterm
type this command: gnome-terminal -e -ls [the bash shell (gnome-terminal) will be open (instead close), because it try to execute another command then the other established in the profile configuration]
- change the profile configuration.
edited Sep 14 '17 at 6:04
Anthon
60.4k17102165
answered Sep 14 '17 at 0:49
Alessandro SenoAlessandro Seno
111
I had the same problem. I found this solution:
open xterm
type this command: gnome-terminal -e -ls [the bash shell (gnome-terminal) will be open (instead close), because it try to execute another command then the other established in the profile configuration]
- change the profile configuration.
edited Sep 14 '17 at 6:04
Anthon
60.4k17102165
answered Sep 14 '17 at 0:49
Alessandro SenoAlessandro Seno
111
edited Sep 14 '17 at 6:04
Anthon
60.4k17102165
edited Sep 14 '17 at 6:04
Anthon
60.4k17102165
edited Sep 14 '17 at 6:04
Anthon
60.4k17102165
60.4k17102165
answered Sep 14 '17 at 0:49
Alessandro SenoAlessandro Seno
111
answered Sep 14 '17 at 0:49
Alessandro SenoAlessandro Seno
111
answered Sep 14 '17 at 0:49
Alessandro SenoAlessandro Seno
111
111
add a comment |
add a comment |
No necro-posting here (OP is already 6 months old) but I had the same issue and was locked out of my one available desktop gnome-terminal, with no way to download and install another one, apart from dropping to console. Similarly to OP I had set gnome-terminal up and ran an invalid custom command instead of my shell.
My "desktop" solution was to reset gnome-terminal's settings by way of dconf.
Just navigate to /org/gnome/terminal, highlight "legacy", right click and choose "reset recursively" ... (in the end, a very minor case of cold sweat).
In the process you will lose yr gnome-terminal settings and any profile you had. However relaunching terminal and starting again from scratch becomes immediately possible.
HTH future lx apprentice sorcerers.
answered Oct 12 '17 at 18:00
CbhiheCbhihe
3031316
add a comment |
No necro-posting here (OP is already 6 months old) but I had the same issue and was locked out of my one available desktop gnome-terminal, with no way to download and install another one, apart from dropping to console. Similarly to OP I had set gnome-terminal up and ran an invalid custom command instead of my shell.
My "desktop" solution was to reset gnome-terminal's settings by way of dconf.
Just navigate to /org/gnome/terminal, highlight "legacy", right click and choose "reset recursively" ... (in the end, a very minor case of cold sweat).
In the process you will lose yr gnome-terminal settings and any profile you had. However relaunching terminal and starting again from scratch becomes immediately possible.
HTH future lx apprentice sorcerers.
answered Oct 12 '17 at 18:00
CbhiheCbhihe
3031316
add a comment |
No necro-posting here (OP is already 6 months old) but I had the same issue and was locked out of my one available desktop gnome-terminal, with no way to download and install another one, apart from dropping to console. Similarly to OP I had set gnome-terminal up and ran an invalid custom command instead of my shell.
My "desktop" solution was to reset gnome-terminal's settings by way of dconf.
Just navigate to /org/gnome/terminal, highlight "legacy", right click and choose "reset recursively" ... (in the end, a very minor case of cold sweat).
In the process you will lose yr gnome-terminal settings and any profile you had. However relaunching terminal and starting again from scratch becomes immediately possible.
HTH future lx apprentice sorcerers.
answered Oct 12 '17 at 18:00
CbhiheCbhihe
3031316
No necro-posting here (OP is already 6 months old) but I had the same issue and was locked out of my one available desktop gnome-terminal, with no way to download and install another one, apart from dropping to console. Similarly to OP I had set gnome-terminal up and ran an invalid custom command instead of my shell.
My "desktop" solution was to reset gnome-terminal's settings by way of dconf.
Just navigate to /org/gnome/terminal, highlight "legacy", right click and choose "reset recursively" ... (in the end, a very minor case of cold sweat).
In the process you will lose yr gnome-terminal settings and any profile you had. However relaunching terminal and starting again from scratch becomes immediately possible.
HTH future lx apprentice sorcerers.
answered Oct 12 '17 at 18:00
CbhiheCbhihe
3031316
answered Oct 12 '17 at 18:00
CbhiheCbhihe
3031316
answered Oct 12 '17 at 18:00
CbhiheCbhihe
3031316
answered Oct 12 '17 at 18:00
CbhiheCbhihe
3031316
3031316
add a comment |
add a comment |
I used dconf tool to work on my way to /org/gnome/terminal/profiles/xxxprofile. Cleared the entry in "custom-command" box, unchecked "use-custom-command" checkbox and cleared the entry in the "visible-name" box.
Terminal function returned to normal.
edited Mar 30 '18 at 15:19
Yurij Goncharuk
2,3232522
answered Mar 30 '18 at 13:41
GordKGordK
11
add a comment |
I used dconf tool to work on my way to /org/gnome/terminal/profiles/xxxprofile. Cleared the entry in "custom-command" box, unchecked "use-custom-command" checkbox and cleared the entry in the "visible-name" box.
Terminal function returned to normal.
edited Mar 30 '18 at 15:19
Yurij Goncharuk
2,3232522
answered Mar 30 '18 at 13:41
GordKGordK
11
add a comment |
I used dconf tool to work on my way to /org/gnome/terminal/profiles/xxxprofile. Cleared the entry in "custom-command" box, unchecked "use-custom-command" checkbox and cleared the entry in the "visible-name" box.
Terminal function returned to normal.
edited Mar 30 '18 at 15:19
Yurij Goncharuk
2,3232522
answered Mar 30 '18 at 13:41
GordKGordK
11
I used dconf tool to work on my way to /org/gnome/terminal/profiles/xxxprofile. Cleared the entry in "custom-command" box, unchecked "use-custom-command" checkbox and cleared the entry in the "visible-name" box.
Terminal function returned to normal.
edited Mar 30 '18 at 15:19
Yurij Goncharuk
2,3232522
answered Mar 30 '18 at 13:41
GordKGordK
11
edited Mar 30 '18 at 15:19
Yurij Goncharuk
2,3232522
edited Mar 30 '18 at 15:19
Yurij Goncharuk
2,3232522
edited Mar 30 '18 at 15:19
Yurij Goncharuk
2,3232522
2,3232522
answered Mar 30 '18 at 13:41
GordKGordK
11
answered Mar 30 '18 at 13:41
GordKGordK
11
answered Mar 30 '18 at 13:41
GordKGordK
11
11
add a comment |
add a comment |
What I actually did was to install dconf then open dconf-editor and going to org/gnome/terminal/legacy/keybindings/preferences, setting the shortcut to <Ctrl><Shift>r (any other not used would do as well) and pressing it before the terminal closes. I went on from there and removed the preference I had made. Having tried everything else, this was my last idea and it worked.
answered 51 mins ago
SteliosKSteliosK
1
New contributor
SteliosK is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
What I actually did was to install dconf then open dconf-editor and going to org/gnome/terminal/legacy/keybindings/preferences, setting the shortcut to <Ctrl><Shift>r (any other not used would do as well) and pressing it before the terminal closes. I went on from there and removed the preference I had made. Having tried everything else, this was my last idea and it worked.
answered 51 mins ago
SteliosKSteliosK
1
New contributor
SteliosK is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
What I actually did was to install dconf then open dconf-editor and going to org/gnome/terminal/legacy/keybindings/preferences, setting the shortcut to <Ctrl><Shift>r (any other not used would do as well) and pressing it before the terminal closes. I went on from there and removed the preference I had made. Having tried everything else, this was my last idea and it worked.
answered 51 mins ago
SteliosKSteliosK
1
New contributor
SteliosK is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
What I actually did was to install dconf then open dconf-editor and going to org/gnome/terminal/legacy/keybindings/preferences, setting the shortcut to <Ctrl><Shift>r (any other not used would do as well) and pressing it before the terminal closes. I went on from there and removed the preference I had made. Having tried everything else, this was my last idea and it worked.
answered 51 mins ago
SteliosKSteliosK
1
New contributor
SteliosK is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 51 mins ago
SteliosKSteliosK
1
New contributor
SteliosK is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 51 mins ago
SteliosKSteliosK
1
answered 51 mins ago
SteliosKSteliosK
1
1
New contributor
SteliosK is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
SteliosK is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
SteliosK is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f360873%2freset-terminal-profile-preferences-without-using-terminal%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
Are you using
gnome-terminal(i.e. the default one from Ubuntu)? If so, one idea would be to search inside your$HOMEdirectory for its settings. Maybe with afind $HOME -iname '*terminal*'– thiagowfx
Apr 24 '17 at 3:48
A second idea would be to find its settings with either
dconforgsettings.– thiagowfx
Apr 24 '17 at 3:49
1
Thanks for the quick reply. I used XTerm to use the command 'dconf reset -f /org/gnome/terminal/legacy/profiles:/' (Sorry commented too soon there before). Thanks for the help :) @thiagowfx
– Bradley
Apr 24 '17 at 4:57
This does not really fix your problem, right? You are just using a different terminal. Anyway, at least you can be productive meanwhile :)
– thiagowfx
Apr 24 '17 at 4:59
It did fix the problem just commented too soon :P
– Bradley
Apr 24 '17 at 5:01