Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork638
-
Read the FAQ first
DescriptionI wanted to have different logos in different themes, in fastfetch.sh there are these lines At the same time when writing the path manually in ~/.config/fastfetch/config.jsonc The logo itself is fine and when moved to the ~/.config/fastfetch/logo folder it displays correctly fastfetch.sh logo --theme I did this and still get the same error again bash /home/eigver/.local/lib/hyde/test.sh ls “/home/eigver/.config/hyde/themes/Rosé Pine/logo/roxy_icon.png”. here's what's inside /home/eigver/.local/lib/hyde/test.sh and here's what's inside the config ~/.config/fastfetch/config.jsonc “source“:”$(bash /home/eigver/.local/lib/hyde/test.sh)”, “height”: 18 I moved graphite mono to the theme and it turns out the same thing, I think it's worth trying to create a theme without spaces. (but I think that's not the mistake). Version usedfastfetch 2.40.4 (x86_64) Bug prevalenceAlways RegressionNot sure InstallationPackage manager Package managerpacman ScreenshotsConfigurationAttached the entire file above, as it is not very convenient with “cat” for personal reasons Image protocol.png Terminalzsh on kitty Image triedError messagefastfetch --show-errors Features built-in |
BetaWas this translation helpful?Give feedback.
All reactions
Replies: 5 comments
-
Reformatted by AI DescriptionI wanted to have different logos in different themes. In if [-n “${HYDE_THEME}” ]&& [-d “${confDir}/hyde/themes/${HYDE_THEME}/logo” ];then image_dirs+=(“${confDir}/hyde/themes/${HYDE_THEME}/logo/”)fi I added the logo directory to one of the themes and placed my image there. However, instead of the expected picture, I got the ASCII Arch logo.
Additional Observations
Configuration
Steps to Reproduce
Version Used
Terminal
Error Messages
Attached Files and ImagesFeatures Built-in |
BetaWas this translation helpful?Give feedback.
All reactions
-
Hi! I am a maintainer of the dotfiles which is being referenced here. I would like to clear things out to avoid confusion. So, the main gist is, the "source" key in config.jsonc fails when the output path (generated by a script outputs a path with spaces in it.
and also@eigver reports that it works in neofetch. The only one failing is when a script outputs a path with spaces. |
BetaWas this translation helpful?Give feedback.
All reactions
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
-
Because the file path contains white space, it must be quoted: To test the source path, in sh: $ ls -l"$(~/script.sh)"# ls -l <text-in-logo-source> |
BetaWas this translation helpful?Give feedback.
All reactions
❤️ 1
-
This doesn't help. Neofetch itself is written in bash, so it works better with bash scripts of course. fastfetch is not neofetch. |
BetaWas this translation helpful?Give feedback.
All reactions
🎉 1
-
I tried quoting it as an output lol. It made sence now as the quote in jsonc are not included. Thank you! |
BetaWas this translation helpful?Give feedback.
All reactions
This discussion was converted from issue #1706 on April 22, 2025 02:09.

