[GH-ISSUE #1000] what am I doing wrong? nothing displays. #7334

New issue

Closed

opened 2026-05-23 02:53:56 +01:00 by JakeStanger · 4 comments

JakeStanger commented

2026-05-23 02:53:56 +01:00

Owner

Originally created by @xircon on GitHub (May 20, 2025).
Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/1000

Installed from aur on EndeavourOS, running hyprland, randomly selected an example:

https://github.com/JakeStanger/ironbar/discussions/864

But also tried the linked to config.json

 ironbar&                                                                                             21:22:42
  ~/.config/ironbar ❯ 2025-05-20T20:22:50.480337Z  INFO ironbar: 137: Ironbar version 0.16.1                               21:22:42
2025-05-20T20:22:50.480356Z  INFO ironbar: 138: Starting application
  ~/.config/ironbar ❯ 2025-05-20T20:22:50.943863Z  WARN ironbar::ipc::server: 33: Socket already exists. Did Ironbar exit abruptly?
2025-05-20T20:22:50.943888Z  WARN ironbar::ipc::server: 34: Attempting IPC shutdown to allow binding to address
2025-05-20T20:22:50.943966Z  INFO ironbar::ipc::server: 39: Starting IPC on /run/user/1000/ironbar-ipc.sock
2025-05-20T20:22:50.944047Z  WARN GTK: 116: [Gtk] Theme parsing error: style.css:5:17: Not using units is deprecated. Assuming 'px'.
2025-05-20T20:22:50.944124Z  WARN GTK: 116: [Gtk] Theme parsing error: style.css:73:25: Not using units is deprecated. Assuming 'px'.
2025-05-20T20:22:50.944160Z  WARN GTK: 116: [Gtk] Theme parsing error: style.css:90:26: Not using units is deprecated. Assuming 'px'.
2025-05-20T20:22:50.944179Z  WARN GTK: 116: [Gtk] Theme parsing error: style.css:96:25: Not using units is deprecated. Assuming 'px'.
2025-05-20T20:22:50.944197Z  WARN GTK: 116: [Gtk] Theme parsing error: style.css:100:25: Not using units is deprecated. Assuming 'px'.
2025-05-20T20:22:50.944219Z  WARN GTK: 116: [Gtk] Theme parsing error: style.css:111:25: Not using units is deprecated. Assuming 'px'.
2025-05-20T20:22:50.944236Z  WARN GTK: 116: [Gtk] Theme parsing error: style.css:119:25: Not using units is deprecated. Assuming 'px'.
2025-05-20T20:22:50.944254Z  WARN GTK: 116: [Gtk] Theme parsing error: style.css:126:17: Not using units is deprecated. Assuming 'px'.
2025-05-20T20:22:50.944277Z  WARN GTK: 116: [Gtk] Theme parsing error: style.css:131:26: Not using units is deprecated. Assuming 'px'.
2025-05-20T20:22:50.944487Z  WARN GTK: 116: [Gtk] Theme parsing error: style.css:337:19: Not using units is deprecated. Assuming 'px'.
2025-05-20T20:22:50.944513Z  WARN GTK: 116: [Gtk] Theme parsing error: style.css:338:20: Not using units is deprecated. Assuming 'px'.

So it is seeing the ~/.config/ironbar/style.css, but nothing displays.

Originally created by @xircon on GitHub (May 20, 2025). Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/1000 Installed from aur on EndeavourOS, running hyprland, randomly selected an example: https://github.com/JakeStanger/ironbar/discussions/864 But also tried the linked to config.json ``` ironbar& 21:22:42   ~/.config/ironbar ❯ 2025-05-20T20:22:50.480337Z INFO ironbar: 137: Ironbar version 0.16.1 21:22:42 2025-05-20T20:22:50.480356Z INFO ironbar: 138: Starting application   ~/.config/ironbar ❯ 2025-05-20T20:22:50.943863Z WARN ironbar::ipc::server: 33: Socket already exists. Did Ironbar exit abruptly? 2025-05-20T20:22:50.943888Z WARN ironbar::ipc::server: 34: Attempting IPC shutdown to allow binding to address 2025-05-20T20:22:50.943966Z INFO ironbar::ipc::server: 39: Starting IPC on /run/user/1000/ironbar-ipc.sock 2025-05-20T20:22:50.944047Z WARN GTK: 116: [Gtk] Theme parsing error: style.css:5:17: Not using units is deprecated. Assuming 'px'. 2025-05-20T20:22:50.944124Z WARN GTK: 116: [Gtk] Theme parsing error: style.css:73:25: Not using units is deprecated. Assuming 'px'. 2025-05-20T20:22:50.944160Z WARN GTK: 116: [Gtk] Theme parsing error: style.css:90:26: Not using units is deprecated. Assuming 'px'. 2025-05-20T20:22:50.944179Z WARN GTK: 116: [Gtk] Theme parsing error: style.css:96:25: Not using units is deprecated. Assuming 'px'. 2025-05-20T20:22:50.944197Z WARN GTK: 116: [Gtk] Theme parsing error: style.css:100:25: Not using units is deprecated. Assuming 'px'. 2025-05-20T20:22:50.944219Z WARN GTK: 116: [Gtk] Theme parsing error: style.css:111:25: Not using units is deprecated. Assuming 'px'. 2025-05-20T20:22:50.944236Z WARN GTK: 116: [Gtk] Theme parsing error: style.css:119:25: Not using units is deprecated. Assuming 'px'. 2025-05-20T20:22:50.944254Z WARN GTK: 116: [Gtk] Theme parsing error: style.css:126:17: Not using units is deprecated. Assuming 'px'. 2025-05-20T20:22:50.944277Z WARN GTK: 116: [Gtk] Theme parsing error: style.css:131:26: Not using units is deprecated. Assuming 'px'. 2025-05-20T20:22:50.944487Z WARN GTK: 116: [Gtk] Theme parsing error: style.css:337:19: Not using units is deprecated. Assuming 'px'. 2025-05-20T20:22:50.944513Z WARN GTK: 116: [Gtk] Theme parsing error: style.css:338:20: Not using units is deprecated. Assuming 'px'. ``` So it is seeing the ~/.config/ironbar/style.css, but nothing displays.

JakeStanger

2026-05-23 02:53:56 +01:00

closed this issue
added the
T:Question
label

JakeStanger commented

2026-05-23 02:53:57 +01:00

Author

Owner

@JakeStanger commented on GitHub (May 20, 2025):

Issue 1000, wow!

It looks like Ironbar isn't trying to create any bars, which would indicate a configuration issue related to monitors.

The linked example in the discussion is set up for specific monitor names. You'll likely need to change those to match your own for anything to display.

As for the "linked" JSON, I'm not sure what you mean exactly. Could you either link to or provide that file in full please?

@JakeStanger commented on GitHub (May 20, 2025): Issue 1000, wow! It looks like Ironbar isn't trying to create any bars, which would indicate a configuration issue related to monitors. The linked example in the discussion is set up for specific monitor names. You'll likely need to change those to match your own for anything to display. As for the "linked" JSON, I'm not sure what you mean exactly. Could you either link to or provide that file in full please?

JakeStanger commented

2026-05-23 02:53:57 +01:00

Author

Owner

@xircon commented on GitHub (May 20, 2025):

https://github.com/JakeStanger/ironbar/blob/master/examples/config.json

My monitor is eDP-1 (laptop), the config.corn contains:

in {
   monitors.eDP-1 = {
       position = "top"
       height = 30
       icon_theme = "oomox-srcery-mthsrnn"
       start = $left
       center = $center
       end = $right
   }

   monitors.HDMI-A-1 = {
       position = "bottom"
       height = 30
       center = [ $lyrics ]
   }
}

Thanks for the quick reply (I will try not to be 1001!)

@xircon commented on GitHub (May 20, 2025): https://github.com/JakeStanger/ironbar/blob/master/examples/config.json My monitor is eDP-1 (laptop), the config.corn contains: ``` in { monitors.eDP-1 = { position = "top" height = 30 icon_theme = "oomox-srcery-mthsrnn" start = $left center = $center end = $right } monitors.HDMI-A-1 = { position = "bottom" height = 30 center = [ $lyrics ] } } ``` Thanks for the quick reply (I will try not to be 1001!)

JakeStanger commented

2026-05-23 02:53:57 +01:00

Author

Owner

@JakeStanger commented on GitHub (May 20, 2025):

Okay strange. The example JSON should just show the same bar across all screens no problem. Your config.corn should work as well.

Let's try a really basic example and see what happens. Try using the following config.corn and nothing more:

{
  end = [ { type = "clock" } ]
}

You can either use IRONBAR_CONFIG to provide a full path to the file, or ensure the config.corn exists in your config directory and no other config files (excluding CSS). It will attempt to load JSON, YAML, TOML, Corn in that order.

Then launch Ironbar from the terminal with IRONBAR_LOG=trace, and please share the output (ensure all previous instances are terminated)

@JakeStanger commented on GitHub (May 20, 2025): Okay strange. The example JSON should just show the same bar across all screens no problem. Your `config.corn` should work as well. Let's try a really basic example and see what happens. Try using the following config.corn and nothing more: ```corn { end = [ { type = "clock" } ] } ``` You can either use `IRONBAR_CONFIG` to provide a full path to the file, or ensure the `config.corn` exists in your config directory and no other config files (excluding CSS). It will attempt to load JSON, YAML, TOML, Corn in that order. Then launch Ironbar from the terminal with `IRONBAR_LOG=trace`, and please share the output (ensure all previous instances are terminated)

JakeStanger commented

2026-05-23 02:53:57 +01:00

Author

Owner

@xircon commented on GitHub (May 20, 2025):

That works!

@xircon commented on GitHub (May 20, 2025): That works!