Question: Is this a GNOME architecture issue? I hope KDE could avoid this issues, atm on Xorg I can restart the window manager and the desktop shell without losing any data.
Yes. And always has been since like forever ago. I'm all for choice and diversity, but I've personally never understood all the love and excitement and attention that GNOME has gotten ever since Canonical got behind it and dropped Unity.
I'm certainly not it's target audience - running XFCE, LXDE/LXQT, and i3/Sway over the years - but it really gobsmacks me to hear the cheerleading over what seem like really basic fixes, like "now the single-threaded shell crashes to login less often! Horray!"
If Linux would have decided to use Mir would have at least shared same "server" code and probably also get around this issues but is hard to promote quality when Gnome and RedHat has a different idea.
That's because there is no such thing as "wayland" actually running on your machine -- it's simply a protocol for compositors and applications to talk to each other.
"Wayland" is also an implementation. The protocol and implementation share a name. By the look of things, Gnome does indeed require it (that is, various "libwayland" packages) on Ubuntu.
Wikipedia:
> Wayland is a communication protocol that specifies the communication between a display server and its clients, as well as a C library implementation of that protocol.
That's the C library also named Wayland and made by the people guiding the Wayland spec on which Gnome depends, no? Or are there three things going by the name Wayland, one of them not actually associated with the Wayland project?
AFAIUI, e.g. KDE doesn't actually use any of that. (I could be wrong, I honestly don't care that much about the minutiae.)