Survive Xwayland crashes
If the Xwayland process crashes, it will bring down the entire session together with itself. Obviously, we don't want that. At least, Wayland clients should survive the crash. This change refactors relevant X11 parts to handle Xwayland crashes in a less fatal way. In order to handle Xwayland crashes better, a pair of start() and stop() methods had been introduced in the Xwayland class to allow starting and stopping the Xwayland process at any moment. If we detect that the Xwayland process has crashed, we will immediately stop the Xwayland server, which in its turn will deactivate the socket notifier and destroy all connected X11 clients. Unfortunately, a couple of subtle changes in X11Client::releaseWindow() and Unmanaged::release() had to be made to ensure that we are left with a valid state after the Xwayland server has been stopped.
parent
fff2bfe7
-
Hi, if I add this change and then sudo Killall Xwayland, will it also log out automatically? What is the specific performance? Is it still in normal use? It seems that the crash caused by killing Xwayland is different on different machines? There is more than one way for autologout to crash. This is my email: w2524180509@163.com. Looking forward to your reply.
Edited by chengyu wang
Please register or sign in to comment