JakeStanger/ironbar

Fork 0

mirror of https://github.com/JakeStanger/ironbar.git synced 2026-07-11 08:15:21 +01:00

[GH-ISSUE #168] Failed to register: Timeout was reached #4302

New issue

Closed

opened 2026-05-23 00:52:34 +01:00 by JakeStanger · 5 comments

JakeStanger commented

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

Owner

Originally created by @TheSunCat on GitHub (May 28, 2023).
Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/168

Describe the bug
Ironbar does not start

To Reproduce
Steps to reproduce the behavior:

Run ironbar
Observe it not starting

Expected behavior
ironbar starts

System information:

Distro: Arch Linux
Compositor: Hyprland
Ironbar version: v0.12.0.r36.ge036ff0-1

Configuration

Share your bar configuration and stylesheet as applicable:

Config

let {

}
in {

}

Additional context
This started happening today. Ironbar has not been updated since yesterday when it was running fine.

Logs

[apm@apg ~]$ ironbar                                                                                     
2023-05-28T11:27:14.209791Z  INFO ironbar: 49: Ironbar version 0.12.1
2023-05-28T11:27:14.209804Z  INFO ironbar: 50: Starting application
Failed to register: Timeout was reached
2023-05-28T11:27:39.233424Z  INFO ironbar: 120: Shutting down

Originally created by @TheSunCat on GitHub (May 28, 2023). Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/168 **Describe the bug** Ironbar does not start **To Reproduce** Steps to reproduce the behavior: 1. Run ironbar 2. Observe it not starting **Expected behavior** ironbar starts **System information:** - Distro: Arch Linux - Compositor: Hyprland - Ironbar version: v0.12.0.r36.ge036ff0-1 **Configuration** > Share your bar configuration and stylesheet as applicable: <details><summary>Config</summary> ``` let { } in { } ``` </details> **Additional context** This started happening today. Ironbar has not been updated since yesterday when it was running fine. **Logs** ```ini [apm@apg ~]$ ironbar 2023-05-28T11:27:14.209791Z INFO ironbar: 49: Ironbar version 0.12.1 2023-05-28T11:27:14.209804Z INFO ironbar: 50: Starting application Failed to register: Timeout was reached 2023-05-28T11:27:39.233424Z INFO ironbar: 120: Shutting down ```

JakeStanger

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

closed this issue
added the
T:Bug
label

JakeStanger commented

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

Author

Owner

@TheSunCat commented on GitHub (May 28, 2023):

aaaand it's gone after a reboot. Not closing this yet in case the issue returns.

@TheSunCat commented on GitHub (May 28, 2023): aaaand it's gone after a reboot. Not closing this yet in case the issue returns.

JakeStanger commented

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

Author

Owner

@JakeStanger commented on GitHub (May 28, 2023):

From a google it looks like this might be a rare GTK thing caused by another running instance. Doing pkill ironbar before restarting it, or rebooting, should consistently fix this.

@JakeStanger commented on GitHub (May 28, 2023): From a google it looks like this might be a rare GTK thing caused by another running instance. Doing `pkill ironbar` before restarting it, or rebooting, should consistently fix this.

JakeStanger commented

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

Author

Owner

@JakeStanger commented on GitHub (Jun 18, 2023):

Going to close this assuming it hasn't happened since. If you run into it again, let me know and I'll re-open.

@JakeStanger commented on GitHub (Jun 18, 2023): Going to close this assuming it hasn't happened since. If you run into it again, let me know and I'll re-open.

JakeStanger commented

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

Author

Owner

@yavko commented on GitHub (Jun 18, 2023):

I think I've had this before too, but it disappeared after a reboot

@yavko commented on GitHub (Jun 18, 2023): I think I've had this before too, but it disappeared after a reboot

JakeStanger commented

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

Author

Owner

@JakeStanger commented on GitHub (Jun 18, 2023):

Interesting, good to know.

I'll keep this closed for now since it still seems to point more to a weird rare GTK/compositor issue than anything else and there's a known fix.

@JakeStanger commented on GitHub (Jun 18, 2023): Interesting, good to know. I'll keep this closed for now since it still seems to point more to a weird rare GTK/compositor issue than anything else and there's a known fix.