gnome-terminal will not load, sudo gnome-terminal will
My gnome-terminal appears to have stopped working. Clicking the icon, Ctrl+Alt+T, and Alt+F2 -> gnome-terminal all have the same effect: the mouse changes to a spinner, the icon shows that gnome-terminal is loading, but then after a few seconds, things go back to where they were before.
I've read a number of threads linking this to a locale setting issue, but none of those answers have worked for me (sudo locale-gen --purge, resetting the locale, etc.).
As with many of the other people who have reported a problem like this, the error message I get from MATE terminal is this: Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached.
I also tried uninstalling and reinstalling gnome-terminal to no avail.
On a whim, I tried sudo gnome-terminal, and this loads up correctly. From here, I can login username and now I can use my terminal normally. I tried cp /etc/skel/.bashrc ~/ + relogging to see if maybe there was something wrong with my .bashrc; this changed nothing.
I'm not sure if it's related, but I'm also now receiving an error message that my default keyring hasn't been unlocked upon logging in, which never happened before.
What could be causing this?
command-line gnome gnome-terminal
asked Oct 12 '18 at 16:14
deckeresqdeckeresq
1163
add a comment |
My gnome-terminal appears to have stopped working. Clicking the icon, Ctrl+Alt+T, and Alt+F2 -> gnome-terminal all have the same effect: the mouse changes to a spinner, the icon shows that gnome-terminal is loading, but then after a few seconds, things go back to where they were before.
I've read a number of threads linking this to a locale setting issue, but none of those answers have worked for me (sudo locale-gen --purge, resetting the locale, etc.).
As with many of the other people who have reported a problem like this, the error message I get from MATE terminal is this: Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached.
I also tried uninstalling and reinstalling gnome-terminal to no avail.
On a whim, I tried sudo gnome-terminal, and this loads up correctly. From here, I can login username and now I can use my terminal normally. I tried cp /etc/skel/.bashrc ~/ + relogging to see if maybe there was something wrong with my .bashrc; this changed nothing.
I'm not sure if it's related, but I'm also now receiving an error message that my default keyring hasn't been unlocked upon logging in, which never happened before.
What could be causing this?
command-line gnome gnome-terminal
asked Oct 12 '18 at 16:14
deckeresqdeckeresq
1163
add a comment |
My gnome-terminal appears to have stopped working. Clicking the icon, Ctrl+Alt+T, and Alt+F2 -> gnome-terminal all have the same effect: the mouse changes to a spinner, the icon shows that gnome-terminal is loading, but then after a few seconds, things go back to where they were before.
I've read a number of threads linking this to a locale setting issue, but none of those answers have worked for me (sudo locale-gen --purge, resetting the locale, etc.).
As with many of the other people who have reported a problem like this, the error message I get from MATE terminal is this: Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached.
I also tried uninstalling and reinstalling gnome-terminal to no avail.
On a whim, I tried sudo gnome-terminal, and this loads up correctly. From here, I can login username and now I can use my terminal normally. I tried cp /etc/skel/.bashrc ~/ + relogging to see if maybe there was something wrong with my .bashrc; this changed nothing.
I'm not sure if it's related, but I'm also now receiving an error message that my default keyring hasn't been unlocked upon logging in, which never happened before.
What could be causing this?
command-line gnome gnome-terminal
asked Oct 12 '18 at 16:14
deckeresqdeckeresq
1163
My gnome-terminal appears to have stopped working. Clicking the icon, Ctrl+Alt+T, and Alt+F2 -> gnome-terminal all have the same effect: the mouse changes to a spinner, the icon shows that gnome-terminal is loading, but then after a few seconds, things go back to where they were before.
I've read a number of threads linking this to a locale setting issue, but none of those answers have worked for me (sudo locale-gen --purge, resetting the locale, etc.).
As with many of the other people who have reported a problem like this, the error message I get from MATE terminal is this: Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached.
I also tried uninstalling and reinstalling gnome-terminal to no avail.
On a whim, I tried sudo gnome-terminal, and this loads up correctly. From here, I can login username and now I can use my terminal normally. I tried cp /etc/skel/.bashrc ~/ + relogging to see if maybe there was something wrong with my .bashrc; this changed nothing.
I'm not sure if it's related, but I'm also now receiving an error message that my default keyring hasn't been unlocked upon logging in, which never happened before.
What could be causing this?
command-line gnome gnome-terminal
command-line gnome gnome-terminal
asked Oct 12 '18 at 16:14
deckeresqdeckeresq
1163
asked Oct 12 '18 at 16:14
deckeresqdeckeresq
1163
edited Oct 12 '18 at 16:26
deckeresq
asked Oct 12 '18 at 16:14
deckeresqdeckeresq
1163
asked Oct 12 '18 at 16:14
deckeresqdeckeresq
1163
asked Oct 12 '18 at 16:14
deckeresqdeckeresq
1163
1163
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
In terminal, try this...
cd # change to home directory
ls -al .*auth* # list some important files
-rw------- 1 decker decker 405834 Oct 11 07:39 .ICEauthority
-rw------- 1 decker decker 58 Jun 23 2017 .Xauthority
The "decker" name might be slightly different, depending on your actual username.
If it shows anything other than rw, or different usernames, you'll need to either:
cd # change to home directory
sudo chmod 600 .*auth* # set to rw
sudo chown decker:decker .*auth* # change the username if need be
Regarding the keyring, make sure that your actual login password is the same for the Default/Login keyring(s). Use the Password and Keys (18.04.1) app to change it.
answered Oct 12 '18 at 17:13
heynnemaheynnema
20.5k22258
1
Thanks! It does show rw, so it doesn't look like that fixed the issue. I ended up just reformatting the drive because I couldn't wait much longer due to some deadlines, so I guess it'll stay a mystery. After some further digging, I found that my sound was messed up and the driver was now listed as something related to chrome-remote-desktop, so I'm curious if something got broken there. Thanks for the ideas!
– deckeresq
Oct 14 '18 at 0:12
add a comment |
I got this - it coincided with suddenly needing to enter a Keyring password on every login. I think that started after installing chrome-remote-desktop.
It also screwed my sound - no sound device:
The fix is here:
Installing Google Chrome Remote Desktop messed up my box
All I had to do was
sudo rm -rf ~/.config/chrome-remote-desktop
and reboot.
I got my sound back
and I could launch gnome-terminal again
chrome-remote-desktop was the culprit
answered 1 hour ago
NoctiluqueNoctiluque
1011
New contributor
Noctiluque 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: "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%2f1083265%2fgnome-terminal-will-not-load-sudo-gnome-terminal-will%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
In terminal, try this...
cd # change to home directory
ls -al .*auth* # list some important files
-rw------- 1 decker decker 405834 Oct 11 07:39 .ICEauthority
-rw------- 1 decker decker 58 Jun 23 2017 .Xauthority
The "decker" name might be slightly different, depending on your actual username.
If it shows anything other than rw, or different usernames, you'll need to either:
cd # change to home directory
sudo chmod 600 .*auth* # set to rw
sudo chown decker:decker .*auth* # change the username if need be
Regarding the keyring, make sure that your actual login password is the same for the Default/Login keyring(s). Use the Password and Keys (18.04.1) app to change it.
answered Oct 12 '18 at 17:13
heynnemaheynnema
20.5k22258
1
Thanks! It does show rw, so it doesn't look like that fixed the issue. I ended up just reformatting the drive because I couldn't wait much longer due to some deadlines, so I guess it'll stay a mystery. After some further digging, I found that my sound was messed up and the driver was now listed as something related to chrome-remote-desktop, so I'm curious if something got broken there. Thanks for the ideas!
– deckeresq
Oct 14 '18 at 0:12
add a comment |
In terminal, try this...
cd # change to home directory
ls -al .*auth* # list some important files
-rw------- 1 decker decker 405834 Oct 11 07:39 .ICEauthority
-rw------- 1 decker decker 58 Jun 23 2017 .Xauthority
The "decker" name might be slightly different, depending on your actual username.
If it shows anything other than rw, or different usernames, you'll need to either:
cd # change to home directory
sudo chmod 600 .*auth* # set to rw
sudo chown decker:decker .*auth* # change the username if need be
Regarding the keyring, make sure that your actual login password is the same for the Default/Login keyring(s). Use the Password and Keys (18.04.1) app to change it.
answered Oct 12 '18 at 17:13
heynnemaheynnema
20.5k22258
1
Thanks! It does show rw, so it doesn't look like that fixed the issue. I ended up just reformatting the drive because I couldn't wait much longer due to some deadlines, so I guess it'll stay a mystery. After some further digging, I found that my sound was messed up and the driver was now listed as something related to chrome-remote-desktop, so I'm curious if something got broken there. Thanks for the ideas!
– deckeresq
Oct 14 '18 at 0:12
add a comment |
In terminal, try this...
cd # change to home directory
ls -al .*auth* # list some important files
-rw------- 1 decker decker 405834 Oct 11 07:39 .ICEauthority
-rw------- 1 decker decker 58 Jun 23 2017 .Xauthority
The "decker" name might be slightly different, depending on your actual username.
If it shows anything other than rw, or different usernames, you'll need to either:
cd # change to home directory
sudo chmod 600 .*auth* # set to rw
sudo chown decker:decker .*auth* # change the username if need be
Regarding the keyring, make sure that your actual login password is the same for the Default/Login keyring(s). Use the Password and Keys (18.04.1) app to change it.
answered Oct 12 '18 at 17:13
heynnemaheynnema
20.5k22258
In terminal, try this...
cd # change to home directory
ls -al .*auth* # list some important files
-rw------- 1 decker decker 405834 Oct 11 07:39 .ICEauthority
-rw------- 1 decker decker 58 Jun 23 2017 .Xauthority
The "decker" name might be slightly different, depending on your actual username.
If it shows anything other than rw, or different usernames, you'll need to either:
cd # change to home directory
sudo chmod 600 .*auth* # set to rw
sudo chown decker:decker .*auth* # change the username if need be
Regarding the keyring, make sure that your actual login password is the same for the Default/Login keyring(s). Use the Password and Keys (18.04.1) app to change it.
answered Oct 12 '18 at 17:13
heynnemaheynnema
20.5k22258
edited Oct 13 '18 at 16:38
answered Oct 12 '18 at 17:13
heynnemaheynnema
20.5k22258
answered Oct 12 '18 at 17:13
heynnemaheynnema
20.5k22258
answered Oct 12 '18 at 17:13
heynnemaheynnema
20.5k22258
20.5k22258
1
Thanks! It does show rw, so it doesn't look like that fixed the issue. I ended up just reformatting the drive because I couldn't wait much longer due to some deadlines, so I guess it'll stay a mystery. After some further digging, I found that my sound was messed up and the driver was now listed as something related to chrome-remote-desktop, so I'm curious if something got broken there. Thanks for the ideas!
– deckeresq
Oct 14 '18 at 0:12
add a comment |
1
Thanks! It does show rw, so it doesn't look like that fixed the issue. I ended up just reformatting the drive because I couldn't wait much longer due to some deadlines, so I guess it'll stay a mystery. After some further digging, I found that my sound was messed up and the driver was now listed as something related to chrome-remote-desktop, so I'm curious if something got broken there. Thanks for the ideas!
– deckeresq
Oct 14 '18 at 0:12
1
1
Thanks! It does show rw, so it doesn't look like that fixed the issue. I ended up just reformatting the drive because I couldn't wait much longer due to some deadlines, so I guess it'll stay a mystery. After some further digging, I found that my sound was messed up and the driver was now listed as something related to chrome-remote-desktop, so I'm curious if something got broken there. Thanks for the ideas!
– deckeresq
Oct 14 '18 at 0:12
Thanks! It does show rw, so it doesn't look like that fixed the issue. I ended up just reformatting the drive because I couldn't wait much longer due to some deadlines, so I guess it'll stay a mystery. After some further digging, I found that my sound was messed up and the driver was now listed as something related to chrome-remote-desktop, so I'm curious if something got broken there. Thanks for the ideas!
– deckeresq
Oct 14 '18 at 0:12
add a comment |
I got this - it coincided with suddenly needing to enter a Keyring password on every login. I think that started after installing chrome-remote-desktop.
It also screwed my sound - no sound device:
The fix is here:
Installing Google Chrome Remote Desktop messed up my box
All I had to do was
sudo rm -rf ~/.config/chrome-remote-desktop
and reboot.
I got my sound back
and I could launch gnome-terminal again
chrome-remote-desktop was the culprit
answered 1 hour ago
NoctiluqueNoctiluque
1011
New contributor
Noctiluque 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 |
I got this - it coincided with suddenly needing to enter a Keyring password on every login. I think that started after installing chrome-remote-desktop.
It also screwed my sound - no sound device:
The fix is here:
Installing Google Chrome Remote Desktop messed up my box
All I had to do was
sudo rm -rf ~/.config/chrome-remote-desktop
and reboot.
I got my sound back
and I could launch gnome-terminal again
chrome-remote-desktop was the culprit
answered 1 hour ago
NoctiluqueNoctiluque
1011
New contributor
Noctiluque 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 |
I got this - it coincided with suddenly needing to enter a Keyring password on every login. I think that started after installing chrome-remote-desktop.
It also screwed my sound - no sound device:
The fix is here:
Installing Google Chrome Remote Desktop messed up my box
All I had to do was
sudo rm -rf ~/.config/chrome-remote-desktop
and reboot.
I got my sound back
and I could launch gnome-terminal again
chrome-remote-desktop was the culprit
answered 1 hour ago
NoctiluqueNoctiluque
1011
New contributor
Noctiluque is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I got this - it coincided with suddenly needing to enter a Keyring password on every login. I think that started after installing chrome-remote-desktop.
It also screwed my sound - no sound device:
The fix is here:
Installing Google Chrome Remote Desktop messed up my box
All I had to do was
sudo rm -rf ~/.config/chrome-remote-desktop
and reboot.
I got my sound back
and I could launch gnome-terminal again
chrome-remote-desktop was the culprit
answered 1 hour ago
NoctiluqueNoctiluque
1011
New contributor
Noctiluque is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 55 mins ago
answered 1 hour ago
NoctiluqueNoctiluque
1011
New contributor
Noctiluque is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 1 hour ago
NoctiluqueNoctiluque
1011
answered 1 hour ago
NoctiluqueNoctiluque
1011
1011
New contributor
Noctiluque is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Noctiluque is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Noctiluque 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 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%2f1083265%2fgnome-terminal-will-not-load-sudo-gnome-terminal-will%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
