Hi. It will appear that when using the fbdev-backend backend, that I can't just pass --tty=2 to use tty2 when I call weston directly as root. I have to call weston directly as root in my loginmanager. And I can't use weston-launch because it nukes the custom XDG_RUNTIME_DIR I am using for it. If I just pass weston --tty=2 --backend=fbdev-backend.so, it starts hijacking all the ttys, if I switch to a text tty, and move the mouse, it starts drawing over it. I noticed that when I called weston like this, it does not seem to operate under a tty when I check the process under ps As a workaround, I now call it open with openvt -c $TTY -- weston --tty=$tty . When I do this, it works correctly, and when I look at the process under ps, it is running on the tty So it appears that if the fbdev-backend backed weston is not confined to a tty, it tries to take over everything. I hope I'm clear enough in my wording.
Now I am not so sure if the fbdev-backend.so backend is at fault with the TTY. After further diagnosis of having this same issue after my workaround later on, I later discovered that I accidentally duplicated my init script for my loginmanager, and I was running two instances of the thing, which was causing me lots of problems, including colliding on TTYs.
Shouldn't you use --tty=/dev/tty2 instead of just --tty=2 or --tty=tty2. That is how I had to use it not so long ago...(that wasn't with fbdev-backend though)
This probably can be closed Because of a scripting error, I was ending up with two instances of my script, which was causing TWO instances of my script running, and calling weston on the same TTY, which was causing the conflict. (I think even pretty much at the same time) When I found out what was giving me two instances, and brought it down to one, I am not getting these wierd TTY issues and --tty=2 is for weston itself while weston-launch takes --tty=/dev/tty2 I think
Reporter identified the problem as starting weston twice on the same tty.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.