On 2014-05-05 12:34 (GMT+0200) Lennart Poettering composed:
Felix Miata wrote:
How can I get it to go there and stay there? When starting F21 in
multi-user, logging in on tty3 and running startx, KDE shows up on
tty3, where, as it's currently broken[1], it needs to be killed to
escape it. Ctrl-Alt-BS fails to kill it (in spite of xorg.con*
entries intended that Ctrl-Alt-BS be enabled for that purpose), and
switching to tty3 is unavailable to use Ctrl-C to kill it as can be
done when started from tty3 but running on tty7. The only way out is
logging in somewhere else, or CAD. This shouldn't be.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1092852
To get the device permissions right startx can only "upgrade" a text
session to a graphical one,
There is a relatively recent change, as it used to be that the first X instance would
always start on tty7 no matter how started. I still have a DM running there if in
graphical target.
What is this permissions business? IOW, what search terms would lead me to an
explanation of the changes, or at least a non-simplistic but not overly detailed why
they occurred?
it cannot open a new VT.
Why?
Hence if you want X
to show up on session N, then you need to start it from ttyN... Note
that only tty1-6 get logins by default, but you can configure that with
NAutoVTs= in /etc/systemd/logind.conf.
That sounds like a method that will prevent a DM from running on the same tty as
startx would as a first and only X session, as if that hasn't already happened. OT,
reading that man page, is setting it 0 how to revert from auto spawning to keeping
gettys running on all of tty1-6 as before systemd existed?
On the F21 system booted ATM:
systemd-212-2.rc21
xorg.x11.server.Xorg-1.15.99.902-5...fc21
xorg.x11.xauth-1.0.7-4.fc20
Booting graphical.target the DM is on tty7. Booting multi-user.target, logging in on
tty3, and from tty3 switching to graphical.target (init 5) also puts the DM on tty7.
Startx from tty3 puts X session on tty3 regardless whether DM is running. Why can't
startx do whatever systemd did to get X going on tty7? Is there a replacement or
substitute for startx that can? Ctrl-Alt-BS fails to kill the startx session. Ctcl-C
is unavailable to kill the startx session from bash on tty3 because it's blocked by
the broken X session.
Same machine booted to openSUSE Factory (target release November):
systemd-210-6.1
xorg.x11.server-7.6_1.15.99.902.2-312.11
xauth-1.0.8-11.1
Booting graphical.target the DM is on tty7. Booting multi-user.target, logging in on
tty3, and from tty3 switching to graphical.target (init 5) also puts the DM on tty7.
Startx -- :1 from tty3 with DM running puts X session on tty8 (same as happened in
Fedora 5 years ago). Ctrl-Alt-BS succeeds to kill the X session. Ctrl-C on tty3 also
will kill the X session started from it. All is same with DM not running (in
multi-user.target) with simple startx, except the startx session is on tty7. Where X
sessions land is nicely same as in e.g. F7 & F14.
I might not even care about the location of X sessions if only it wasn't so
complicated to kill a broken one. Why doesn't Ctrl-Alt-BS not work any more?
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
