Affected users who are running X11 should audit their Zoom version, isolate conferencing workloads onto dedicated hardware or virtual machines, or move to a browser-based version of Zoom where sandboxing prevents unprompted clipboard access.
Anyone running a Linux system with Wayland should be OK.
It’s been quite a while since I’ve had issues with Wayland, but for a while there I was convinced that the only testing done on it was on a single screen laptop, because as soon as you attached a second standalone monitor (or third or fourth) all hell broke loose.
Also Flatpak would be helpful in this case too, if there was a package for.
Thank you. This is the summary I needed.
And this is exactly why I put up with the functionality regressions of Wayland over X11 for the first few years.
It’s been quite a while since I’ve had issues with Wayland, but for a while there I was convinced that the only testing done on it was on a single screen laptop, because as soon as you attached a second standalone monitor (or third or fourth) all hell broke loose.
It’s just a better compositor. X is roughly half a million bandaids in a 30 year old trench coat.
I understood that all X11 apps running under Wayland are running inside the same environment, or is that wrong?
In other words, all X11 clipboards are shared.
I’m also not sure about clipboard isolation, since I’d have thought that copy/paste between Wayland and X11 would be expected.