[GH-ISSUE #382] Crash on hyprland when use tray #2947

New issue

Closed

opened 2026-05-22 23:52:52 +01:00 by JakeStanger · 1 comment

JakeStanger commented

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

Owner

Originally created by @woshiluo on GitHub (Dec 24, 2023).
Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/382

Describe the bug

ironbar will crash immediately on hyprland if there is tray module.

To Reproduce
Steps to reproduce the behavior:

Run ironbar
and then it get crashed

2023-12-24T02:52:30.316697Z  INFO ironbar: 117: Ironbar version 0.14.0-pre
2023-12-24T02:52:30.316736Z  INFO ironbar: 118: Starting application
2023-12-24T02:52:30.368783Z  WARN ironbar::ipc::server: 31: Socket already exists. Did Ironbar exit abruptly?
2023-12-24T02:52:30.368847Z  WARN ironbar::ipc::server: 32: Attempting IPC shutdown to allow binding to address
2023-12-24T02:52:30.369008Z  INFO ironbar::ipc::server: 37: Starting IPC on /run/user/1000/ironbar-ipc.sock
2023-12-24T02:52:30.369731Z  INFO ironbar::bar: 113: Initializing bar 'bar-4' on 'eDP-1'
2023-12-24T02:52:30.371353Z ERROR ironbar::logging: 47: The application panicked (crashed).
Message:  there is no reactor running, must be called from the context of a Tokio 1.x runtime
Location: src/main.rs:373

Expected behavior

ironbar will normally started.

System information:

Distro: ArchLinux
Compositor: Hyprland(0.33.1-2)
Ironbar version: github.com/JakeStanger/ironbar@29eeefbd24

Configuration

Share your bar configuration and stylesheet as applicable:

Config

[[end]]
type = 'tray'

Styles

Empty

Screenshots

Originally created by @woshiluo on GitHub (Dec 24, 2023). Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/382 **Describe the bug** ironbar will crash immediately on hyprland if there is tray module. **To Reproduce** Steps to reproduce the behavior: 1. Run `ironbar` 2. and then it get crashed ``` 2023-12-24T02:52:30.316697Z INFO ironbar: 117: Ironbar version 0.14.0-pre 2023-12-24T02:52:30.316736Z INFO ironbar: 118: Starting application 2023-12-24T02:52:30.368783Z WARN ironbar::ipc::server: 31: Socket already exists. Did Ironbar exit abruptly? 2023-12-24T02:52:30.368847Z WARN ironbar::ipc::server: 32: Attempting IPC shutdown to allow binding to address 2023-12-24T02:52:30.369008Z INFO ironbar::ipc::server: 37: Starting IPC on /run/user/1000/ironbar-ipc.sock 2023-12-24T02:52:30.369731Z INFO ironbar::bar: 113: Initializing bar 'bar-4' on 'eDP-1' 2023-12-24T02:52:30.371353Z ERROR ironbar::logging: 47: The application panicked (crashed). Message: there is no reactor running, must be called from the context of a Tokio 1.x runtime Location: src/main.rs:373 ``` **Expected behavior** ironbar will normally started. **System information:** - Distro: ArchLinux - Compositor: Hyprland(0.33.1-2) - Ironbar version: https://github.com/JakeStanger/ironbar/commit/29eeefbd24a7741db48889ba951bc7992edcd7ad **Configuration** > Share your bar configuration and stylesheet as applicable: <details><summary>Config</summary> ``` [[end]] type = 'tray' ``` </details> <details><summary>Styles</summary> ```css Empty ``` </details> **Screenshots** ![image](https://github.com/JakeStanger/ironbar/assets/29979060/9aa7bdb7-49df-4901-8dda-7f29fd10c372)

JakeStanger closed this issue

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

JakeStanger commented

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

Author

Owner

@JakeStanger commented on GitHub (Dec 24, 2023):

Thanks for reporting. Looks like I missed a spot when refactoring for the GTK/GLib update recently, should have the fix merged in a few mins.

@JakeStanger commented on GitHub (Dec 24, 2023): Thanks for reporting. Looks like I missed a spot when refactoring for the GTK/GLib update recently, should have the fix merged in a few mins.