-
-
Notifications
You must be signed in to change notification settings - Fork 43
Not applying theme corretly in Ubuntu 24.04 #255
Comments
Seems like a gnome-shell issue. The best way to see if this is the case would be to install |
@isabelroses I applied the theme using gnome-tweaks, here is that and screenfetch: |
Your shell theme doesn't seem to be applying properly, nor your GTK4 theme. Can you |
Those look like dead symlinks to me. Bash does not have error checking for unset vars, so it looks like it symlinked to a dir that does not exist. Shall we try again with something like this. (this does assume that you have the catppuccin themes in It's important that you replace ln -sf "${HOME}/.local/share/themes/<put the catppuccin theme name here>/gtk-4.0/gtk-dark.css" "${HOME}/.config/gtk-4.0/gtk-dark.css"
ln -sf "${HOME}/.local/share/themes/<put the catppuccin theme name here>/gtk-4.0/gtk.css" "${HOME}/.config/gtk-4.0/gtk.css"
ln -sf "${HOME}/.local/share/themes/<put the catppuccin theme name here>/gtk-4.0/assets" "${HOME}/.config/gtk-4.0/assets" |
Thank you! That did the trick 🙌🏻 |
Is there an existing issue outlining your problem?
Describe the bug.
The theme only works in a couple of random places, like the Gnome power menu and some apps like Shotwell. It doesn't apply anywhere else. I installed it using the installation script and applied the theme to the Shell and Legacy Applications with the Gnome tweak tool.
I also added the symlinks:
I tried using the script:
./install.py macchiato lavender --link
and then the manual way:
mkdir -p "${HOME}/.config/gtk-4.0" && ln -sf "${THEME_DIR}/gtk-4.0/assets" "${HOME}/.config/gtk-4.0/assets" && ln -sf "${THEME_DIR}/gtk-4.0/gtk.css" "${HOME}/.config/gtk-4.0/gtk.css" && ln -sf "${THEME_DIR}/gtk-4.0/gtk-dark.css" "${HOME}/.config/gtk-4.0/gtk-dark.css"
screefetch shows that catppucin is installed as the GTK theme, but WM Theme is listed as Yaru.
Attach screenshots.
How did you install the theme?
From release (install.py)
Are you running the latest release, and if not does the issue persist there?
If using GTK4, have you symlinked the "gtk-4.0" folder?
gtk-4.0
folder.What GNOME version are you seeing the bug on?
GNOME Version 46.0.1
Any additional comments?
No response
The text was updated successfully, but these errors were encountered: