[GH-ISSUE #538] adding volume sections fails loading config.toml #4393

Closed
opened 2026-05-23 00:53:01 +01:00 by JakeStanger · 6 comments
Owner

Originally created by @zimbipw on GitHub (Apr 11, 2024).
Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/538

When adding volume section the config isn't loaded.

Steps to reproduce the behavior:
add this section to config.toml

[[start]]                             
type = "volume"                       
format = "{icon} {percentage}% {name}"                                                    
                                     
[[start.icons]]                       
volume_high = ""                     
volume_medium = ""                   
volume_low = ""                      
muted = ""  

restart ironbar

2024-04-11T16:23:15.822518Z ERROR ironbar: 280: Failed to load config: TOML parse error at line 1, column 1
  |
1 | anchor_to_edges = true
  | ^^^^^^^^^^^^^^^^^^^^^^
invalid type: map, expected a string

2024-04-11T16:23:15.822568Z  WARN ironbar: 281: Falling back to the default config
2024-04-11T16:23:15.822578Z  INFO ironbar: 282: If this is your first time using Ironbar, you should create a config in ~/.config/ironbar/
2024-04-11T16:23:15.822584Z  INFO ironbar: 283: More info here: https://github.com/JakeStanger/ironbar/wiki/configuration-guide
2024-04-11T16:23:15.822598Z  INFO ironbar: 111: Ironbar version 0.15.0-pre
2024-04-11T16:23:15.822606Z  INFO ironbar: 112: Starting application
2024-04-11T16:23:15.859120Z  INFO ironbar::ipc::server: 37: Starting IPC on /run/user/1000/ironbar-ipc.sock
2024-04-11T16:23:15.860241Z  INFO ironbar::bar: 118: Initializing bar 'bar-8' on 'eDP-1'

Expected behavior
ironbar should start normal showing volume icon

System information:

  • Distro: Arch Linux
  • Compositor: Hyprland
  • Ironbar version: v0.14.1.r145.gedf20b6
Originally created by @zimbipw on GitHub (Apr 11, 2024). Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/538 When adding volume section the config isn't loaded. Steps to reproduce the behavior: add this section to config.toml ```toml [[start]] type = "volume" format = "{icon} {percentage}% {name}" [[start.icons]] volume_high = "" volume_medium = "" volume_low = "" muted = "" ``` restart ironbar ``` 2024-04-11T16:23:15.822518Z ERROR ironbar: 280: Failed to load config: TOML parse error at line 1, column 1 | 1 | anchor_to_edges = true | ^^^^^^^^^^^^^^^^^^^^^^ invalid type: map, expected a string 2024-04-11T16:23:15.822568Z WARN ironbar: 281: Falling back to the default config 2024-04-11T16:23:15.822578Z INFO ironbar: 282: If this is your first time using Ironbar, you should create a config in ~/.config/ironbar/ 2024-04-11T16:23:15.822584Z INFO ironbar: 283: More info here: https://github.com/JakeStanger/ironbar/wiki/configuration-guide 2024-04-11T16:23:15.822598Z INFO ironbar: 111: Ironbar version 0.15.0-pre 2024-04-11T16:23:15.822606Z INFO ironbar: 112: Starting application 2024-04-11T16:23:15.859120Z INFO ironbar::ipc::server: 37: Starting IPC on /run/user/1000/ironbar-ipc.sock 2024-04-11T16:23:15.860241Z INFO ironbar::bar: 118: Initializing bar 'bar-8' on 'eDP-1' ``` **Expected behavior** ironbar should start normal showing volume icon **System information:** - Distro: Arch Linux - Compositor: Hyprland - Ironbar version: v0.14.1.r145.gedf20b6
JakeStanger 2026-05-23 00:53:01 +01:00
  • closed this issue
  • added the
    T:Bug
    label
Author
Owner

@JakeStanger commented on GitHub (Apr 11, 2024):

The error suggests your config is invalid, and has nothing to do with the volume module. Please share the full config and I can help.

Please also in future use code blocks for formatting to keep things tidy & readable, cheers.

<!-- gh-comment-id:2050450853 --> @JakeStanger commented on GitHub (Apr 11, 2024): The error suggests your config is invalid, and has nothing to do with the volume module. Please share the full config and I can help. Please also in future use code blocks for formatting to keep things tidy & readable, cheers.
Author
Owner

@JakeStanger commented on GitHub (Apr 17, 2024):

@zimbipw do you still need help with this?

<!-- gh-comment-id:2062359964 --> @JakeStanger commented on GitHub (Apr 17, 2024): @zimbipw do you still need help with this?
Author
Owner

@bobblkabb commented on GitHub (Apr 21, 2024):

Same here. Using example config

2024-04-21T16:09:16.662310Z ERROR ironbar: Failed to load config: TOML parse error at line 43, column 8
   |
43 | type = "volume"
   |        ^^^^^^^^
unknown variant `volume`, expected one of `clipboard`, `clock`, `custom`, `focused`, `label`, `launcher`, `music`, `script`, `sys_info`, `tray`, `upower`, `workspaces`

2024-04-21T16:09:16.662370Z WARN ironbar: Falling back to the default config

openSUSE Tumbleweed, niri 0.15, ironbar 0.14

<!-- gh-comment-id:2068122124 --> @bobblkabb commented on GitHub (Apr 21, 2024): Same here. Using [example config](https://github.com/JakeStanger/ironbar/blob/master/examples/config.toml) ``` 2024-04-21T16:09:16.662310Z ERROR ironbar: Failed to load config: TOML parse error at line 43, column 8 | 43 | type = "volume" | ^^^^^^^^ unknown variant `volume`, expected one of `clipboard`, `clock`, `custom`, `focused`, `label`, `launcher`, `music`, `script`, `sys_info`, `tray`, `upower`, `workspaces` ``` 2024-04-21T16:09:16.662370Z WARN ironbar: Falling back to the default config openSUSE Tumbleweed, niri 0.15, ironbar 0.14
Author
Owner

@JakeStanger commented on GitHub (Apr 21, 2024):

The volume module is currently only available on the git build(0.15.0-pre). I'm targeting a point release in the next week or two.

<!-- gh-comment-id:2068141141 --> @JakeStanger commented on GitHub (Apr 21, 2024): The volume module is currently only available on the git build(0.15.0-pre). I'm targeting a point release in the next week or two.
Author
Owner

@bobblkabb commented on GitHub (Apr 22, 2024):

Good to know, thank you.

<!-- gh-comment-id:2068868382 --> @bobblkabb commented on GitHub (Apr 22, 2024): Good to know, thank you.
Author
Owner

@JakeStanger commented on GitHub (Apr 24, 2024):

I found there were issues with several TOML examples off the back of #555, including with the volume one. These have been resolved, so I am considering this fixed.

If this is not the case, please let me know.

<!-- gh-comment-id:2075819979 --> @JakeStanger commented on GitHub (Apr 24, 2024): I found there were issues with several TOML examples off the back of #555, including with the volume one. These have been resolved, so I am considering this fixed. If this is not the case, please let me know.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
JakeStanger/ironbar#4393
No description provided.