Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509369
Title:
gdm ru
After using workaround from coomment #4 now gdm starts two X session on
vt7 and vt8 :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509369
Title:
gdm runs in vt7 and gnome-shell in vt2 after resu
On Wed, 02 Dec 2015 09:46:49 -
David Girault <1509...@bugs.launchpad.net> 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
First, thanks for your detailled comment.
Now, did you found any way to force gdm to only use vt > 7 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1509369
Title:
gdm runs in vt7 and gnome-shell in
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 sy
