dash to panels better, tied with arcmenu and pip

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.

If you still need help:

1. Open a TTY (Ctrl+Alt+F3 for example, works from F1 to F6 but depending on Wayland or Xorg F1, F2 and/or F6 may be used so F3 should be good, otherwise try another one).
2. The TTY will ask for your username and password, so login with your normal user (not root).
3. You shoud get to an interactive shell, so you can go to the Gnome extensions directory (cd ~/.local/share/gnome-shell/extensions/).
4. You can now remove the problematic extension (rm -r …).
5. Now either you reboot your computer (the reboot command will be enough to restart the computer), this will ensure you don’t keep a remaining session and you’ll boot in your login manager (GDM I guess).

Hope it helps!

https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/customizing_the_gnome_desktop_environment/managing-gnome-shell-extensions-via-command-line_customizing-the-gnome-desktop-environment

Oh no, my desktop is fried!

1. Create a new user.
2. Login as new user.
3. Copy your old files over.
5. Profit.