Various services (Terminal, gnome-disks, TTY) won't launch until I log out / back in The 2019 Stack Overflow Developer Survey Results Are InCannot open Gnome-Terminal Ubuntu 17.10Window Manager and Login Screen Removed After Trying and Uninstalling Gnome ShellCan't launch gnome-terminalLaunch gnome-terminal into GUI via TTYServer with GUI, can't get elevated privileges with Chrome Remote DesktopBroken Desktop & unable to boot to fresh USB to reinstall.Ubuntu GNOME 17.04 problems now that I've switched full timeChrome not starting after auto-loginUse a different window manager with gnome3?Unable to end session/log out using lightdm (16.04)After upgrade from 16.04 LTS to 18.04 LTS, display manager fails apparently because of freedesktop
Is it okay to consider publishing in my first year of PhD?
Deal with toxic manager when you can't quit
Why didn't the Event Horizon Telescope team mention Sagittarius A*?
What do I do when my TA workload is more than expected?
Why does the nucleus not repel itself?
Straighten subgroup lattice
What is this business jet?
Keeping a retro style to sci-fi spaceships?
What do these terms in Caesar's Gallic Wars mean?
Can there be female White Walkers?
Why couldn't they take pictures of a closer black hole?
Can I have a signal generator on while it's not connected?
Are there any other methods to apply to solving simultaneous equations?
What's the name of these plastic connectors
Output the Arecibo Message
Did any laptop computers have a built-in 5 1/4 inch floppy drive?
Why isn't the circumferential light around the M87 black hole's event horizon symmetric?
What does Linus Torvalds mean when he says that Git "never ever" tracks a file?
Why doesn't shell automatically fix "useless use of cat"?
Dropping list elements from nested list after evaluation
Star Trek - X-shaped Item on Regula/Orbital Office Starbases
Slides for 30 min~1 hr Skype tenure track application interview
Is it ethical to upload a automatically generated paper to a non peer-reviewed site as part of a larger research?
Why “相同意思的词” is called “同义词” instead of "同意词"?
Various services (Terminal, gnome-disks, TTY) won't launch until I log out / back in
The 2019 Stack Overflow Developer Survey Results Are InCannot open Gnome-Terminal Ubuntu 17.10Window Manager and Login Screen Removed After Trying and Uninstalling Gnome ShellCan't launch gnome-terminalLaunch gnome-terminal into GUI via TTYServer with GUI, can't get elevated privileges with Chrome Remote DesktopBroken Desktop & unable to boot to fresh USB to reinstall.Ubuntu GNOME 17.04 problems now that I've switched full timeChrome not starting after auto-loginUse a different window manager with gnome3?Unable to end session/log out using lightdm (16.04)After upgrade from 16.04 LTS to 18.04 LTS, display manager fails apparently because of freedesktop
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
Like this guy I have lost the ability to use several core Ubuntu apps - most notably, terminal and gnome-disks. When I try to launch them, I get a spinner for a few seconds and sometimes an entry in the window bar, then nothing. Amazingly, the emergency terminals (TTY?) I can normally depend on to save the day also don't work. If I press ctrl + alt + F*, nothing happens.
Spinner icon screenshot
By default, my desktop environment auto logs in. I discovered that if I log out, then log back in from the top right menu, Terminal (and the TTY shortcuts) start working. Strangely, gnome-disks from the launcher menu still doesn't, but if I invoke it from the terminal, it launches fine.
When I looked at my logs for a failed gnome-disks invocation, I see this:
[session uid=1000 pid=2863] Activating service name='org.gnome.DiskUtility' requested by ':1.46' (uid=1000 pid=3519 comm="/usr/bin/gnome-shell " label="unconfined")
[session uid=1000 pid=2863] Successfully activated service 'org.gnome.DiskUtility'
Unable to init server: Could not connect: Connection refused
cannot open display: :20
I am working directly on this Ubuntu machine - no SSH involved - but I think these problems may have started when I set up Chrome Remote Desktop. I've tried adding an sshd_config file as others suggested, but no dice.
My theory is that something's broken with the desktop environment (window manager?) and it doesn't know what display it's meant to send stuff to. Terminal somehow does. Any ideas how I can debug further or fix?
unity gnome
New contributor
|
show 1 more comment
Like this guy I have lost the ability to use several core Ubuntu apps - most notably, terminal and gnome-disks. When I try to launch them, I get a spinner for a few seconds and sometimes an entry in the window bar, then nothing. Amazingly, the emergency terminals (TTY?) I can normally depend on to save the day also don't work. If I press ctrl + alt + F*, nothing happens.
Spinner icon screenshot
By default, my desktop environment auto logs in. I discovered that if I log out, then log back in from the top right menu, Terminal (and the TTY shortcuts) start working. Strangely, gnome-disks from the launcher menu still doesn't, but if I invoke it from the terminal, it launches fine.
When I looked at my logs for a failed gnome-disks invocation, I see this:
[session uid=1000 pid=2863] Activating service name='org.gnome.DiskUtility' requested by ':1.46' (uid=1000 pid=3519 comm="/usr/bin/gnome-shell " label="unconfined")
[session uid=1000 pid=2863] Successfully activated service 'org.gnome.DiskUtility'
Unable to init server: Could not connect: Connection refused
cannot open display: :20
I am working directly on this Ubuntu machine - no SSH involved - but I think these problems may have started when I set up Chrome Remote Desktop. I've tried adding an sshd_config file as others suggested, but no dice.
My theory is that something's broken with the desktop environment (window manager?) and it doesn't know what display it's meant to send stuff to. Terminal somehow does. Any ideas how I can debug further or fix?
unity gnome
New contributor
1
What version Ubuntu? If you log out, at the login screen, after selecting/entering your username, do you see a cogwheel icon? If so, can you tell which environment is selected? If not, is there a "Ubuntu" or "Ubuntu on xorg" choice. Select it and retry Disks app.
– heynnema
2 days ago
18.04.2 LTS. The options behind the cog are "Ubuntu" and "Ubuntu on Wayland" - the former is selected. Let me try the latter now and report back, last time I tried I lost Chrome + this comment ;)
– Crispin Hershey
2 days ago
Disks works! Terminal works! What does Wayland mean, and how / should I make it the default when I auto login?
– Crispin Hershey
2 days ago
You're running with Wayland right now, correct? Wayland is not ready for prime time. Lets see if we can figure out what happened to the "Ubuntu" environment. Try selecting it again at the login screen, and see if it still fails. What was involved with setting up Chrome Remote Desktop?
– heynnema
2 days ago
When I log in using Wayland, everything works. If I switch back to regular Ubuntu, things keep working - until I reboot, then I need to go through Wayland once to fix it up again. Unfortunately the Chrome Remote Desktop installer was both opaque (I have no idea what it touched) and for a new beta version (browser based, I think). I'd really like to avoid reformatting... does this symptom sound related to a specific config file or memory block I could look at before and after a Wayland trip?
– Crispin Hershey
2 days ago
|
show 1 more comment
Like this guy I have lost the ability to use several core Ubuntu apps - most notably, terminal and gnome-disks. When I try to launch them, I get a spinner for a few seconds and sometimes an entry in the window bar, then nothing. Amazingly, the emergency terminals (TTY?) I can normally depend on to save the day also don't work. If I press ctrl + alt + F*, nothing happens.
Spinner icon screenshot
By default, my desktop environment auto logs in. I discovered that if I log out, then log back in from the top right menu, Terminal (and the TTY shortcuts) start working. Strangely, gnome-disks from the launcher menu still doesn't, but if I invoke it from the terminal, it launches fine.
When I looked at my logs for a failed gnome-disks invocation, I see this:
[session uid=1000 pid=2863] Activating service name='org.gnome.DiskUtility' requested by ':1.46' (uid=1000 pid=3519 comm="/usr/bin/gnome-shell " label="unconfined")
[session uid=1000 pid=2863] Successfully activated service 'org.gnome.DiskUtility'
Unable to init server: Could not connect: Connection refused
cannot open display: :20
I am working directly on this Ubuntu machine - no SSH involved - but I think these problems may have started when I set up Chrome Remote Desktop. I've tried adding an sshd_config file as others suggested, but no dice.
My theory is that something's broken with the desktop environment (window manager?) and it doesn't know what display it's meant to send stuff to. Terminal somehow does. Any ideas how I can debug further or fix?
unity gnome
New contributor
Like this guy I have lost the ability to use several core Ubuntu apps - most notably, terminal and gnome-disks. When I try to launch them, I get a spinner for a few seconds and sometimes an entry in the window bar, then nothing. Amazingly, the emergency terminals (TTY?) I can normally depend on to save the day also don't work. If I press ctrl + alt + F*, nothing happens.
Spinner icon screenshot
By default, my desktop environment auto logs in. I discovered that if I log out, then log back in from the top right menu, Terminal (and the TTY shortcuts) start working. Strangely, gnome-disks from the launcher menu still doesn't, but if I invoke it from the terminal, it launches fine.
When I looked at my logs for a failed gnome-disks invocation, I see this:
[session uid=1000 pid=2863] Activating service name='org.gnome.DiskUtility' requested by ':1.46' (uid=1000 pid=3519 comm="/usr/bin/gnome-shell " label="unconfined")
[session uid=1000 pid=2863] Successfully activated service 'org.gnome.DiskUtility'
Unable to init server: Could not connect: Connection refused
cannot open display: :20
I am working directly on this Ubuntu machine - no SSH involved - but I think these problems may have started when I set up Chrome Remote Desktop. I've tried adding an sshd_config file as others suggested, but no dice.
My theory is that something's broken with the desktop environment (window manager?) and it doesn't know what display it's meant to send stuff to. Terminal somehow does. Any ideas how I can debug further or fix?
unity gnome
unity gnome
New contributor
New contributor
New contributor
asked 2 days ago
Crispin HersheyCrispin Hershey
1
1
New contributor
New contributor
1
What version Ubuntu? If you log out, at the login screen, after selecting/entering your username, do you see a cogwheel icon? If so, can you tell which environment is selected? If not, is there a "Ubuntu" or "Ubuntu on xorg" choice. Select it and retry Disks app.
– heynnema
2 days ago
18.04.2 LTS. The options behind the cog are "Ubuntu" and "Ubuntu on Wayland" - the former is selected. Let me try the latter now and report back, last time I tried I lost Chrome + this comment ;)
– Crispin Hershey
2 days ago
Disks works! Terminal works! What does Wayland mean, and how / should I make it the default when I auto login?
– Crispin Hershey
2 days ago
You're running with Wayland right now, correct? Wayland is not ready for prime time. Lets see if we can figure out what happened to the "Ubuntu" environment. Try selecting it again at the login screen, and see if it still fails. What was involved with setting up Chrome Remote Desktop?
– heynnema
2 days ago
When I log in using Wayland, everything works. If I switch back to regular Ubuntu, things keep working - until I reboot, then I need to go through Wayland once to fix it up again. Unfortunately the Chrome Remote Desktop installer was both opaque (I have no idea what it touched) and for a new beta version (browser based, I think). I'd really like to avoid reformatting... does this symptom sound related to a specific config file or memory block I could look at before and after a Wayland trip?
– Crispin Hershey
2 days ago
|
show 1 more comment
1
What version Ubuntu? If you log out, at the login screen, after selecting/entering your username, do you see a cogwheel icon? If so, can you tell which environment is selected? If not, is there a "Ubuntu" or "Ubuntu on xorg" choice. Select it and retry Disks app.
– heynnema
2 days ago
18.04.2 LTS. The options behind the cog are "Ubuntu" and "Ubuntu on Wayland" - the former is selected. Let me try the latter now and report back, last time I tried I lost Chrome + this comment ;)
– Crispin Hershey
2 days ago
Disks works! Terminal works! What does Wayland mean, and how / should I make it the default when I auto login?
– Crispin Hershey
2 days ago
You're running with Wayland right now, correct? Wayland is not ready for prime time. Lets see if we can figure out what happened to the "Ubuntu" environment. Try selecting it again at the login screen, and see if it still fails. What was involved with setting up Chrome Remote Desktop?
– heynnema
2 days ago
When I log in using Wayland, everything works. If I switch back to regular Ubuntu, things keep working - until I reboot, then I need to go through Wayland once to fix it up again. Unfortunately the Chrome Remote Desktop installer was both opaque (I have no idea what it touched) and for a new beta version (browser based, I think). I'd really like to avoid reformatting... does this symptom sound related to a specific config file or memory block I could look at before and after a Wayland trip?
– Crispin Hershey
2 days ago
1
1
What version Ubuntu? If you log out, at the login screen, after selecting/entering your username, do you see a cogwheel icon? If so, can you tell which environment is selected? If not, is there a "Ubuntu" or "Ubuntu on xorg" choice. Select it and retry Disks app.
– heynnema
2 days ago
What version Ubuntu? If you log out, at the login screen, after selecting/entering your username, do you see a cogwheel icon? If so, can you tell which environment is selected? If not, is there a "Ubuntu" or "Ubuntu on xorg" choice. Select it and retry Disks app.
– heynnema
2 days ago
18.04.2 LTS. The options behind the cog are "Ubuntu" and "Ubuntu on Wayland" - the former is selected. Let me try the latter now and report back, last time I tried I lost Chrome + this comment ;)
– Crispin Hershey
2 days ago
18.04.2 LTS. The options behind the cog are "Ubuntu" and "Ubuntu on Wayland" - the former is selected. Let me try the latter now and report back, last time I tried I lost Chrome + this comment ;)
– Crispin Hershey
2 days ago
Disks works! Terminal works! What does Wayland mean, and how / should I make it the default when I auto login?
– Crispin Hershey
2 days ago
Disks works! Terminal works! What does Wayland mean, and how / should I make it the default when I auto login?
– Crispin Hershey
2 days ago
You're running with Wayland right now, correct? Wayland is not ready for prime time. Lets see if we can figure out what happened to the "Ubuntu" environment. Try selecting it again at the login screen, and see if it still fails. What was involved with setting up Chrome Remote Desktop?
– heynnema
2 days ago
You're running with Wayland right now, correct? Wayland is not ready for prime time. Lets see if we can figure out what happened to the "Ubuntu" environment. Try selecting it again at the login screen, and see if it still fails. What was involved with setting up Chrome Remote Desktop?
– heynnema
2 days ago
When I log in using Wayland, everything works. If I switch back to regular Ubuntu, things keep working - until I reboot, then I need to go through Wayland once to fix it up again. Unfortunately the Chrome Remote Desktop installer was both opaque (I have no idea what it touched) and for a new beta version (browser based, I think). I'd really like to avoid reformatting... does this symptom sound related to a specific config file or memory block I could look at before and after a Wayland trip?
– Crispin Hershey
2 days ago
When I log in using Wayland, everything works. If I switch back to regular Ubuntu, things keep working - until I reboot, then I need to go through Wayland once to fix it up again. Unfortunately the Chrome Remote Desktop installer was both opaque (I have no idea what it touched) and for a new beta version (browser based, I think). I'd really like to avoid reformatting... does this symptom sound related to a specific config file or memory block I could look at before and after a Wayland trip?
– Crispin Hershey
2 days ago
|
show 1 more comment
1 Answer
1
active
oldest
votes
The goal is to make the "Ubuntu" environment work for you, and to move away from Wayland, as it's not really ready for prime time. There are a number of things that can be checked/tried.
Try and uninstall the
Chrome Remote Desktop
and the betaChrome
browser. Reboot. Retest the terminal app.In
terminal
, typesudo dpkg-reconfigure gdm3
, selectgdm3
, then reboot. Reboot into the "Ubuntu" environment and see if things are working now.HOLD on this until we talk... after steps 1 & 2...
You may have a problem with an older computer, with an older GPU. Try this...
- boot to recovery mode
- choose root access
type:
sudo mount -o remount,rw / # to remount the disk r/w
sudo pico /etc/gdm3/custom.conf # edit this file
change:
#WaylandEnable=false
to:
WaylandEnable=false
Then reboot.
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
);
);
Crispin Hershey is a new contributor. Be nice, and check out our Code of Conduct.
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%2f1132442%2fvarious-services-terminal-gnome-disks-tty-wont-launch-until-i-log-out-bac%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The goal is to make the "Ubuntu" environment work for you, and to move away from Wayland, as it's not really ready for prime time. There are a number of things that can be checked/tried.
Try and uninstall the
Chrome Remote Desktop
and the betaChrome
browser. Reboot. Retest the terminal app.In
terminal
, typesudo dpkg-reconfigure gdm3
, selectgdm3
, then reboot. Reboot into the "Ubuntu" environment and see if things are working now.HOLD on this until we talk... after steps 1 & 2...
You may have a problem with an older computer, with an older GPU. Try this...
- boot to recovery mode
- choose root access
type:
sudo mount -o remount,rw / # to remount the disk r/w
sudo pico /etc/gdm3/custom.conf # edit this file
change:
#WaylandEnable=false
to:
WaylandEnable=false
Then reboot.
add a comment |
The goal is to make the "Ubuntu" environment work for you, and to move away from Wayland, as it's not really ready for prime time. There are a number of things that can be checked/tried.
Try and uninstall the
Chrome Remote Desktop
and the betaChrome
browser. Reboot. Retest the terminal app.In
terminal
, typesudo dpkg-reconfigure gdm3
, selectgdm3
, then reboot. Reboot into the "Ubuntu" environment and see if things are working now.HOLD on this until we talk... after steps 1 & 2...
You may have a problem with an older computer, with an older GPU. Try this...
- boot to recovery mode
- choose root access
type:
sudo mount -o remount,rw / # to remount the disk r/w
sudo pico /etc/gdm3/custom.conf # edit this file
change:
#WaylandEnable=false
to:
WaylandEnable=false
Then reboot.
add a comment |
The goal is to make the "Ubuntu" environment work for you, and to move away from Wayland, as it's not really ready for prime time. There are a number of things that can be checked/tried.
Try and uninstall the
Chrome Remote Desktop
and the betaChrome
browser. Reboot. Retest the terminal app.In
terminal
, typesudo dpkg-reconfigure gdm3
, selectgdm3
, then reboot. Reboot into the "Ubuntu" environment and see if things are working now.HOLD on this until we talk... after steps 1 & 2...
You may have a problem with an older computer, with an older GPU. Try this...
- boot to recovery mode
- choose root access
type:
sudo mount -o remount,rw / # to remount the disk r/w
sudo pico /etc/gdm3/custom.conf # edit this file
change:
#WaylandEnable=false
to:
WaylandEnable=false
Then reboot.
The goal is to make the "Ubuntu" environment work for you, and to move away from Wayland, as it's not really ready for prime time. There are a number of things that can be checked/tried.
Try and uninstall the
Chrome Remote Desktop
and the betaChrome
browser. Reboot. Retest the terminal app.In
terminal
, typesudo dpkg-reconfigure gdm3
, selectgdm3
, then reboot. Reboot into the "Ubuntu" environment and see if things are working now.HOLD on this until we talk... after steps 1 & 2...
You may have a problem with an older computer, with an older GPU. Try this...
- boot to recovery mode
- choose root access
type:
sudo mount -o remount,rw / # to remount the disk r/w
sudo pico /etc/gdm3/custom.conf # edit this file
change:
#WaylandEnable=false
to:
WaylandEnable=false
Then reboot.
answered yesterday
heynnemaheynnema
21.5k32361
21.5k32361
add a comment |
add a comment |
Crispin Hershey is a new contributor. Be nice, and check out our Code of Conduct.
Crispin Hershey is a new contributor. Be nice, and check out our Code of Conduct.
Crispin Hershey is a new contributor. Be nice, and check out our Code of Conduct.
Crispin Hershey is a new contributor. Be nice, and check out our Code of Conduct.
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%2f1132442%2fvarious-services-terminal-gnome-disks-tty-wont-launch-until-i-log-out-bac%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
What version Ubuntu? If you log out, at the login screen, after selecting/entering your username, do you see a cogwheel icon? If so, can you tell which environment is selected? If not, is there a "Ubuntu" or "Ubuntu on xorg" choice. Select it and retry Disks app.
– heynnema
2 days ago
18.04.2 LTS. The options behind the cog are "Ubuntu" and "Ubuntu on Wayland" - the former is selected. Let me try the latter now and report back, last time I tried I lost Chrome + this comment ;)
– Crispin Hershey
2 days ago
Disks works! Terminal works! What does Wayland mean, and how / should I make it the default when I auto login?
– Crispin Hershey
2 days ago
You're running with Wayland right now, correct? Wayland is not ready for prime time. Lets see if we can figure out what happened to the "Ubuntu" environment. Try selecting it again at the login screen, and see if it still fails. What was involved with setting up Chrome Remote Desktop?
– heynnema
2 days ago
When I log in using Wayland, everything works. If I switch back to regular Ubuntu, things keep working - until I reboot, then I need to go through Wayland once to fix it up again. Unfortunately the Chrome Remote Desktop installer was both opaque (I have no idea what it touched) and for a new beta version (browser based, I think). I'd really like to avoid reformatting... does this symptom sound related to a specific config file or memory block I could look at before and after a Wayland trip?
– Crispin Hershey
2 days ago