Changing the refresh rate on my display seems to have fixed this issue for me.
Another:
I may have found the cause of the problem. if you look, the second animation is actually the animation that gnome shell runs when you minimize windows. gnome shell minimize application to the "activities" button while dash to dock tend to override to bottom, left or right depending on where you put the dock
_
we need to disable the gnome shell animation and I emphasize that this glitch does not occur in wayland session
Others mention disabling extensions to solve the issue...
I also saw comments that cover this and honestly, seeing that the bug is still in the confirmed state, I don't think there is a final solution for this yet that doesn't involve disabling the animation or.. migrating to wayland.
Just to point out that issues with screen-sharing is down to Wayland full stop. Nothing to do with Zorin. When I installed Zorin 17.1 I removed everything to do with the Zorin/Gnome DE and installed Plasma 5.24 and Enlightenment DE. The downside to the latter is I keep getting notifications of a newer version but no way to install it!
I see what you mean, these "flaws" are not inherit of Zorin implementation per se but it doesn't change the fact that they should have responsibility of the software they choose to implement into their OS. At least, turn into a priority trying to improve the implementation itself to minimize bugs.
If you have a distribution that has problems with depreciated audio manager for example, it should be a critical goal to try to fix it before launching the OS. Of course, it's way easier said than done but they could be more transparent about problems they are having and possible solutions.
They made the choice to make Wayland the default so they should make a clear goal of fixing the way it crashes with screenshare in other softwares imo.
If the primary purpose is to appeal to Windows OS users, then the broad and sweeping stable support of X11 is by far, preferable.
Having 17 default to Wayland, from the perspective of a Windows User, makes no sense.
The list of stuff that does not work with Wayland is a long one. And this even includes hardware like Nvidia.
Why complicate the system? Many of these users are already struggling with WINE, trying to learn about Flatpak and APT... Why subject new users to immediately having to troubleshoot the fact that One Default Setting was all that messed them up?
Certainly, some say that Wayland is going to fix all these issues and it will all be working soon. Everything will be fine.
Promises... great so... why is it here?Now?
It's not ready so Why Is It Here?
ZorinGroup has often stated that they adhere to a strict "Release When Ready" Policy. Yet, they released Zorin OS 17 with an Unready default Display Protocol that has been unready for over ten years and there is no indication of any actual coded fixes, yet.
-shrug-
There is no part of this that makes sense and no part of it that aligns to the publicly stated goals of the ZorinGroup.
Glad I'm using Cosmic DE, even if it's in Alpha stage. I just got fed up with Gnome and Nvidia. So I switched to Cosmic and switch card to Radeon. It's a breeze.
I'm not privy to various Gnome shell numbers but suspect the Gnome shell used for Zorin 17 has Wayland embedded in it. At least with Plasma the default is X11 (xorg) with Wayland being the second option, based on my experience with other distributions. You see you can't remove systemd or pulse audio without taking the whole OS with it. At least in terms of Audio I have audacious which lets me access ALSA over Pulse Audio and Pipewire. Audacious means I get sound out of all my speakers from Logitech!
