I recently switched from x11 to wayland as I got a new monitor which needed fractional scaling and x11 didn't handle having multiple monitors with differing fractional scaling well.
An issue I've had since switching is that when I unplug my USB C displaylink hub the desktop environment crashes and I'm booted out to the login screen. On logging back in all have quit.
I think the culprit may be the Zorin App Indicator plugin as this is one of the first post-disconnect errors in the log:
May 08 18:06:39 john-xps15-zorin gnome-shell[76310]: [76287:1916407:0508/180639.014799:ERROR:net/socket/socket_posix.cc:93] CreatePlatformSocket() failed: Address family not supported by protocol (97)
May 08 18:06:39 john-xps15-zorin gnome-shell[76310]: [76287:1916407:0508/180639.016420:ERROR:net/socket/socket_posix.cc:93] CreatePlatformSocket() failed: Address family not supported by protocol (97)
May 08 18:06:39 john-xps15-zorin gnome-shell[25510]: JS ERROR: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in Get
_promisify/proto[asyncFunc]/</<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:446:45
### Promise created here: ###
getProperty@/usr/share/gnome-shell/extensions/zorin-appindicator@zorinos.com/util.js:553:33
refreshProperty@/usr/share/gnome-shell/extensions/zorin-appindicator@zorinos.com/appIndicator.js:316:48
_refreshOwnProperties/<@/usr/share/gnome-shell/extensions/zorin-appindicator@zorinos.com/appIndicator.js:202:32
_refreshOwnProperties@/usr/share/gnome-shell/extensions/zorin-appindicator@zorinos.com/appIndicator.js:200:51
_onSignalAsync/refreshPropertiesPromises<@/usr/share/gnome-shell/extensions/zorin-appindicator@zorinos.com/appIndicator.js:256:26
_onSignalAsync@/usr/share/gnome-shell/extensions/zorin-appindicator@zorinos.com/appIndicator.js:255:50
async*_onSignal@/usr/share/gnome-shell/extensions/zorin-appindicator@zorinos.com/appIndicator.js:214:14
_init/<@/usr/share/gnome-shell/extensions/zorin-appindicator@zorinos.com/util.js:504:43
May 08 18:06:39 john-xps15-zorin systemd[1]: docker-150f2e45d6ba89185ca08a69229ac3882233571571bda46afe1c1c1ab303d5c7.scope: Deactivated successfully.
May 08 18:06:39 john-xps15-zorin systemd[1]: docker-150f2e45d6ba89185ca08a69229ac3882233571571bda46afe1c1c1ab303d5c7.scope: Consumed 1.696s CPU time.
May 08 18:06:40 john-xps15-zorin containerd[1987]: time="2025-05-08T18:06:40.003724382+01:00" level=info msg="shim disconnected" id=150f2e45d6ba89185ca08a69229ac3882233571571bda46afe1c1c1ab303d5c7 namespace=moby
May 08 18:06:40 john-xps15-zorin containerd[1987]: time="2025-05-08T18:06:40.003770771+01:00" level=warning msg="cleaning up after shim disconnected" id=150f2e45d6ba89185ca08a69229ac3882233571571bda46afe1c1c1ab303d5c7 namespace=moby
May 08 18:06:40 john-xps15-zorin containerd[1987]: time="2025-05-08T18:06:40.003784399+01:00" level=info msg="cleaning up dead shim" namespace=moby
May 08 18:06:40 john-xps15-zorin dockerd[10658]: time="2025-05-08T18:06:40.003778744+01:00" level=info msg="ignoring event" container=150f2e45d6ba89185ca08a69229ac3882233571571bda46afe1c1c1ab303d5c7 module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Has anyone else seen this issue and know of any fixes/workarounds that don't involve disabling the extension, which is a last resort.
There's a lot in the logs, so I can't be 100% sure that's the culprit, but from reading around it seems likely.
Next time I'm in work I'll try unpluggin but with the extension disabled and see what happens.