No, I took a quick look through the X server git log too, but nothing jumped out. You'd have to walk through the VT switch and startup code paths to see where the fix may have been committed. Or if it's easy to reproduce on the system you could try bisecting through the X server commits for the fix; it might be a pain due to dependencies though... Anyway I'll mark fixed since it sounds like upstream is ok here.
No, I took a quick look through the X server git log too, but nothing jumped out. You'd have to walk through the VT switch and startup code paths to see where the fix may have been committed. Or if it's easy to reproduce on the system you could try bisecting through the X server commits for the fix; it might be a pain due to dependencies though... Anyway I'll mark fixed since it sounds like upstream is ok here.