[Bug]: app themes not syncing
AlexandrosMelissas opened this issue · comments
Bug Report
Description
When i change a theme, for example, vs code or spotify won't follow the theme. Even if i change wallbash mode. Is this intended? It used to work. Is this related? #1310
Steps to Reproduce
- Super + Shift + T to open theme menu
- Change to a different theme
- VSCode or Spotify won't follow the theme
Expected Behavior
The apps to follow the theme
Actual Behavior
Nothing changed
- Linux Distro: ArchLinux
- Linux Version, output of
uname -a
: Linux alex-b650aoruseliteaxice 6.9.1-zen1-1-zen #1 ZEN SMP PREEMPT_DYNAMIC Fri, 17 May 2024 16:56:18 +0000 x86_64 GNU/Linux - Hyprland Version, output of
hyprctl version
: Hyprland, built from branch at commit cba1ade848feac44b2eda677503900639581c3f4 (props: bump version to 0.40.0). - Installation Environment: Main
- Other info: 1440p
please provide any output of themeselect.sh
after selecting a theme
Spotify
- be sure to have spotify and spicetify-cli
- run
wallbashspotify.sh --reset
incase the theme is not yet set.
Code
- Be sure you remove all the old ~/.config/Code* and ~/.vscode*
==> So if you're using code-oss remove the other code derivatives.
this is the output for wallbashspotify.sh --reset
(wouldnt work without sudo)
❯ wallbashspotify.sh --reset
==== AUTHENTICATING FOR org.freedesktop.policykit.exec ====
Authentication is needed to run `/usr/bin/chmod a+wr /opt/spotify' as the super user
Authenticating as: alex mel (alexm)
Password:
polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
==== AUTHENTICATION FAILED ====
Error executing command as another user: Not authorized
This incident has been reported.
==== AUTHENTICATING FOR org.freedesktop.policykit.exec ====
Authentication is needed to run `/usr/bin/chmod a+wr /opt/spotify/Apps -R' as the super user
Authenticating as: alex mel (alexm)
Password:
polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
==== AUTHENTICATION FAILED ====
Error executing command as another user: Not authorized
This incident has been reported.
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 5149 100 5149 0 0 6321 0 --:--:-- --:--:-- --:--:-- 6321
spicetify v2.36.11
info Spicetify up-to-date
Backing up app files:
OK
Extracting:
OK
Preprocessing:
info Fetching remote CSS map for newer compatible tag version: master
OK
OK
success Everything is ready, you can start applying now!
Copying raw assets:
fatal unlinkat /opt/spotify/Apps/login.spa: permission denied
success Config changed: current_theme = Sleek
info Run "spicetify apply" to apply new config
success Config changed: color_scheme = Wallbash
info Run "spicetify apply" to apply new config
spicetify v2.36.11
info Spicetify up-to-date
Copying raw assets:
fatal unlinkat /opt/spotify/Apps/login.spa: permission denied
❯ sudo wallbashspotify.sh --reset
find: ‘/root/.config/hyde/themes’: No such file or directory
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
Warning: Failed to open the file
Warning: /root/.cache/hyde/landing/Spotify_Sleek.tar.gz: No such file or
Warning: directory
0 5149 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (23) Failure writing output to destination, passed 1369 returned 4294967295
tar (child): /root/.cache/hyde/landing/Spotify_Sleek.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
spicetify v2.36.11
info Spicetify up-to-date
Backing up app files:
OK
Extracting:
OK
Preprocessing:
info Fetching remote CSS map for newer compatible tag version: master
OK
OK
success Everything is ready, you can start applying now!
Copying raw assets:
OK
success Custom CSS is updated
Applying additional modifications:
OK
success Spotify is spiced up!
success Config changed: current_theme = Sleek
info Run "spicetify apply" to apply new config
success Config changed: color_scheme = Wallbash
info Run "spicetify apply" to apply new config
spicetify v2.36.11
info Spicetify up-to-date
error Theme "Sleek" not found
this is the output after applying the proposed changes:
❯ themeselect.sh
:: applying theme :: "Catppuccin Latte"
:: applying wall :: "/home/alexm/.config/hyde/themes/Catppuccin Latte/wallpapers/cat_minimal.jpg"
:: deploying wallbash colors :: light wallpaper detected
VsCode still wont follow the theme
Spotify
NO, it should not be run as sudo because root don't have Spotify configuration.
Nothing popups if you run the command asking you a password?
Manually grant this perms, it is in the spicetify-cli documentation if you wanna check it
This is only the part that needs sudo.
sudo chmod a+wr /opt/spotify
sudo chmod a+wr /opt/spotify/Apps -R
VsCode still wont follow the theme
This needs manual restart of vscode ( you don't want to wipe your progress just to change themes) .
And be sure to clean up the old code derivative folders.
Note
The error message you get during the themeselect.sh
command will disappear(run on a separate thread) so try to observed it before it dissapears.
Hmmm it's very very fast but it's something like: [skip] home/alexm/.config/cava/Wall-Dcol
.
Also after applying chmods to spotify, i think reset runs successfully:
❯ wallbashspotify.sh --reset
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 5149 100 5149 0 0 16057 0 --:--:-- --:--:-- --:--:-- 16057
spicetify v2.36.11
info Spicetify up-to-date
info There is available backup.
info Clear current backup:
warning After clearing backup, Spotify cannot be backed up again.
info Please restore first then backup, run "spicetify restore backup" or re-install Spotify then run "spicetify backup".
success Config changed: current_theme = Sleek
info Run "spicetify apply" to apply new config
success Config changed: color_scheme = Wallbash
info Run "spicetify apply" to apply new config
spicetify v2.36.11
info Spicetify up-to-date
warning Spotify version and backup version are mismatched.
info Spotify cannot be backed up at this state. Please re-install Spotify then run "spicetify backup apply".
But spotify still wont show anything. I also tried restarting vscode and the theme still wont follow.
I also tried rebooting.
Also noticed there is no such file in this path: ~/.config/cava/Wall-Dcol
. Instead i can see a folder with that name in ~/.config/hyde/wallbash/Wall-Dcol
Look spicetify-cli is telling you something. This needs manual intervention.
Also noticed there is no such file in this path: ~/.config/cava/Wall-Dcol. Instead i can see a folder with that name in ~/.config/hyde/wallbash/Wall-Dcol
This is expected as you don't have a cava config and unrelated.
wallbashcode.sh
try to run this. This one is the script that handles vscode.
Just to be sure if the configs even exist
find ~/.config -mindepth 1 -maxdepth 1 -type d -name "Code*"
also this one can you give outputs for this
find "$HOME" -mindepth 1 -maxdepth 1 -type d -name ".vscode*"
The configs seem to exist. Running wallbashcode.sh does nothing, no output. Also, tried to correct spicetify errors but i get a error Theme "Sleek" not found
error.
These are all the logs:
❯ wallbashspotify.sh --reset
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 5149 100 5149 0 0 6407 0 --:--:-- --:--:-- --:--:-- 6407
spicetify v2.36.11
info Spicetify up-to-date
info There is available backup.
info Clear current backup:
warning After clearing backup, Spotify cannot be backed up again.
info Please restore first then backup, run "spicetify restore backup" or re-install Spotify then run "spicetify backup".
success Config changed: current_theme = Sleek
info Run "spicetify apply" to apply new config
success Config changed: color_scheme = Wallbash
info Run "spicetify apply" to apply new config
spicetify v2.36.11
info Spicetify up-to-date
warning Spotify version and backup version are mismatched.
info Spotify cannot be backed up at this state. Please re-install Spotify then run "spicetify backup apply".
❯ sudo pacman -S spotify
[sudo] password for alexm:
warning: spotify-1:1.2.37.701-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
Package (1) Old Version New Version Net Change
chaotic-aur/spotify 1:1.2.37.701-1 1:1.2.37.701-1 0,00 MiB
Total Installed Size: 292,43 MiB
Net Upgrade Size: 0,00 MiB
:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring [------------------------------------------------------------] 100%
(1/1) checking package integrity [------------------------------------------------------------] 100%
(1/1) loading package files [------------------------------------------------------------] 100%
(1/1) checking for file conflicts [------------------------------------------------------------] 100%
(1/1) checking available disk space [------------------------------------------------------------] 100%
warning: could not get file information for opt/spotify/Apps/login.spa
warning: could not get file information for opt/spotify/Apps/xpui.spa
:: Running pre-transaction hooks...
(1/2) Rejecting pacman transaction if running in snapshot...
(2/2) Performing snapper pre snapshots for the following configurations...
==> root: 59
:: Processing package changes...
(1/1) reinstalling spotify [------------------------------------------------------------] 100%
warning: directory permissions differ on /opt/spotify/
filesystem: 777 package: 755
warning: directory permissions differ on /opt/spotify/Apps/
filesystem: 766 package: 755
:: Running post-transaction hooks...
(1/8) Arming ConditionNeedsUpdate...
(2/8) Foreign/AUR package notification
hyde-cli-git v0.5.2.r6.5202a1e-1
paru-debug 2.0.3-1
python-pyamdgpuinfo 2.1.6-1
swaylock-effects-git r470.496059a-1
(3/8) Orphaned package notification...
base-devel 1-1
cython 3.0.10-3
mbedtls 3.5.2-1
mbedtls2 2.28.8-2
python-build 1.2.1-3
python-installer 0.7.0-8
python-wheel 0.43.0-4
qt5-tools 5.15.13+kde+r4-1
rust 1:1.78.0-1
scdoc 1.11.3-1
(4/8) Checking for .pacnew and .pacsave files...
.pac* files found:
/etc/paru.conf.pacnew
Please check and merge
(5/8) Updating icon theme caches...
(6/8) Updating the desktop file MIME type cache...
(7/8) Performing snapper post snapshots for the following configurations...
==> root: 60
(8/8) Syncing all file systems...
❯ spicetify backup apply
spicetify v2.36.11
info Spicetify up-to-date
info There is available backup.
info Clear current backup:
success Backup is cleared.
Backing up app files:
open /opt/spotify/Apps/login.spa: permission denied
❯ sudo chmod a+wr /opt/spotify/Apps -R
❯ sudo chmod a+wr /opt/spotify
❯ spicetify backup apply
spicetify v2.36.11
info Spicetify up-to-date
Backing up app files:
open /opt/spotify/Apps/login.spa: permission denied
❯ sudo spicetify backup apply
spicetify v2.36.11
info Spicetify up-to-date
info There is available backup.
info Clear current backup:
success Backup is cleared.
Backing up app files:
OK
Extracting:
OK
Preprocessing:
info Fetching remote CSS map for newer compatible tag version: master
OK
OK
success Everything is ready, you can start applying now!
error Theme "Sleek" not found
I m thinking of doing a clean arch install, maybe that will fix everything. Thanks for all your help.
P.S: I would love to contribute in this project some time in the future. I could learn more about hyprland etc. If you want any help with full stack web development, please let me know.
Hey, just as an update. I did a clean arch install (no kde, desktop configs, files etc) and it's working flawlessly. I also love the new hyde cli script. Keep up the good work. Im closing this.