Alacritty throwing errors after Migration from YAML to TOML [WARN unused config]

Hello! Went to update today and noticed Alacritty is throwing an error I cannot copy and paste here. Says the following:

“[WARN] See log at /tmp/Alacritty-(numbers).log
YAML is deprecated, please migrate to TOML using Alacritty Migrate”

After completing “alacritty migrate” the original error was replaced by the following in the Alacritty log

[0.000386599s] [WARN ] [alacritty_config_derive] Unused config key: author
[0.000443701s] [WARN ] [alacritty_config_derive] Unused config key: name
[0.000468370s] [WARN ] [alacritty_config_derive] Unused config key: size
[0.000671869s] [WARN ] [alacritty_config_derive] Unused config key: window.decorations_theme_variant
[0.000687057s] [WARN ] [alacritty_config_derive] Unused config key: save_to_clipboard
[0.000697059s] [WARN ] [alacritty_config_derive] Unused config key: theme
[0.000706213s] [WARN ] [alacritty_config_derive] Unused config key: window.dynamic_title

I searched the forums as well as google and all I found on the topic was the Arch Wiki page here: Alacritty - ArchWiki

What can I do to stop the Unused Config errors that now show after migration?

Just in case, I did make a BTRFS snapshot prior to the change in case I need to revert for any reason.


  Kernel: 6.6.8-zen1-1-zen arch: x86_64 bits: 64
    compiler: gcc v: 13.2.1 clocksource: tsc
    available: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=78c2e7f5-5af0-4cd6-a76f-f692f5c10941 rw
    rootflags=subvol=@ quiet quiet intel_iommu=on
    iommu=pt video=efifb:off rd.udev.log_priority=3
    vt.global_cursor_default=0 loglevel=3 ibt=off
  Desktop: KDE Plasma v: 5.27.10 tk: Qt v: 5.15.11
    wm: kwin_x11 vt: 2 dm: SDDM Distro: Garuda Linux
    base: Arch Linux
  Type: Desktop Mobo: ASUSTeK model: STRIX Z270E GAMING
    v: Rev 1.xx serial: <superuser required>
    UEFI: American Megatrends v: 1302 date: 03/15/2018
  Info: model: Intel Core i7-7700K bits: 64 type: MT MCP
    arch: Kaby Lake gen: core 7 level: v3 note: check
    built: 2018 process: Intel 14nm family: 6
    model-id: 0x9E (158) stepping: 9 microcode: 0xF4
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8
    smt: enabled cache: L1: 256 KiB
    desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB
    desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
  Speed (MHz): avg: 2130 high: 2400
    min/max: 800/4500:4600 scaling: driver: intel_pstate
    governor: powersave cores: 1: 2000 2: 2091 3: 2177
    4: 2000 5: 2099 6: 2162 7: 2116 8: 2400
    bogomips: 67200
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1
    sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
  Device-1: NVIDIA GA106 [GeForce RTX 3060]
    vendor: Micro-Star MSI driver: nvidia v: 545.29.06
    alternate: nouveau,nvidia_drm non-free: 545.xx+
    status: current (as of 2023-10; EOL~2026-12-xx)
    arch: Ampere code: GAxxx process: TSMC n7 (7nm)
    built: 2020-2023 pcie: gen: 2 speed: 5 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s ports: active: none
    off: DP-1,DP-2,HDMI-A-1 empty: DP-3 bus-ID: 01:00.0
    chip-ID: 10de:2503 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.10 with: Xwayland
    v: 23.2.3 compositor: kwin_x11 driver: X: loaded: nvidia
    gpu: nvidia,nvidia-nvswitch display-ID: :0 screens: 1
  Screen-1: 0 s-res: 4080x2041 s-dpi: 80
    s-size: 1295x647mm (50.98x25.47")
    s-diag: 1448mm (56.99")
  Monitor-1: DP-1 mapped: DP-0 note: disabled
    pos: primary,bottom-c model: VG278 serial: <filter>
    built: 2020 res: 1920x1080 dpi: 82 gamma: 1.2
    size: 598x336mm (23.54x13.23") diag: 686mm (27")
    ratio: 16:9 modes: max: 1920x1080 min: 640x480
  Monitor-2: DP-2 note: disabled pos: top-right
    model: BenQ ZOWIE XL LCD serial: <filter> built: 2016
    res: 1080x1920 dpi: 81 gamma: 1.2
    size: 340x600mm (13.39x23.62") diag: 686mm (27")
    ratio: 16:9 modes: max: 2560x1440 min: 640x480
  Monitor-3: HDMI-A-1 mapped: HDMI-0 note: disabled
    pos: middle-l model: HP E243 serial: <filter>
    built: 2020 res: 1080x1920 hz: 60 dpi: 93 gamma: 1.2
    size: 296x527mm (11.65x20.75") diag: 604mm (23.8")
    ratio: 16:9 modes: max: 1920x1080 min: 640x480
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0
    drv: nvidia device: 2 drv: swrast gbm: drv: nvidia
    surfaceless: drv: nvidia x11: drv: nvidia
    inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa
    v: 545.29.06 glx-v: 1.4 direct-render: yes
    renderer: NVIDIA GeForce RTX 3060/PCIe/SSE2
    memory: 11.72 GiB
  API: Vulkan v: 1.3.274 layers: 12 device: 0
    type: discrete-gpu name: NVIDIA GeForce RTX 3060
    driver: nvidia v: 545.29.06 device-ID: 10de:2503
    surfaces: xcb,xlib
  Device-1: Intel 200 Series PCH HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel alternate: snd_soc_avs
    bus-ID: 00:1f.3 chip-ID: 8086:a2f0 class-ID: 0403
  Device-2: NVIDIA GA106 High Definition Audio
    vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
    pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
    speed: 16 GT/s bus-ID: 01:00.1 chip-ID: 10de:228e
    class-ID: 0403
  Device-3: Blue Microphones Yeti Stereo Microphone
    driver: hid-generic,snd-usb-audio,usbhid type: USB
    rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1
    bus-ID: 1-6.1:5 chip-ID: b58e:9e84 class-ID: 0300
    serial: <filter>
  Device-4: Creative Sound Blaster X3
    driver: cdc_acm,hid-generic,snd-usb-audio,usbhid
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0
    bus-ID: 1-6.3:8 chip-ID: 041e:3264 class-ID: 0102
    serial: <filter>
  API: ALSA v: k6.6.8-zen1-1-zen status: kernel-api
    with: aoss type: oss-emulator tools: N/A
  Server-1: PipeWire v: 1.0.0 status: active with:
    1: pipewire-pulse status: active 2: wireplumber
    status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
  Device-1: Intel Ethernet I219-V vendor: ASUSTeK
    driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6
    chip-ID: 8086:15b8 class-ID: 0200
  IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full
    mac: <filter>
  Device-2: Qualcomm Atheros QCA6174 802.11ac Wireless
    Network Adapter vendor: ASUSTeK driver: ath10k_pci
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
    bus-ID: 04:00.0 chip-ID: 168c:003e class-ID: 0280
    temp: 45.0 C
  IF: wlp4s0 state: down mac: <filter>
  IF-ID-1: wgpia0 state: unknown speed: N/A duplex: N/A
    mac: N/A
  Device-1: TP-Link UB500 Adapter driver: btusb v: 0.8
    type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1
    bus-ID: 1-11:6 chip-ID: 2357:0604 class-ID: e001
    serial: <filter>
  Report: btmgmt ID: hci0 rfk-id: 0 state: up
    address: <filter> bt-v: 5.1 lmp-v: 10 status:
    discoverable: no pairing: no class-ID: 7c0104
  Hardware-1: Intel SATA Controller [RAID mode]
    driver: ahci v: 3.0 port: f020 bus-ID: 00:17.0
    chip-ID: 8086:2822 rev: class-ID: 0104
  Local Storage: total: 2.05 TiB used: 1.57 TiB (76.8%)
  SMART Message: Unable to run smartctl. Root
    privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Seagate
    model: ST2000DM001-1ER164 size: 1.82 TiB block-size:
    physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 7200 serial: <filter> fw-rev: CC26
    scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung
    model: SSD 850 EVO 250GB size: 232.89 GiB block-size:
    physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 2B6Q scheme: GPT
  ID-1: / raw-size: 232.59 GiB size: 232.59 GiB (100.00%)
    used: 197.21 GiB (84.8%) fs: btrfs dev: /dev/sdb2
    maj-min: 8:18
  ID-2: /boot/efi raw-size: 300 MiB
    size: 299.4 MiB (99.80%) used: 588 KiB (0.2%) fs: vfat
    dev: /dev/sdb1 maj-min: 8:17
  ID-3: /home raw-size: 232.59 GiB
    size: 232.59 GiB (100.00%) used: 197.21 GiB (84.8%)
    fs: btrfs dev: /dev/sdb2 maj-min: 8:18
  ID-4: /var/log raw-size: 232.59 GiB
    size: 232.59 GiB (100.00%) used: 197.21 GiB (84.8%)
    fs: btrfs dev: /dev/sdb2 maj-min: 8:18
  ID-5: /var/tmp raw-size: 232.59 GiB
    size: 232.59 GiB (100.00%) used: 197.21 GiB (84.8%)
    fs: btrfs dev: /dev/sdb2 maj-min: 8:18
  Kernel: swappiness: 133 (default 60)
    cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 31.28 GiB
    used: 0 KiB (0.0%) priority: 100 comp: zstd
    avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 8
    dev: /dev/zram0
  System Temperatures: cpu: 48.0 C mobo: N/A gpu: nvidia
    temp: 50 C
  Fan Speeds (rpm): N/A gpu: nvidia fan: 0%
  Processes: 358 Uptime: 1h 21m wakeups: 0 Memory:
  total: 32 GiB available: 31.28 GiB used: 9.2 GiB (29.4%)
  Init: systemd v: 255 default: graphical tool: systemctl
  Compilers: gcc: 13.2.1 clang: 16.0.6 Packages: 2030
  pm: pacman pkgs: 2024 libs: 561 tools: octopi,paru
  pm: flatpak pkgs: 6 Shell: fish v: 3.6.4 default: Bash
  v: 5.2.21 running-in: alacritty inxi: 3.3.31
Garuda (2.6.22-1):
  System install date:     2023-11-27
  Last full system update: 2023-12-27
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager mkinitcpio nvidia-dkms
  Windows dual boot:       No/Undetected
  Failed units:

EDIT: Noticed it on the other machines running Garuda in the house. All 3 are throwing this error. Was not present yesterday (12/27/23)

Thank you for all the help, I am stumped on this one!

I haven’t done that migration yet, I guess it’s a good opportunity.
For now, just two thoughts: you don’t need a full snapshot to revert this, just a copy of the alacritty.yml and alacritty.toml files; second, it says “unused” so you can just comment out those lines to silence the warning, it’s already as if they were not there.
Now I look if there’s any indication on the alacritty website/repository, why they are now ignored. But if everything otherwise works fine, you can reciprocate… just ignore them.


Nope, it’s a warning :slight_smile:

1 Like

@SGS Ah, where I am from they are used interchangeably. If it doesnt work or throws something up, its an error here. Thanks though lol.

Thank you, commenting out the ones listed in “warnings” fixed the issue. Much appreciated on the quick reply. All 3 PC’s in the house no longer showing the popups.

Have a great day, and thank you for the help!

Update: in my case, I only got a warning about dynamic_padding.
For some reason the migration put it at the beginning of alacritty.toml, while it’s supposed to be under the [window] section.
Likely, because that is where I used to have it in the .yml (right or wrong, I don’t know).
Moving the line at its appropriate place makes it work again (it’s a bit subtle: when the window size is not a multiple of the character size, with dynamic_padding the content is centered otherwise it’s flushed top-left).
I did not get the other warnings though.
I also found a brief, up to date Alacritty configuration guide that mentions a few of them: An Example and Concise Guide to Alacritty Configuration through TOML | convoluted
for instance, decorations_theme_variant, though it picks the correct light/dark variant without it.


This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.