[Bug 429616] Re: x display manager won't open session on next free vt
seems like the main culprit is really usplash it tinkers with ttys in initramfs scripts. ** Package changed: gdm (Ubuntu) => usplash (Ubuntu) -- x display manager won't open session on next free vt https://bugs.launchpad.net/bugs/429616 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 429616] Re: x display manager won't open session on next free vt
no idea about what to look but you can try to contact the ubuntu-devel about technical questions -- x display manager won't open session on next free vt https://bugs.launchpad.net/bugs/429616 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 429616] Re: x display manager won't open session on next free vt
fair enough, at least for the 4th line (the other 3 i could try to challenge). would you anyway be able to hint which file i could look into, haven t find anything in /etc/init.d (only some references to fgconsole check in usplash) ? -- x display manager won't open session on next free vt https://bugs.launchpad.net/bugs/429616 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 429616] Re: x display manager won't open session on next free vt
the documentation for ubuntu bug triaging describe "Low: Bugs which affect functionality, but to a lesser extent than most bugs, examples are: * Ones that can be easily worked around * Ones that affect unusual configurations or uncommon hardware * A bug that has a moderate impact on a non-core application * A cosmetic/usability issue that does not limit the functionality of an application " the settings seem adapted there, normal users don't know what at vt is and will not never switch to a specific one but use the ui user switching features rather -- x display manager won't open session on next free vt https://bugs.launchpad.net/bugs/429616 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 429616] Re: x display manager won't open session on next free vt
Just a comment, the startx "discovery" meant that vt8 was not actually locked by usplash as I had thought since Gutsy, -- x display manager won't open session on next free vt https://bugs.launchpad.net/bugs/429616 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 429616] Re: x display manager won't open session on next free vt
Sebastien I beg to differ. Though sure this is not a critical bug, it certainly is one since it's well documented that new vts should be created sequentially, vt7, vt8, etc... Also before I came to the startx "discovery" I've found quite a few complaints, some very old dating from hardy or 2005 (like this https://lists.ubuntu.com/archives/ubuntu- users/2005-November/056772.html) from a standard user). I'm sure many people quit complaining as they assume that vt8 anyway is allocated to usplash and have not been told you can redirect it. I can say myself this is a regression as it worked ok in Feisty/Gutsy. More importand yet, there are a number of indirect bugs probably related to this, like bug #172444 running since Gutsy Also please note that the behaviour occurs inside gdm but also from pure startx command. For the time being I've modified gdm to start at vt9. Startx then launches at vt7 and a second startx session launches at vt...10. Could you maybe give a hint of which file I should hack to get startx behaving as specified or is it hardcoded ? Bottom line, I would ask you to raise to medium so that I can see it fixed one day. It doesn't seem too hard to fix and the benefits may be greater than it appears. -- x display manager won't open session on next free vt https://bugs.launchpad.net/bugs/429616 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 429616] Re: x display manager won't open session on next free vt
not sure that's really a bug, not something likely to affect user experience in any way and low importance ** Changed in: gdm (Ubuntu) Importance: Undecided => Low -- x display manager won't open session on next free vt https://bugs.launchpad.net/bugs/429616 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 429616] Re: x display manager won't open session on next free vt
seems like gdm is rather managing this ** Package changed: xdm (Ubuntu) => gdm (Ubuntu) -- x display manager won't open session on next free vt https://bugs.launchpad.net/bugs/429616 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 429616] Re: x display manager won't open session on next free vt
** Description changed: Binary package hint: xdm Since Ibex, opening a new session will create it on vt9, even if vt8 has been released from usplash activities at kernel boot by console=ttyX, unless vt8 is specifically forced (through startx) So somehow the dm seems just to assume that vt8 is permanently assigned to usplash or the info is not reset somewhere. Bug reproduction: - Boot 9.04 by adding, say, console=tty4 to the kernel boot line to redirect usplash screen messages from vt8 to vt4 - Log in new console session on tty1 - "startx -- :1 vt8" will create new graphical session on vt8 - but "startx -- :1" will create new graphical session on vt9 by "default" - This default behaviour of course happens at "New Session" from inside - the graphical session. + This default behaviour of course also happens at "New Session" from + inside the graphical session, but there you have no option to force vt8. + + The bug is however related to usplash since this does not occur if + usplash is disabled. Guess is usplash sets some info that vt8 is busy + even if console is redirected but xdm (?) does not check or resets the + info. -- x display manager won't open session on next free vt https://bugs.launchpad.net/bugs/429616 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 429616] Re: x display manager won't open session on next free vt
** Description changed: Binary package hint: xdm Since Ibex, opening a new session will create it on vt9, even if vt8 has been released from usplash activities at kernel boot by console=ttyX, unless vt8 is specifically forced (through startx) So somehow the dm seems just to assume that vt8 is permanently assigned to usplash or the info is not reset somewhere. Bug reproduction: - - Boot 9.04 normally + - Boot 9.04 by adding, say, console=tty4 to the kernel boot line to redirect usplash screen messages from vt8 to vt4 - Log in new console session on tty1 - "startx -- :1 vt8" will create new graphical session on vt8 - but "startx -- :1" will create new graphical session on vt9 by "default" This default behaviour of course happens at "New Session" from inside the graphical session. -- x display manager won't open session on next free vt https://bugs.launchpad.net/bugs/429616 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
