When I have first 16 tty's used, XFree (x11-base/xorg-x11-6.7.0-r2) choose tty16, hapilly start, but keyboard's not working, because all keys get that getty already running on tty16. Reproducible: Always Steps to Reproduce: 1. Start 15 getty and one X 2. Start another X Actual Results: In new X, keyboard is not working, including CTRL-ALT-F1 and CTRL-ALT-BACKSPACE, because X uses tty16 Expected Results: X should take next free tty - tty17 or in my case tty40 - and work normally including keyboard Problem is in 0350_all_4.2.0-vt7.patch, which is clearly broken. It switch from using VT_OPENQRY, which work perfectly, to using VT_GETSTATE and searching for free console representet as unset bit in vt_stat.v_active. Definition of vt_stat in linux/vt.h: struct vt_stat { unsigned short v_active; /* active vt */ unsigned short v_signal; /* signal to send */ unsigned short v_state; /* vt bitmask */ }; unsigned short means 16 bites, 0350_all_4.2.0-vt7.patch assumes 64. So, it is clearly wrong. I also don't know why is needed in first place, but searching only 16 tty as in 0350_all_4.2.0-vt7.patch and fallback to VT_OPENQRY should have advantages of both versions.
I'd appreciate if you'd attach a fixed version of that patch, or a patch to it.
Created attachment 42168 [details, diff] Solution by merging methods. Not tested. I still don't know what problem was solved by first patch (and why simple removing of that patch isn't solution). I didn't tested this patch. I didn't even test if it compile. I will report after I test it, but I assume you can test it faster and better.
OK, it will at least compile.
OK, tested. Fallback works.
This bug is still present in xorg-x11-6.8.0-r4. And BTW, ald is still missing in portage. Should someone remind me what point have filling bugreports ? It's over 4 month, 4 gentoo and one upstream version old !
I've removed this patch altogether in 6.8.99.x in April, because I was unable to justify it after searching extensively. Thanks for filing, and sorry for the delay.
Just note: xorg-x11-6.8.2-r6 still have that broken patch and 6.8.99.x (6.8.99.15-r4) is still ~x86 and ~amd64. I hope 6.8.99 will make it in stable as soon as possible, but still ... can you do something in 6.8.2-r7, if that version appear ?
7.0 will be the next X to go stable; 6.8.2 will not receive any further changes that aren't fixing security holes.
Just note: xorg-x11-6.8.2-r7 is out and bug is still there. I hope 7.0 will be soon ...
(In reply to comment #9) > Just note: xorg-x11-6.8.2-r7 is out and bug is still there. I hope 7.0 will be > soon ... Will be soon what? 7.1 has been in ~arch for a while already.
