gdm runs in vt7 and gnome-shell in vt2 after resuming

After some research, I think this is not strictly related to suspend/resume and more to how gdm selects the next VT available to spawn your session and how systemd manages VTs initialization (getty on demand). From http://0pointer.de/blog/projects/serial-console.html

"""
Traditionally, the init system on Linux machines was configured to spawn a fixed number login prompts at boot.[...]

In a systemd world we made this more dynamic: in order to make things more efficient login prompts are now started on demand only. As you switch to the VTs the getty service is instantiated to <email address hidden>, <email address hidden> and so on.
"""

I rebooted my machine and before logging in I cycled from VT1 until VT7(gdm), so systemd launched a getty in each VT, then I logged in gdm and gnome-shell was launched in VT8 and this problem went away.

So this is what I think is happening:

- the system boots
- a getty in launched in VT1 and gdm in VT7
- the user logs in
- gdm looks for the next available VT, as systemd didn't launch VT2...VT6, gdm uses VT2 and from that point Alt+<arrow> behave like if you were running virtual terminal console instead of an X session.

First, thanks for your detailled comment.
Now, did you found any way to force gdm to only use vt > 7 ?

On Wed, 02 Dec 2015 09:46:49 -0000
David Girault <email address hidden> wrote:

> First, thanks for your detailled comment.
> Now, did you found any way to force gdm to only use vt > 7 ?
>

No, I didn't. The workaround I found was to force the initialization
vt{2..6}, in a systemd world this is achieved running:

$ cd /etc/systemd/system/getty.target.wants/
$ for i in {2..6}; do sudo ln -s /lib/systemd/system/getty@.service getty@tty${i}.service;done
$ ls /etc/systemd/system/getty.target.wants/ -l
total 0
lrwxrwxrwx 1 root root 34 Oct 19 16:40 <email address hidden> -> /lib/systemd/system/getty@.service
lrwxrwxrwx 1 root root 34 Oct 27 17:53 <email address hidden> -> /lib/systemd/system/getty@.service
lrwxrwxrwx 1 root root 34 Oct 27 17:53 <email address hidden> -> /lib/systemd/system/getty@.service
lrwxrwxrwx 1 root root 34 Oct 27 17:53 <email address hidden> -> /lib/systemd/system/getty@.service
lrwxrwxrwx 1 root root 34 Oct 27 17:53 <email address hidden> -> /lib/systemd/system/getty@.service
lrwxrwxrwx 1 root root 34 Oct 27 17:53 <email address hidden> -> /lib/systemd/system/getty@.service

This made my problem go away, considering that VTs have a really small
footprint maybe is a good way to make this a default.

After using workaround from coomment #4 now gdm starts two X session on vt7 and vt8 :-)

Status changed to 'Confirmed' because the bug affects multiple users.