Enabling virtual consoles in Ubuntu 18.04












2















I have used the virtual consoles (tty1-6) for decades in various Linuxes. I recently installed Ubuntu 18.04 (Bionic Beaver) on an x86-64 box. Everything is fine, except that the VCs don't work. As far as I can tell, it is by design that people are now only supposed to use the GUI (like in Windows). I would like to be able to use the VCs.



Note:

I've noticed (from ps output) that a lot of the GUI processes are running on tty1, so I assume that the GUI gets launched from there).



What I've tried:





  1. Ctrl-Alt-F1 (or F2 or F3 or ...). Nothing happens. By "nothing happens", I mean, literally, nothing happens.
    Note:

    I am familiar with one system where you can switch to the virtual consoles (from the GUI), and it really does switch, but the screen stays on the GUI. You can now type and you are typing on the virtual console, but the screen makes it look like you are still on the GUI. I mention all this to say that, no, this is not the case here. You are still typing into the GUI.

  2. (as root) chvt 1. Nothing happens. Prompt comes right back and nothing has changed.

  3. (as root) chvt 2. Process hangs until you hit Ctrl/C. Weird...!


  4. (as root) strace chvt 2. Lots of strace output, ending with something like:



    ioctl(3,VT_WAITACTIVE ...)



and then it hangs (until you hit CTRL-C).

Next, following some advice I found on this board, I tried editing the file:



/etc/systemd/logind.conf


and uncommenting the first two active lines, which are:



NAutoVTs=6
ReserveVT=6


I tried first just uncommenting the first one, then rebooted, nothing changed.

So I then uncommented the second one as well, rebooted, again, no change.



So, what to do?

What is next?










share|improve this question

























  • Thank you, zx485, for editing my post. It looks much nicer now. I didn't know how to do any of those things.

    – Joe Schmoe
    Aug 30 '18 at 11:39











  • One more piece of information regarding this. I tried (as root): open sleep 1000 and then I can see (via ps) that sleep is indeed running on tty2. But, I still can't get to it...

    – Joe Schmoe
    Aug 30 '18 at 16:01








  • 1





    Ctrl+Alt+F1 does nothing on my Ubuntu 18.04.1 because the gnome session is running there. Other Ctrl+Alt+Fx shortcut work as expected (I see linux console). Previously, (Ubuntu 16.04) GUI part (Unity) used Ctrl + Alt + F7.

    – jfs
    Sep 16 '18 at 14:39











  • Are you sure those keys are mapped as Fx keys? Nowadays on laptops those usually are used to VolUp/Down, airplane mode, etc. You'll need to press the Fn (function but in other sense) key: Ctrp+Fn+Alt+F2.

    – Pablo Bianchi
    Jan 10 at 18:54
















2















I have used the virtual consoles (tty1-6) for decades in various Linuxes. I recently installed Ubuntu 18.04 (Bionic Beaver) on an x86-64 box. Everything is fine, except that the VCs don't work. As far as I can tell, it is by design that people are now only supposed to use the GUI (like in Windows). I would like to be able to use the VCs.



Note:

I've noticed (from ps output) that a lot of the GUI processes are running on tty1, so I assume that the GUI gets launched from there).



What I've tried:





  1. Ctrl-Alt-F1 (or F2 or F3 or ...). Nothing happens. By "nothing happens", I mean, literally, nothing happens.
    Note:

    I am familiar with one system where you can switch to the virtual consoles (from the GUI), and it really does switch, but the screen stays on the GUI. You can now type and you are typing on the virtual console, but the screen makes it look like you are still on the GUI. I mention all this to say that, no, this is not the case here. You are still typing into the GUI.

  2. (as root) chvt 1. Nothing happens. Prompt comes right back and nothing has changed.

  3. (as root) chvt 2. Process hangs until you hit Ctrl/C. Weird...!


  4. (as root) strace chvt 2. Lots of strace output, ending with something like:



    ioctl(3,VT_WAITACTIVE ...)



and then it hangs (until you hit CTRL-C).

Next, following some advice I found on this board, I tried editing the file:



/etc/systemd/logind.conf


and uncommenting the first two active lines, which are:



NAutoVTs=6
ReserveVT=6


I tried first just uncommenting the first one, then rebooted, nothing changed.

So I then uncommented the second one as well, rebooted, again, no change.



So, what to do?

What is next?










share|improve this question

























  • Thank you, zx485, for editing my post. It looks much nicer now. I didn't know how to do any of those things.

    – Joe Schmoe
    Aug 30 '18 at 11:39











  • One more piece of information regarding this. I tried (as root): open sleep 1000 and then I can see (via ps) that sleep is indeed running on tty2. But, I still can't get to it...

    – Joe Schmoe
    Aug 30 '18 at 16:01








  • 1





    Ctrl+Alt+F1 does nothing on my Ubuntu 18.04.1 because the gnome session is running there. Other Ctrl+Alt+Fx shortcut work as expected (I see linux console). Previously, (Ubuntu 16.04) GUI part (Unity) used Ctrl + Alt + F7.

    – jfs
    Sep 16 '18 at 14:39











  • Are you sure those keys are mapped as Fx keys? Nowadays on laptops those usually are used to VolUp/Down, airplane mode, etc. You'll need to press the Fn (function but in other sense) key: Ctrp+Fn+Alt+F2.

    – Pablo Bianchi
    Jan 10 at 18:54














2












2








2


1






I have used the virtual consoles (tty1-6) for decades in various Linuxes. I recently installed Ubuntu 18.04 (Bionic Beaver) on an x86-64 box. Everything is fine, except that the VCs don't work. As far as I can tell, it is by design that people are now only supposed to use the GUI (like in Windows). I would like to be able to use the VCs.



Note:

I've noticed (from ps output) that a lot of the GUI processes are running on tty1, so I assume that the GUI gets launched from there).



What I've tried:





  1. Ctrl-Alt-F1 (or F2 or F3 or ...). Nothing happens. By "nothing happens", I mean, literally, nothing happens.
    Note:

    I am familiar with one system where you can switch to the virtual consoles (from the GUI), and it really does switch, but the screen stays on the GUI. You can now type and you are typing on the virtual console, but the screen makes it look like you are still on the GUI. I mention all this to say that, no, this is not the case here. You are still typing into the GUI.

  2. (as root) chvt 1. Nothing happens. Prompt comes right back and nothing has changed.

  3. (as root) chvt 2. Process hangs until you hit Ctrl/C. Weird...!


  4. (as root) strace chvt 2. Lots of strace output, ending with something like:



    ioctl(3,VT_WAITACTIVE ...)



and then it hangs (until you hit CTRL-C).

Next, following some advice I found on this board, I tried editing the file:



/etc/systemd/logind.conf


and uncommenting the first two active lines, which are:



NAutoVTs=6
ReserveVT=6


I tried first just uncommenting the first one, then rebooted, nothing changed.

So I then uncommented the second one as well, rebooted, again, no change.



So, what to do?

What is next?










share|improve this question
















I have used the virtual consoles (tty1-6) for decades in various Linuxes. I recently installed Ubuntu 18.04 (Bionic Beaver) on an x86-64 box. Everything is fine, except that the VCs don't work. As far as I can tell, it is by design that people are now only supposed to use the GUI (like in Windows). I would like to be able to use the VCs.



Note:

I've noticed (from ps output) that a lot of the GUI processes are running on tty1, so I assume that the GUI gets launched from there).



What I've tried:





  1. Ctrl-Alt-F1 (or F2 or F3 or ...). Nothing happens. By "nothing happens", I mean, literally, nothing happens.
    Note:

    I am familiar with one system where you can switch to the virtual consoles (from the GUI), and it really does switch, but the screen stays on the GUI. You can now type and you are typing on the virtual console, but the screen makes it look like you are still on the GUI. I mention all this to say that, no, this is not the case here. You are still typing into the GUI.

  2. (as root) chvt 1. Nothing happens. Prompt comes right back and nothing has changed.

  3. (as root) chvt 2. Process hangs until you hit Ctrl/C. Weird...!


  4. (as root) strace chvt 2. Lots of strace output, ending with something like:



    ioctl(3,VT_WAITACTIVE ...)



and then it hangs (until you hit CTRL-C).

Next, following some advice I found on this board, I tried editing the file:



/etc/systemd/logind.conf


and uncommenting the first two active lines, which are:



NAutoVTs=6
ReserveVT=6


I tried first just uncommenting the first one, then rebooted, nothing changed.

So I then uncommented the second one as well, rebooted, again, no change.



So, what to do?

What is next?







virtual virtual-console






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 30 '18 at 0:23









zx485

1,45231114




1,45231114










asked Aug 29 '18 at 18:46









Joe SchmoeJoe Schmoe

111




111













  • Thank you, zx485, for editing my post. It looks much nicer now. I didn't know how to do any of those things.

    – Joe Schmoe
    Aug 30 '18 at 11:39











  • One more piece of information regarding this. I tried (as root): open sleep 1000 and then I can see (via ps) that sleep is indeed running on tty2. But, I still can't get to it...

    – Joe Schmoe
    Aug 30 '18 at 16:01








  • 1





    Ctrl+Alt+F1 does nothing on my Ubuntu 18.04.1 because the gnome session is running there. Other Ctrl+Alt+Fx shortcut work as expected (I see linux console). Previously, (Ubuntu 16.04) GUI part (Unity) used Ctrl + Alt + F7.

    – jfs
    Sep 16 '18 at 14:39











  • Are you sure those keys are mapped as Fx keys? Nowadays on laptops those usually are used to VolUp/Down, airplane mode, etc. You'll need to press the Fn (function but in other sense) key: Ctrp+Fn+Alt+F2.

    – Pablo Bianchi
    Jan 10 at 18:54



















  • Thank you, zx485, for editing my post. It looks much nicer now. I didn't know how to do any of those things.

    – Joe Schmoe
    Aug 30 '18 at 11:39











  • One more piece of information regarding this. I tried (as root): open sleep 1000 and then I can see (via ps) that sleep is indeed running on tty2. But, I still can't get to it...

    – Joe Schmoe
    Aug 30 '18 at 16:01








  • 1





    Ctrl+Alt+F1 does nothing on my Ubuntu 18.04.1 because the gnome session is running there. Other Ctrl+Alt+Fx shortcut work as expected (I see linux console). Previously, (Ubuntu 16.04) GUI part (Unity) used Ctrl + Alt + F7.

    – jfs
    Sep 16 '18 at 14:39











  • Are you sure those keys are mapped as Fx keys? Nowadays on laptops those usually are used to VolUp/Down, airplane mode, etc. You'll need to press the Fn (function but in other sense) key: Ctrp+Fn+Alt+F2.

    – Pablo Bianchi
    Jan 10 at 18:54

















Thank you, zx485, for editing my post. It looks much nicer now. I didn't know how to do any of those things.

– Joe Schmoe
Aug 30 '18 at 11:39





Thank you, zx485, for editing my post. It looks much nicer now. I didn't know how to do any of those things.

– Joe Schmoe
Aug 30 '18 at 11:39













One more piece of information regarding this. I tried (as root): open sleep 1000 and then I can see (via ps) that sleep is indeed running on tty2. But, I still can't get to it...

– Joe Schmoe
Aug 30 '18 at 16:01







One more piece of information regarding this. I tried (as root): open sleep 1000 and then I can see (via ps) that sleep is indeed running on tty2. But, I still can't get to it...

– Joe Schmoe
Aug 30 '18 at 16:01






1




1





Ctrl+Alt+F1 does nothing on my Ubuntu 18.04.1 because the gnome session is running there. Other Ctrl+Alt+Fx shortcut work as expected (I see linux console). Previously, (Ubuntu 16.04) GUI part (Unity) used Ctrl + Alt + F7.

– jfs
Sep 16 '18 at 14:39





Ctrl+Alt+F1 does nothing on my Ubuntu 18.04.1 because the gnome session is running there. Other Ctrl+Alt+Fx shortcut work as expected (I see linux console). Previously, (Ubuntu 16.04) GUI part (Unity) used Ctrl + Alt + F7.

– jfs
Sep 16 '18 at 14:39













Are you sure those keys are mapped as Fx keys? Nowadays on laptops those usually are used to VolUp/Down, airplane mode, etc. You'll need to press the Fn (function but in other sense) key: Ctrp+Fn+Alt+F2.

– Pablo Bianchi
Jan 10 at 18:54





Are you sure those keys are mapped as Fx keys? Nowadays on laptops those usually are used to VolUp/Down, airplane mode, etc. You'll need to press the Fn (function but in other sense) key: Ctrp+Fn+Alt+F2.

– Pablo Bianchi
Jan 10 at 18:54










0






active

oldest

votes











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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1070235%2fenabling-virtual-consoles-in-ubuntu-18-04%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1070235%2fenabling-virtual-consoles-in-ubuntu-18-04%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

How to change which sound is reproduced for terminal bell?

Can I use Tabulator js library in my java Spring + Thymeleaf project?

Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents