I typically start a server with "--test-client <whatever>" and that seems to be what provokes the problem I see. If I start the server, then VT switch to start a client everything works. (Even if I switch a monitor off or on - so I can't confirm the above test case.)
This is with both trunk and 0.14 - so I agree in suspecting a change to kernel behaviour. While "carry on" seems plausible I think we ought to report that a problem occurred and not just ignore it.
No problems on vivid with either scenario or codebase.
A bit more information:
I typically start a server with "--test-client <whatever>" and that seems to be what provokes the problem I see. If I start the server, then VT switch to start a client everything works. (Even if I switch a monitor off or on - so I can't confirm the above test case.)
This is with both trunk and 0.14 - so I agree in suspecting a change to kernel behaviour. While "carry on" seems plausible I think we ought to report that a problem occurred and not just ignore it.
No problems on vivid with either scenario or codebase.