Un-Dr460nize KDE

For systems still on Dr460nized

This guide is for systems that still run the Dr460nized KDE settings. The packages and theme names may have changed since the original guide was published in 2024. Check the package names with pacman -Qs dr460nized before you follow the steps. Compare the paths against the current package in the garuda-dr460nized repository.

Garuda Linux ships a bold KDE look with the Dr460nized spin. Some users want the other KDE features Garuda offers but a calmer desktop theme. Restoring a plain KDE setup is harder once Dr460nized is applied, because the garuda-dr460nized package deploys a large preset.

The package provides its settings through /etc/skel. Removing the package does not remove the files already copied into your home directory. This guide covers both steps.

Current package facts

Item	Current value
Package	garuda-dr460nized (a garuda-dr460nized-git variant also exists)
Settings source	/etc/skel from the package
Theme names	Look and feel Dr460nized, Plasma desktop theme Dr460nized, Kvantum Dr460nized, Aurorae Sweet-Dark with the dr460nized window button settings
Dependencies	garuda-fish-config, garuda-common-settings, beautyline, garuda-icons and others. These stay installed when you remove the package.
Related packages	grub-theme-garuda-dr460nized and plymouth-theme-dr460nized are separate packages. Removing garuda-dr460nized does not remove them.

Method 1: Remove the package and create a new user

1. Confirm your backups are up to date. Snapper snapshots cover the system, but the home directory is not part of them unless you set up a Snapper config for it yourself.

2. Remove the package:

   sudo pacman -R garuda-dr460nized

3. Create a new user in System Settings → System → Users. Sign in as the new user and use that account from now on.

Method 2: Remove the leftover settings from your home directory

Advanced

Make sure you have backups and that you know how to restore them. The home directory is not captured in Snapper snapshots unless you created a Snapper config for it.

First, make a copy of /etc/skel.

sudo cp -r /etc/skel /etc/skel_old

What is /etc/skel?

/etc/skel is a system directory that serves as a template for new user accounts. Its files are copied into the home directory when a user is created, including during the initial installation. Much of the Dr460nized customization is done through /etc/skel.

1. Remove the package. This also removes the configuration it provides in /etc/skel.

   sudo pacman -R garuda-dr460nized

2. Compare the old and the new /etc/skel. The files that only exist in /etc/skel_old are the ones the package created in your home directory.

   diff -rqn /etc/skel/ /etc/skel_old

   The example below comes from the 2024 package. Your list can differ.

   Only in /etc/skel_old/.config/autostart: initial-setup.desktop
   Only in /etc/skel_old/.config: baloofilerc
   Only in /etc/skel_old/.config: dolphinrc
   Only in /etc/skel_old/.config/environment.d: garuda.conf
   Only in /etc/skel_old/.config: gtk-3.0
   Only in /etc/skel_old/.config: gtk-4.0
   Only in /etc/skel_old/.config: katerc
   Only in /etc/skel_old/.config: kcminputrc
   Only in /etc/skel_old/.config: kdeglobals
   Only in /etc/skel_old/.config: konsolerc
   Only in /etc/skel_old/.config: kscreenlockerrc
   Only in /etc/skel_old/.config: Kvantum
   Only in /etc/skel_old/.config: kwinrc
   Only in /etc/skel_old/.config: libinput-gestures.conf
   Only in /etc/skel_old/.config: mimeapps.list
   Only in /etc/skel_old/.config: touchpadrc
   Only in /etc/skel_old/.config: touchpadxlibinputrc
   Only in /etc/skel_old: .firedragon
   Only in /etc/skel_old: .icons
   Only in /etc/skel_old/.local/share: konsole

3. Advanced users can go through the files one by one and keep the ones they want. The ~/.config entries can be listed with sed:

   diff -rqn /etc/skel/ /etc/skel_old | sed -n 's|^Only in /etc/skel_old/.config: ||p' | tr '\n' ',' | sed 's/,$//'

   Then remove them with brace expansion. Replace the list with the output of the command above.

   rm -r ~/.config/{baloofilerc,dolphinrc,gtk-3.0,gtk-4.0,katerc,kcminputrc,kdeglobals,konsolerc,kscreenlockerrc,Kvantum,kwinrc,libinput-gestures.conf,mimeapps.list,touchpadrc,touchpadxlibinputrc}

4. Remove the remaining files and folders:

   rm -r ~/.config/autostart/initial-setup.desktop ~/.config/environment.d/garuda.conf ~/.firedragon ~/.icons ~/.local/share/konsole

   The ~/.firedragon folder is not part of the current /etc/skel. The command still works, and it does nothing if the folder is missing.

5. Reboot to see the plain KDE setup.

Note

Removing the Konsole settings also removes the Garuda Konsole profile. The terminal may then not open Fish, as reported.

Optional: Disable the Garuda Starship prompt in Bash

Garuda uses Starship for the Bash and Fish prompt. The package garuda-starship-prompt is a dependency of garuda-fish-config and garuda-bash-config, so it is not removed with Dr460nized. If you want a blank prompt in Bash, disable Starship in your ~/.bashrc.

1. Rename the Starship configuration file:

   mv ~/.config/starship.toml ~/.config/starship.toml.bak

2. Make a backup of your ~/.bashrc:

   cp ~/.bashrc ~/.bashrc.orig

3. The Starship block is in /usr/share/garuda/garuda-bash-config/bashrc, which your ~/.bashrc sources with the line source /usr/share/garuda/garuda-bash-config/bashrc. Do not edit that file, because a package update overwrites it. Instead, replace the source line in ~/.bashrc with the contents of that file, then comment out the Starship block in your copy. The block starts with # Load starship prompt if starship is installed and ends with fi. After commenting, it looks like this:

   # Load starship prompt if starship is installed
   # if [ -x /usr/bin/starship ]; then
   #   __main() {
   #     local major="${BASH_VERSINFO[0]}"
   #     local minor="${BASH_VERSINFO[1]}"
   #
   #     if ((major > 4)) || { ((major == 4)) && ((minor >= 1)); }; then
   #       source <("/usr/bin/starship" init bash --print-full-init)
   #     else
   #       source /dev/stdin <<<"$("/usr/bin/starship" init bash --print-full-init)"
   #     fi
   #   }
   #   __main
   #   unset -f __main
   # fi

4. Log out and back in. You now have a blank prompt that you can set up in your ~/.bashrc.

Note

Fish also loads Starship in config.fish. Disabling it in ~/.bashrc does not change the Fish prompt.

Follow-up considerations

• This is an unsupported procedure. Do not open forum issues about settings you removed on purpose. Open a new topic for real bugs.
• Keep this guide focused on the steps. Opinions about the default theme belong in another topic.

---

Source: How to un-Dr460nize KDE on the Garuda forum by BluishHumility, with the Starship notes by tbg.