State clearly which distro and which versions of Gnome and dash-to-dock and perhaps what other extensions you are running, and there might be a chance someone is able to help you. (Also state clearly the source of your Gnome extensions).
Most of the hints/solutions in answer to this post are also not good. If dash-to-dock triggered the malfunction of the gnome-shell on your system, just login to a terminal and use dconf or gsettings to
set org.gnome.shell enabled-extensions to an empty array or to an array w/o dash-to-dock.
I am happily running dash-dock@micxgx.gmail.com on multiple physical and virtual machines w/o any trouble, using the dash-to-dock provided by my package manager on different CPU architectures YMMV.
Sorry, but this post is really, really bad.
State clearly which distro and which versions of Gnome and dash-to-dock and perhaps what other extensions you are running, and there might be a chance someone is able to help you. (Also state clearly the source of your Gnome extensions).
Most of the hints/solutions in answer to this post are also not good. If dash-to-dock triggered the malfunction of the gnome-shell on your system, just login to a terminal and use dconf or gsettings to set org.gnome.shell enabled-extensions to an empty array or to an array w/o dash-to-dock.
I am happily running dash-dock@micxgx.gmail.com on multiple physical and virtual machines w/o any trouble, using the dash-to-dock provided by my package manager on different CPU architectures YMMV.
Ubuntu 22, but it’s too late I installed something else