This hasn't been my experience with X – if anything falls over, I get kicked back to the greeter and all my applications get killed. Not to say that Wayland is necessarily any better, but X is not...
unlike X11, where a compositing window manager crash may leave you without window decorations but a simple kwin_x11 –replace from a terminal or SSH session will bring you back to full working order, a crash in a Wayland compositor will terminate your entire session.
This hasn't been my experience with X – if anything falls over, I get kicked back to the greeter and all my applications get killed. Not to say that Wayland is necessarily any better, but X is not perfect in this regard either.
This really depends on how your session starts, on Plasma in particular I've experienced these kwin crashes constantly, but the solution to me was openbox --replace rather than kwin. It seems like...
This really depends on how your session starts, on Plasma in particular I've experienced these kwin crashes constantly, but the solution to me was openbox --replace rather than kwin. It seems like your crashes went deeper than the composer, and your actual session considered terminated by the greeter. I think it all depends on what process is considered the root of the session, but in theory this point stands firmly - a composer crash doesn't kill x windows on a protocol level.
For me it was, in Plasma 4 time OpenBox worked much better than Kwin, I've just pocked a bit of fun at it. But yeah, that just shows the flexibility of X once again - you can replace the composer...
For me it was, in Plasma 4 time OpenBox worked much better than Kwin, I've just pocked a bit of fun at it. But yeah, that just shows the flexibility of X once again - you can replace the composer on the go and keep your workflow.
Those reading this may also be interested in this post that addresses some of the points raised in the article.
This hasn't been my experience with X – if anything falls over, I get kicked back to the greeter and all my applications get killed. Not to say that Wayland is necessarily any better, but X is not perfect in this regard either.
This really depends on how your session starts, on Plasma in particular I've experienced these kwin crashes constantly, but the solution to me was
openbox --replacerather than kwin. It seems like your crashes went deeper than the composer, and your actual session considered terminated by the greeter. I think it all depends on what process is considered the root of the session, but in theory this point stands firmly - a composer crash doesn't kill x windows on a protocol level.For me it was, in Plasma 4 time OpenBox worked much better than Kwin, I've just pocked a bit of fun at it. But yeah, that just shows the flexibility of X once again - you can replace the composer on the go and keep your workflow.