yay -Syyu to update everything, and after doing that for like a week ago, spotify started having this reaally oldlooking titlebar. i asked the allmighty le chat about it, but it wants me to toggle a setting which doesnt exist or writing an own css file, which im not comfortable doing. I havent found anything in settings that would suggest a solution to the problem. Do anyone now how to fix it, or should just wait for an update?
Hi @Fruktsallad,
All I can recommend as a plasma non-spotify user, is clearing the cache:
rm -fr ~/.cache/*
…logging out, and logging in again.
AI chatbots are not a reliable source of information
support.spotify.com has a disclaimer for their AI
Answers are generated by AI, and may not always be accurate.
AUR (en) - spicetify-cli
Command-line tool to customize Spotify client
Themes | Spicetify
One of the most popular features in Spicetify is theming. You can customize your Spotify to your heart’s desire! However, this is a very cumbersome task.For this reason, the theming heroes of the Spicetify community have created a huge library of themes which can be found in the following repositories:
Some themes are also available from AUR - spicetify-theme
That is not a safe way to use yay.
Using yay -Syu (or yay without any parameters) will update all installed Repo and AUR sourced packages at the same time – this in dangerous 
Repo updates should be processed first (on their own) before any foreign sources such as the AUR.
Ignoring this rule can lead to a system being left in an unsupported state, due to system packages and dependencies being replaced by older (often incompatible) versions.
pacman and/or pamac (with appropriate parameters) is generally suggested, however, if you really must use yay please use it responsibly, as shown (below).
1. Update packages from the Manjaro repo(s):
pamac update --no-aur (using pamac)yay -SyuN – or – yay -Syu --repo (using yay)2. Build/update software sourced via the AUR:
pamac update --aur (using pamac)yay -Sua – or – yay -Su --aur (using yay)3. If you use flatpak “containerised” apps:
flatpak updateThe important factor is to maintain separation between updating from the Manjaro repos, the AUR or any other foreign sources.
Regards
Ignoring package update in Pamac flags others for deletion
Ignoring AUR packages when updating is not necessary since this commit 1 March 2025
perform sysupgrade transaction always separately from AUR · manjaro/libpamac@c629d1d · GitHub
From an issue reported on 23 Feb 2025
Please make the upgrade process a two step process: First upgrade repo packages only, then upgrade AUR packages · Issue #488 · manjaro/pamac · GitHub
I have been testing this commit inpamac-gtk3by updating repository and AUR packages at the same time. Building AUR packages is postponed until after repository packages have been fully updated, and user has options to either Edit build files, Cancel or Apply
Releases · manjaro/libpamac - 11.7.3 · GitHub
always perform sysupgrade transaction separately from AUR
No of the suggested fixes worked, so ive continued looking around. i found this page, which probably explains why it is as it is, if someone stumbles over the same problem later.
Closed without a solution.