How to turn off Ubuntu 17.10's GUI (GDM)?
Unlike 17.04, sudo service stop gdm
or sudo service stop lightdm
will return stop: unrecognized service
, so my question being how to stop the GUI process in this bleeding edge version?
17.10
add a comment |
Unlike 17.04, sudo service stop gdm
or sudo service stop lightdm
will return stop: unrecognized service
, so my question being how to stop the GUI process in this bleeding edge version?
17.10
1
There is an error in the command you are using: You must usesudo service gdm stop
(stop gdm
is a mistake)
– Jaime
May 7 '18 at 13:17
add a comment |
Unlike 17.04, sudo service stop gdm
or sudo service stop lightdm
will return stop: unrecognized service
, so my question being how to stop the GUI process in this bleeding edge version?
17.10
Unlike 17.04, sudo service stop gdm
or sudo service stop lightdm
will return stop: unrecognized service
, so my question being how to stop the GUI process in this bleeding edge version?
17.10
17.10
asked Nov 23 '17 at 11:06
Aero WindwalkerAero Windwalker
4961615
4961615
1
There is an error in the command you are using: You must usesudo service gdm stop
(stop gdm
is a mistake)
– Jaime
May 7 '18 at 13:17
add a comment |
1
There is an error in the command you are using: You must usesudo service gdm stop
(stop gdm
is a mistake)
– Jaime
May 7 '18 at 13:17
1
1
There is an error in the command you are using: You must use
sudo service gdm stop
(stop gdm
is a mistake)– Jaime
May 7 '18 at 13:17
There is an error in the command you are using: You must use
sudo service gdm stop
(stop gdm
is a mistake)– Jaime
May 7 '18 at 13:17
add a comment |
3 Answers
3
active
oldest
votes
Instead of killing the gdm
, you can change the systemd target.
Changing the systemd target
As mentioned here, starting from 16.04, Ubuntu uses systemd
and the boot process relies on a set of targets
. Each target
defines the system software that Ubuntu must run.
This is a list of targets
for Ubuntu:
┌───────────────────┐
│ Target │
├───────────────────┤
│ poweroff.target │ turn off the computer
├───────────────────┤
│ rescue.target │ minimal for admin/rescue tasks
├───────────────────┤
│ multi-user.target │ multi-user, no GUI
├───────────────────┤
│ graphical.target │ multi-user, GUI
├───────────────────┤
│ reboot.target │ reboot the computer
└───────────────────┘
To stop the GUI, you can change the target
. The system checks all the running system software and kills those not included in the specified target. In consequence, if you change to the multi-user.target
target, the GUI will be killed.
To change the "target" and kill the GUI:
sudo systemctl isolate multi-user.target
To make this the default "target" (and start booting your computer without GUI), you can use:
sudo systemctl enable multi-user.target
sudo systemctl set-default multi-user.target
add a comment |
To stop it:
sudo systemctl gdm stop
To disable it completely:
sudo systemctl gdm disable
To start it:
sudo systemctl gdm start
and to re-enable it:
sudo systemctl gdm enable
To see the actually running services
systemctl --state running
I had problems after stoping the graphical user interface in this way. In my computer I was not able to get a console to log in. Instead of, I am changing thesystemd target
. That command stops all the GUI without restarting the computer.
– Jaime
May 7 '18 at 13:29
add a comment |
To stop:
sudo telinit 3
To start:
sudo telinit 5
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%2f979463%2fhow-to-turn-off-ubuntu-17-10s-gui-gdm%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Instead of killing the gdm
, you can change the systemd target.
Changing the systemd target
As mentioned here, starting from 16.04, Ubuntu uses systemd
and the boot process relies on a set of targets
. Each target
defines the system software that Ubuntu must run.
This is a list of targets
for Ubuntu:
┌───────────────────┐
│ Target │
├───────────────────┤
│ poweroff.target │ turn off the computer
├───────────────────┤
│ rescue.target │ minimal for admin/rescue tasks
├───────────────────┤
│ multi-user.target │ multi-user, no GUI
├───────────────────┤
│ graphical.target │ multi-user, GUI
├───────────────────┤
│ reboot.target │ reboot the computer
└───────────────────┘
To stop the GUI, you can change the target
. The system checks all the running system software and kills those not included in the specified target. In consequence, if you change to the multi-user.target
target, the GUI will be killed.
To change the "target" and kill the GUI:
sudo systemctl isolate multi-user.target
To make this the default "target" (and start booting your computer without GUI), you can use:
sudo systemctl enable multi-user.target
sudo systemctl set-default multi-user.target
add a comment |
Instead of killing the gdm
, you can change the systemd target.
Changing the systemd target
As mentioned here, starting from 16.04, Ubuntu uses systemd
and the boot process relies on a set of targets
. Each target
defines the system software that Ubuntu must run.
This is a list of targets
for Ubuntu:
┌───────────────────┐
│ Target │
├───────────────────┤
│ poweroff.target │ turn off the computer
├───────────────────┤
│ rescue.target │ minimal for admin/rescue tasks
├───────────────────┤
│ multi-user.target │ multi-user, no GUI
├───────────────────┤
│ graphical.target │ multi-user, GUI
├───────────────────┤
│ reboot.target │ reboot the computer
└───────────────────┘
To stop the GUI, you can change the target
. The system checks all the running system software and kills those not included in the specified target. In consequence, if you change to the multi-user.target
target, the GUI will be killed.
To change the "target" and kill the GUI:
sudo systemctl isolate multi-user.target
To make this the default "target" (and start booting your computer without GUI), you can use:
sudo systemctl enable multi-user.target
sudo systemctl set-default multi-user.target
add a comment |
Instead of killing the gdm
, you can change the systemd target.
Changing the systemd target
As mentioned here, starting from 16.04, Ubuntu uses systemd
and the boot process relies on a set of targets
. Each target
defines the system software that Ubuntu must run.
This is a list of targets
for Ubuntu:
┌───────────────────┐
│ Target │
├───────────────────┤
│ poweroff.target │ turn off the computer
├───────────────────┤
│ rescue.target │ minimal for admin/rescue tasks
├───────────────────┤
│ multi-user.target │ multi-user, no GUI
├───────────────────┤
│ graphical.target │ multi-user, GUI
├───────────────────┤
│ reboot.target │ reboot the computer
└───────────────────┘
To stop the GUI, you can change the target
. The system checks all the running system software and kills those not included in the specified target. In consequence, if you change to the multi-user.target
target, the GUI will be killed.
To change the "target" and kill the GUI:
sudo systemctl isolate multi-user.target
To make this the default "target" (and start booting your computer without GUI), you can use:
sudo systemctl enable multi-user.target
sudo systemctl set-default multi-user.target
Instead of killing the gdm
, you can change the systemd target.
Changing the systemd target
As mentioned here, starting from 16.04, Ubuntu uses systemd
and the boot process relies on a set of targets
. Each target
defines the system software that Ubuntu must run.
This is a list of targets
for Ubuntu:
┌───────────────────┐
│ Target │
├───────────────────┤
│ poweroff.target │ turn off the computer
├───────────────────┤
│ rescue.target │ minimal for admin/rescue tasks
├───────────────────┤
│ multi-user.target │ multi-user, no GUI
├───────────────────┤
│ graphical.target │ multi-user, GUI
├───────────────────┤
│ reboot.target │ reboot the computer
└───────────────────┘
To stop the GUI, you can change the target
. The system checks all the running system software and kills those not included in the specified target. In consequence, if you change to the multi-user.target
target, the GUI will be killed.
To change the "target" and kill the GUI:
sudo systemctl isolate multi-user.target
To make this the default "target" (and start booting your computer without GUI), you can use:
sudo systemctl enable multi-user.target
sudo systemctl set-default multi-user.target
edited yesterday
Madacol
234
234
answered May 7 '18 at 13:42
JaimeJaime
784310
784310
add a comment |
add a comment |
To stop it:
sudo systemctl gdm stop
To disable it completely:
sudo systemctl gdm disable
To start it:
sudo systemctl gdm start
and to re-enable it:
sudo systemctl gdm enable
To see the actually running services
systemctl --state running
I had problems after stoping the graphical user interface in this way. In my computer I was not able to get a console to log in. Instead of, I am changing thesystemd target
. That command stops all the GUI without restarting the computer.
– Jaime
May 7 '18 at 13:29
add a comment |
To stop it:
sudo systemctl gdm stop
To disable it completely:
sudo systemctl gdm disable
To start it:
sudo systemctl gdm start
and to re-enable it:
sudo systemctl gdm enable
To see the actually running services
systemctl --state running
I had problems after stoping the graphical user interface in this way. In my computer I was not able to get a console to log in. Instead of, I am changing thesystemd target
. That command stops all the GUI without restarting the computer.
– Jaime
May 7 '18 at 13:29
add a comment |
To stop it:
sudo systemctl gdm stop
To disable it completely:
sudo systemctl gdm disable
To start it:
sudo systemctl gdm start
and to re-enable it:
sudo systemctl gdm enable
To see the actually running services
systemctl --state running
To stop it:
sudo systemctl gdm stop
To disable it completely:
sudo systemctl gdm disable
To start it:
sudo systemctl gdm start
and to re-enable it:
sudo systemctl gdm enable
To see the actually running services
systemctl --state running
answered Nov 23 '17 at 11:22
VideonauthVideonauth
24.2k1271100
24.2k1271100
I had problems after stoping the graphical user interface in this way. In my computer I was not able to get a console to log in. Instead of, I am changing thesystemd target
. That command stops all the GUI without restarting the computer.
– Jaime
May 7 '18 at 13:29
add a comment |
I had problems after stoping the graphical user interface in this way. In my computer I was not able to get a console to log in. Instead of, I am changing thesystemd target
. That command stops all the GUI without restarting the computer.
– Jaime
May 7 '18 at 13:29
I had problems after stoping the graphical user interface in this way. In my computer I was not able to get a console to log in. Instead of, I am changing the
systemd target
. That command stops all the GUI without restarting the computer.– Jaime
May 7 '18 at 13:29
I had problems after stoping the graphical user interface in this way. In my computer I was not able to get a console to log in. Instead of, I am changing the
systemd target
. That command stops all the GUI without restarting the computer.– Jaime
May 7 '18 at 13:29
add a comment |
To stop:
sudo telinit 3
To start:
sudo telinit 5
add a comment |
To stop:
sudo telinit 3
To start:
sudo telinit 5
add a comment |
To stop:
sudo telinit 3
To start:
sudo telinit 5
To stop:
sudo telinit 3
To start:
sudo telinit 5
answered May 26 '18 at 21:36
aksungurluaksungurlu
111
111
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%2f979463%2fhow-to-turn-off-ubuntu-17-10s-gui-gdm%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
There is an error in the command you are using: You must use
sudo service gdm stop
(stop gdm
is a mistake)– Jaime
May 7 '18 at 13:17