<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"> <html><head><meta name="qrichtext" content="1" /><style type="text/css"> p, li { white-space: pre-wrap; } </style></head><body style=" font-family:'DejaVu Sans Mono'; font-size:9pt; font-weight:400; font-style:normal;"> Hi. As far as I know, X apps always had the ability to reconnect, its just that none ever did. I don't know why, maybe piximaps or windows states/ID's where lost or something... Or the idea never caught on. X apps don't crash when they lose connection to the x server, its just that they all (most) perform a safe exit action (you can see it in the terminal) and then close, instead of looking for a new display. I don't know if its possible or not, but seeing that its client server, I don't see why it would not be. I have a feeling that Wayland clients would be able to reconnect, but don't take it from me. But I agree that this is importiant, If Wayland was to segfault, or if the user needs to switch to a new instance of the Wayland server, (because of a new version, wanted to switch to a compositor with a different WM style, or wanted to leave the desktop session, and remote into the session) it should be supported early. PS I don't know about the last example. It was stated earlier that a custom version of Wayland could be made to support remote/remote rootless sessions. It would be a great feature If session could be made remote/local on the fly.</body></html>