Why does GDM run on TTY1 and gnome-shell on TTY2? [duplicate]











up vote
5
down vote

favorite













This question already has an answer here:




  • Why is my GDM at a different TTY than my desktop environment?

    1 answer




I am running Ubuntu Gnome 16.10 with gnome-shell 3.20.4.

I usually see my graphic interface run on TTY7. But now (new install) I see GDM run on TTY1 and my graphic interface on TTY2. Why GDM and gnome-shell are separate? And why it's run graphic interface on TTY2 and not in TTY7. It is a wrong configuration or it is totally normal to see this ?



On my TTY7 I can see : /dev/sda4/ clean: xxx/xxx files, xxx/xxx blocks










share|improve this question















marked as duplicate by muru, Videonauth, dessert, karel, pomsky Nov 24 '17 at 13:29


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.















  • I have the same problem running unstable Debian after recent upgrade. I am running gnome-shell 3.22.2-1 and gdm 3.22.1-1.
    – thegeko
    Dec 31 '16 at 1:18










  • If you see the date of the post, my question is older than yours...
    – Zagonine
    Oct 16 '17 at 15:52















up vote
5
down vote

favorite













This question already has an answer here:




  • Why is my GDM at a different TTY than my desktop environment?

    1 answer




I am running Ubuntu Gnome 16.10 with gnome-shell 3.20.4.

I usually see my graphic interface run on TTY7. But now (new install) I see GDM run on TTY1 and my graphic interface on TTY2. Why GDM and gnome-shell are separate? And why it's run graphic interface on TTY2 and not in TTY7. It is a wrong configuration or it is totally normal to see this ?



On my TTY7 I can see : /dev/sda4/ clean: xxx/xxx files, xxx/xxx blocks










share|improve this question















marked as duplicate by muru, Videonauth, dessert, karel, pomsky Nov 24 '17 at 13:29


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.















  • I have the same problem running unstable Debian after recent upgrade. I am running gnome-shell 3.22.2-1 and gdm 3.22.1-1.
    – thegeko
    Dec 31 '16 at 1:18










  • If you see the date of the post, my question is older than yours...
    – Zagonine
    Oct 16 '17 at 15:52













up vote
5
down vote

favorite









up vote
5
down vote

favorite












This question already has an answer here:




  • Why is my GDM at a different TTY than my desktop environment?

    1 answer




I am running Ubuntu Gnome 16.10 with gnome-shell 3.20.4.

I usually see my graphic interface run on TTY7. But now (new install) I see GDM run on TTY1 and my graphic interface on TTY2. Why GDM and gnome-shell are separate? And why it's run graphic interface on TTY2 and not in TTY7. It is a wrong configuration or it is totally normal to see this ?



On my TTY7 I can see : /dev/sda4/ clean: xxx/xxx files, xxx/xxx blocks










share|improve this question
















This question already has an answer here:




  • Why is my GDM at a different TTY than my desktop environment?

    1 answer




I am running Ubuntu Gnome 16.10 with gnome-shell 3.20.4.

I usually see my graphic interface run on TTY7. But now (new install) I see GDM run on TTY1 and my graphic interface on TTY2. Why GDM and gnome-shell are separate? And why it's run graphic interface on TTY2 and not in TTY7. It is a wrong configuration or it is totally normal to see this ?



On my TTY7 I can see : /dev/sda4/ clean: xxx/xxx files, xxx/xxx blocks





This question already has an answer here:




  • Why is my GDM at a different TTY than my desktop environment?

    1 answer








tty gdm






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 4 '16 at 16:51

























asked Dec 4 '16 at 16:44









Zagonine

1438




1438




marked as duplicate by muru, Videonauth, dessert, karel, pomsky Nov 24 '17 at 13:29


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.






marked as duplicate by muru, Videonauth, dessert, karel, pomsky Nov 24 '17 at 13:29


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.














  • I have the same problem running unstable Debian after recent upgrade. I am running gnome-shell 3.22.2-1 and gdm 3.22.1-1.
    – thegeko
    Dec 31 '16 at 1:18










  • If you see the date of the post, my question is older than yours...
    – Zagonine
    Oct 16 '17 at 15:52


















  • I have the same problem running unstable Debian after recent upgrade. I am running gnome-shell 3.22.2-1 and gdm 3.22.1-1.
    – thegeko
    Dec 31 '16 at 1:18










  • If you see the date of the post, my question is older than yours...
    – Zagonine
    Oct 16 '17 at 15:52
















I have the same problem running unstable Debian after recent upgrade. I am running gnome-shell 3.22.2-1 and gdm 3.22.1-1.
– thegeko
Dec 31 '16 at 1:18




I have the same problem running unstable Debian after recent upgrade. I am running gnome-shell 3.22.2-1 and gdm 3.22.1-1.
– thegeko
Dec 31 '16 at 1:18












If you see the date of the post, my question is older than yours...
– Zagonine
Oct 16 '17 at 15:52




If you see the date of the post, my question is older than yours...
– Zagonine
Oct 16 '17 at 15:52










1 Answer
1






active

oldest

votes

















up vote
2
down vote













I found an explanation on Gnome's Bugzilla, see below. Hopefully they will address the increased memory consumption by tearing down the greeter after user login.




GDM's behavior was changed in 3.16 so that instead of running one X server on the login screen which is then transformed into the user's session, we now start a new X session from within the user's session, which means that we need to start the user's session on another TTY/VT.



Note that when using fast user switching, you effectively got this behavior as well, with each user on a different TTY/VT. We just extended it to the first user to log in as well.







share|improve this answer




























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    2
    down vote













    I found an explanation on Gnome's Bugzilla, see below. Hopefully they will address the increased memory consumption by tearing down the greeter after user login.




    GDM's behavior was changed in 3.16 so that instead of running one X server on the login screen which is then transformed into the user's session, we now start a new X session from within the user's session, which means that we need to start the user's session on another TTY/VT.



    Note that when using fast user switching, you effectively got this behavior as well, with each user on a different TTY/VT. We just extended it to the first user to log in as well.







    share|improve this answer

























      up vote
      2
      down vote













      I found an explanation on Gnome's Bugzilla, see below. Hopefully they will address the increased memory consumption by tearing down the greeter after user login.




      GDM's behavior was changed in 3.16 so that instead of running one X server on the login screen which is then transformed into the user's session, we now start a new X session from within the user's session, which means that we need to start the user's session on another TTY/VT.



      Note that when using fast user switching, you effectively got this behavior as well, with each user on a different TTY/VT. We just extended it to the first user to log in as well.







      share|improve this answer























        up vote
        2
        down vote










        up vote
        2
        down vote









        I found an explanation on Gnome's Bugzilla, see below. Hopefully they will address the increased memory consumption by tearing down the greeter after user login.




        GDM's behavior was changed in 3.16 so that instead of running one X server on the login screen which is then transformed into the user's session, we now start a new X session from within the user's session, which means that we need to start the user's session on another TTY/VT.



        Note that when using fast user switching, you effectively got this behavior as well, with each user on a different TTY/VT. We just extended it to the first user to log in as well.







        share|improve this answer












        I found an explanation on Gnome's Bugzilla, see below. Hopefully they will address the increased memory consumption by tearing down the greeter after user login.




        GDM's behavior was changed in 3.16 so that instead of running one X server on the login screen which is then transformed into the user's session, we now start a new X session from within the user's session, which means that we need to start the user's session on another TTY/VT.



        Note that when using fast user switching, you effectively got this behavior as well, with each user on a different TTY/VT. We just extended it to the first user to log in as well.








        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Dec 31 '16 at 1:43









        thegeko

        20414




        20414















            Popular posts from this blog

            Ellipse (mathématiques)

            Quarter-circle Tiles

            Mont Emei