Issues with matcha-gtk-theme

[D.Dave]

The installation/update of the package matcha-gtk-theme 20250411-1 has attempted to write files under my home directory, specifically by linking /usr/share/themes/Matcha-dark-sea/gtk-4.0/gtk-dark.css and /usr/share/themes/Matcha-dark-sea/gtk-4.0/gtk.css under /home/dave/.config/gtk-4.0/, with the result to have DejaDup and Pavucontrol displayed with the theme matcha, instead of my choosed theme Greybird-dark.

I said “has attempted”, because under /home/dave/.config/gtk-4.0/ I already had a gtk.css file made by me.

To prove this action: I moved my /home/dave/.config/gtk-4.0/gtk.css file elsewhere, reinstalled the package matcha-gtk-theme 20250411-1 and I’ve found the mention applications displayed with the Matcha theme instead of Greybird-dark.

A package shouldn’t write/link files in the user directory, with the aggravating circumstance to change application’s theme.

please take care of this, @philm

A solution to keep the theme choosed by the user, is to delete these linked gtk.css files in ~/.config/gtk-4.0/ to have again DejaDup and Pavucontrol displayed with the user choosed system theme. I am disappointed.

[Yochanan]

I’ve moved your post to a separate topic.

@D.Dave

A package shouldn’t write/link files in the user directory

You’re right. Guess what? Not a single package in the repos–including matcha-gtk-theme–do. As you can see in the PKGBUILD, files are only installed to /usr/share/themes/.

I think you might have seen the message printed during the update and thought it was actually doing what it said. Well, it doesn’t actually do anything, it only prints a message:

To force Libadwaita appliations to use the gtk-4.0 theme,
symlink the gtk-4.0 theme to config folder
(replace Matcha-dark-sea with chosen theme variant):

mkdir -p ~/.config/gtk-4.0/
ln -sf /usr/share/themes/Matcha-dark-sea/gtk-4.0/{assets,gtk.css,gtk-dark.css} ~/.config/gtk-4.0/

[D.Dave]

@Yochanan

Well, it doesn’t actually do anything, it only prints a message

Ok, so I’m really sorry.
I thought that the package was unable to write under ~/.config/gtk-4.0/ due to the fact that I already had a gtk.css file, and so, consequentially , I also thought that the package has triggered a post hook.

So, I admit: I was totally wrong.
Thank you very much, @Yochanan, for the clarification: I promise that the next time, I will pay more attention.

Case closed