[GH-ISSUE #293] Example config.corn does not start #5740

New issue

Closed

opened 2026-05-23 01:52:47 +01:00 by JakeStanger · 2 comments

JakeStanger commented

2026-05-23 01:52:47 +01:00

Owner

Originally created by @MarcusE1W on GitHub (Aug 30, 2023).
Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/293

Describe the bug

A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

install ironbar on ArchlinuxARM: cargo install ironbar
copy config.corn from repository to ~/.config/ironbar
run ironbar

Expected behavior
The example config starts like with the othe config files (toml, yaml, json)

what actually happens:

Ironbar starts with default config and these messages:

2023-08-30T16:06:00.550003Z  INFO ironbar: 92: Ironbar version 0.13.0
2023-08-30T16:06:00.550101Z  INFO ironbar: 93: Starting application
2023-08-30T16:06:00.729009Z  INFO ironbar::ipc::server: 43: Starting IPC on /run/user/1000/ironbar-ipc.sock
2023-08-30T16:06:00.729659Z ERROR ironbar: 176: Failed to load config: failed to resolve referenced input
2023-08-30T16:06:00.729734Z  WARN ironbar: 177: Falling back to the default config
2023-08-30T16:06:00.729758Z  INFO ironbar: 178: If this is your first time using Ironbar, you should create a config in ~/.config/ironbar/
2023-08-30T16:06:00.729769Z  INFO ironbar: 179: More info here: https://github.com/JakeStanger/ironbar/wiki/configuration-guide
2023-08-30T16:06:00.730099Z  INFO ironbar: 231: Creating bar on 'eDP-1'
2023-08-30T16:06:00.732452Z  INFO ironbar::bar: 33: Creating bar bar-5
^C2023-08-30T16:13:52.936957Z  INFO ironbar: 142: Shutting down

(The other config files work ok)

System information:

Distro: ManjaroARM
Compositor: [Hyprland 0.28]
Ironbar version: [0.13]

Originally created by @MarcusE1W on GitHub (Aug 30, 2023). Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/293 **Describe the bug** > A clear and concise description of what the bug is. **To Reproduce** Steps to reproduce the behavior: 1. install ironbar on ArchlinuxARM: cargo install ironbar 2. copy config.corn from repository to ~/.config/ironbar 3. run ironbar **Expected behavior** The example config starts like with the othe config files (toml, yaml, json) **what actually happens:** Ironbar starts with default config and these messages: ``` 2023-08-30T16:06:00.550003Z INFO ironbar: 92: Ironbar version 0.13.0 2023-08-30T16:06:00.550101Z INFO ironbar: 93: Starting application 2023-08-30T16:06:00.729009Z INFO ironbar::ipc::server: 43: Starting IPC on /run/user/1000/ironbar-ipc.sock 2023-08-30T16:06:00.729659Z ERROR ironbar: 176: Failed to load config: failed to resolve referenced input 2023-08-30T16:06:00.729734Z WARN ironbar: 177: Falling back to the default config 2023-08-30T16:06:00.729758Z INFO ironbar: 178: If this is your first time using Ironbar, you should create a config in ~/.config/ironbar/ 2023-08-30T16:06:00.729769Z INFO ironbar: 179: More info here: https://github.com/JakeStanger/ironbar/wiki/configuration-guide 2023-08-30T16:06:00.730099Z INFO ironbar: 231: Creating bar on 'eDP-1' 2023-08-30T16:06:00.732452Z INFO ironbar::bar: 33: Creating bar bar-5 ^C2023-08-30T16:13:52.936957Z INFO ironbar: 142: Shutting down ``` (The other config files work ok) **System information:** - Distro: ManjaroARM - Compositor: [Hyprland 0.28] - Ironbar version: [0.13]

JakeStanger

2026-05-23 01:52:47 +01:00

closed this issue
added the
T:Bug
label

JakeStanger commented

2026-05-23 01:52:48 +01:00

Author

Owner

@JakeStanger commented on GitHub (Aug 30, 2023):

Looks like this has come about due to an issue in the new(ish) string interpolation feature in Corn, which I've logged here https://github.com/JakeStanger/corn/issues/21.

In the meantime, I've just pushed an update to master with a patched example.corn and an updated Corn build that will return more helpful errors, so you'll now get the input name it can't resolve.

@JakeStanger commented on GitHub (Aug 30, 2023): Looks like this has come about due to an issue in the new(ish) string interpolation feature in Corn, which I've logged here https://github.com/JakeStanger/corn/issues/21. In the meantime, I've just pushed an update to master with a patched `example.corn` and an updated Corn build that will return more helpful errors, so you'll now get the input name it can't resolve.

JakeStanger commented

2026-05-23 01:52:48 +01:00

Author

Owner

@MarcusE1W commented on GitHub (Aug 31, 2023):

Works now, thanks :-)

@MarcusE1W commented on GitHub (Aug 31, 2023): Works now, thanks :-)