OK, I just upgraded another machine from gdm 2.20 to 2.26, and can confirm that for that upgrade, the new gdm is erroneously started on vt8 / X screen :1 whilst the previous session remains happily alive on vt7 / :0.
I am attaching apt-term.log from that upgrade - in particular I find it suspicious that there is first an attempt to reload gdm, which fails, followed by an attempt to start gdm afresh, with is presumably responsible for the extra spurious gdm. ** Attachment added: "apt-term.log" http://launchpadlibrarian.net/28685927/apt-term.log -- gdm 2.26 kills or switches away from active X sessions on upgrading https://bugs.launchpad.net/bugs/395313 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
