[BUG] Chafa arguments seemingly ignored

[kartcs]

Read the FAQ first

• I have checked the FAQ but the issue is not covered

Description

Tried to set chafa config arguments for a custom image, but they are seemingly ignored. Displays as default chafa output.

Version used

fastfetch 2.41.0 (x86_64)

Bug prevalence

Always

Regression

Not sure

Installation

Package manager

Package manager

pacman

Screenshots

image display with arguments provided in config file:

image displayed with chafa (same arguments):

(yes i was using neofetch before this)

Configuration

{
  "$schema": "https://github.com/fastfetch-cli/fastfetch/raw/dev/doc/json_schema.json",
  "logo": {
      "type": "chafa", 
      "source": "~/Desktop/neofetch/kartcat.png",     
      "width": 30,
      "height": 13,
      "chafa": {
        "fgOnly": true,
        "symbols": "ascii"
      }
  },
  "modules": [
    "title",
    "separator",
    "os",
    "kernel",
    "shell",
    "de",
    "wmtheme",
    "terminal",
    "cpu",
    "gpu",
    "memory",
    "break",
    "colors"
  ]
}

Image protocol

chafa

Terminal

GNOME Terminal 3.56.1

Image tried

kartcat my beloved

Error message

no errors displayed

Features built-in

threads
vulkan
wayland
xcb-randr
xrandr
drm
drm_amdgpu
gio
dconf
dbus
imagemagick7
chafa
zlib
xfconf
opencl
libpulse
libddcutil
libelf
libzfs
Directx Headers
System yyjson
linux/videodev2
linux/wireless

[CarterLi]

Fastfetch caches the generated ASCII logos. Please try fastfetch --logo-recache

[kartcs]

Thanks! That fixed the arguments being ignored, however it seems that it has "inverted" as a pre-chosen symbol to use, which cannot be removed as far as i can tell? Is there a way to have it use ascii as the default?

[CarterLi]

Fixed in the dev branch. For now, you can work around this issue by specifying --chafa-symbols ascii in command line. After the ASCII art is generated the flags can be omitted since the ASCII logo will be cached