Fastfetch gives accent-color error on F40

[Danar435]

Describe the bug

Executing Fastfetch on Bluefin GTS results in an error right before the output: No such key “accent-color”

What did you expect to happen?

There should be no error

Output of bootc status

No staged image present
Current booted state is native ostree
Current rollback state is native ostree

State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx:gts
                   Digest: sha256:6736870a710fd6b14af5d5fe020155a40bf05cb83ac41f662862beea468ce40a
                  Version: gts-40.20241216.1 (2024-12-16T13:20:52Z)
          LayeredPackages: waydroid

  ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx:gts
                   Digest: sha256:c6b01cd449234fddc32720fc1bec03e95474a878d1ffacdfd85a2a43f0715aa3
                  Version: gts-40.20241208 (2024-12-08T06:12:52Z)
          LayeredPackages: waydroid

Output of groups

kristiyan wheel audio lxd incus-admin docker libvirt

Extra information or context

This should not be an issue in the next major Fedora release

[castrojo]

This is likely because there's no accent colors in the version of gnome in gts. Ideally we should skip the value if we're on F40.

[Danar435]

bluefin/system_files/shared/usr/libexec/ublue-bling-fastfetch

Line 3 in 8512e3c

THEME=$(gsettings get org.gnome.desktop.interface accent-color || echo "'slate'")

There is a fallback for when the gsettings command fails, but the output is printed to the users whenever that happens. This also happens with motd. I can hide it by redirecting the output to /dev/null. Should I open a PR?

[castrojo]

Yeah a PR would be lovely!