[GH-ISSUE #1057] Crash when workspaces enabled on unsupported compositor #5953

New issue

Closed

opened 2026-05-23 01:54:11 +01:00 by JakeStanger · 0 comments

JakeStanger commented

2026-05-23 01:54:11 +01:00

Owner

Originally created by @adamcstephens on GitHub (Jun 19, 2025).
Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/1057

Describe the bug
If workspaces are enabled then ironbar will crash on an unsupported compositor.

To reproduce
Steps to reproduce the behavior:

Enable workspaces
Start an unsupported compositor, e.g. river, and attempt to run ironbar.
Observe crash

Jun 19 12:01:18 punk ironbar[85897]: 2025-06-19T16:01:18.169984Z ERROR ironbar: 239:
Jun 19 12:01:18 punk ironbar[85897]:    0: Unsupported compositor
Jun 19 12:01:18 punk ironbar[85897]: Location:
Jun 19 12:01:18 punk ironbar[85897]:    src/clients/compositor/mod.rs:130
Jun 19 12:01:18 punk ironbar[85897]: Note: Currently workspaces are only supported by Sway, Niri and Hyprland
Jun 19 12:01:18 punk ironbar[85897]: Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.

Expected behavior

No crash, just ironbar runs without workspace support.

System information:

Distro: NixOS Unstable
Compositor: River, but I also switch with Niri
Ironbar version: 0.16.1 (will crash with Niri), and master (crashes on River)

Configuration

Config not included, but happy to provide if deemed necessary.

Config

Styles

Additional context

Filed as a bug since this is a crash, but if graceful degradation isn't a goal this could be a feature request. Being able to switch to other compositors can be desirable, but I'd love to keep using ironbar without having to reconfigure.

Screenshots

Originally created by @adamcstephens on GitHub (Jun 19, 2025). Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/1057 **Describe the bug** If workspaces are enabled then ironbar will crash on an unsupported compositor.  **To reproduce** Steps to reproduce the behavior: 1. Enable workspaces 2. Start an unsupported compositor, e.g. river, and attempt to run ironbar. 3. Observe crash ``` Jun 19 12:01:18 punk ironbar[85897]: 2025-06-19T16:01:18.169984Z ERROR ironbar: 239: Jun 19 12:01:18 punk ironbar[85897]: 0: Unsupported compositor Jun 19 12:01:18 punk ironbar[85897]: Location: Jun 19 12:01:18 punk ironbar[85897]: src/clients/compositor/mod.rs:130 Jun 19 12:01:18 punk ironbar[85897]: Note: Currently workspaces are only supported by Sway, Niri and Hyprland Jun 19 12:01:18 punk ironbar[85897]: Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it. ``` **Expected behavior**  No crash, just ironbar runs without workspace support. **System information:** - Distro: NixOS Unstable - Compositor: River, but I also switch with Niri - Ironbar version: 0.16.1 (will crash with Niri), and master (crashes on River) **Configuration**  Config not included, but happy to provide if deemed necessary. <details><summary>Config</summary> ``` ``` </details> <details><summary>Styles</summary> ```css ``` </details> **Additional context**  Filed as a bug since this is a crash, but if graceful degradation isn't a goal this could be a feature request. Being able to switch to other compositors can be desirable, but I'd love to keep using ironbar without having to reconfigure. **Screenshots**

JakeStanger

2026-05-23 01:54:11 +01:00