Using Perplexity search engine in Zen Browser gives (I used Ubuntu 24.04 in search criteria as that is what Zorin 18 is a fork of):
" Bluecherry’s .deb packages are built for older Ubuntu versions and can break the desktop on 24.04, often leaving you stuck at the login screen or in a login loop. The system itself is usually recoverable without reinstalling Ubuntu.
Step 1: Get to a text console
Try to reach a TTY (text login):
- Press
Ctrl + Alt + F3 (or F2–F6) at the login or error screen.
- Log in with your usual username and password.
If this works, you can repair the system from there.
Step 2: Remove Bluecherry packages
Once logged in on the TTY, remove the Bluecherry client and any related packages:
bash
sudo apt-get remove --purge bluecherry-client bluecherry*
sudo apt-get autoremove
If you installed it from a .deb file with dpkg -i, also run:
bash
sudo apt-get -f install
These commands remove the client and fix broken dependencies that can block the desktop from starting correctly.
Step 3: Fix broken packages and reconfigure
Still in the TTY, run these commands in order:
bash
sudo dpkg --configure -a
sudo apt-get -f install
sudo apt-get update
sudo apt-get upgrade
If there were dependency or partial‑install problems, this sequence usually repairs them so the graphical session can start again.
Step 4: Check the display manager
On Ubuntu 24.04 the display manager is usually gdm3:
bash
sudo systemctl status gdm3
- If it shows “inactive” or “failed”, try:
bash
sudo systemctl restart gdm3
- If it still fails, reinstall it:
bash
sudo apt-get install --reinstall gdm3
sudo dpkg-reconfigure gdm3
sudo reboot
Similar steps are used for other display managers such as lightdm if you had switched to one.
Step 5: If you still cannot log in
If the above does not work, from the TTY you can create a fresh user to test whether the issue is per‑user or system‑wide:
bash
sudo adduser testuser
sudo usermod -aG sudo testuser
sudo reboot
Then try logging into the desktop as testuser. If that user works, the problem is likely in your original account’s configuration (for example, a corrupted GNOME or Wayland config) rather than Ubuntu itself.
If you can share what exactly you see now (login loop, black screen, “Oh no! Something has gone wrong”, etc.) and whether TTY works, more targeted commands can be suggested."