So, instead of having my X session always run on a specific virtual terminal, the X session will run only on the virtual terminal from which it is started. It seems that, basically, the virtual terminal to which X is attached can no longer be specified. Certainly, "someone", perhaps Hans de Goede, at, or perhaps one of the Arch maintainers, should describe, in very basic and complete terms, what, exactly, is "the plan" for this new X server configuration format. My immediate reaction would be that "this is totally unacceptable", but I suppose I could learn to live with it. Hmm - this is very different behavior, for the X server. When starting from the first virtual terminal, and that the environment variable "XDG_VTNR" is getting set uniquely at each virtual terminal, to match each virtual terminal number. usr/bin/Xorg.bin -nolisten tcp :0 -auth /tmp/serverauth.3Zr4iN05qW vt1 I had had a custom ".xserverrc", starting Xorg on a different VT.īut, as you say, "starting X on a different TTY than where the login happened, which is broken." On the other hand, Weston and Xwayland seem to work fine - thankfully - though Weston is a bit fragile still.Īha! Yes, thanks, that worked. The log files do not seem to be informative. (EE) Screen(s) found, but none have a usable configuration. (EE) RADEON(0): Kernel modesetting setup failed (EE) RADEON(0): failed to set drm interface version. Running "Xorg.wrap" or "Xorg.bin" as root: Of course, "/dev/tty0" _does_ exist, with:Ĭrw-w- 1 root tty 4, 0 Jul 19 08:39 /dev/tty0 (EE) xf86OpenConsole: Cannot open /dev/tty0 (No such file or directory) Running "Xorg.wrap" or "Xorg.bin" as a non-root user: setversion 1.4 failed: Permission denied Running "startx" for "startkde" ends with: I don't remember having any trouble with the development server from the AUR. I can't seem to get the Xorg server to run at all, on a Radeon, with any permissions.
0 kommentar(er)
