[GH-ISSUE #18] Run without sway #5641

New issue

Closed

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

JakeStanger commented 2026-05-23 01:52:10 +01:00

Owner

Copy link

Originally created by @yavko on GitHub (Sep 23, 2022).
Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/18

It would be nice if the bar could run without the features that require sway if it isn't present, also for workspaces to use the standardized wlr_ext_workspace_unstable_v1 protocol. I would love to try this bar, but I run Hyprland and not sway.

But I'm willing to add support for Hyprland as a pr in the future, and it wouldn't be too hard as I have developed a crate to communicate with Hyprland.

Originally created by @yavko on GitHub (Sep 23, 2022). Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/18 It would be nice if the bar could run without the features that require sway if it isn't present, also for workspaces to use the standardized `wlr_ext_workspace_unstable_v1` protocol. I would love to try this bar, but I run Hyprland and not sway. > But I'm willing to add support for Hyprland as a pr in the future, and it wouldn't be too hard as I have developed a crate to communicate with Hyprland.

JakeStanger closed this issue 2026-05-23 01:52:10 +01:00

JakeStanger commented 2026-05-23 01:52:11 +01:00

Author

Owner

Copy link

@JakeStanger commented on GitHub (Sep 23, 2022):

Hey, thanks for the interest! I'd definitely like to make the bar independent from Sway. The biggest roadblock for me at the moment is I'm not too familiar with Wayland or wlroots under the hood (Sway's IPC server proved the easy option).

The bar relies on Sway's IPC server in these places currently:

• On startup, to get output names. This is used to parse multi-monitor config options and for the Workspaces module
• In the workspaces module, to subscribe to workspace events
• In the launcher and focused modules, to subscribe to window events

The first one is the biggest hurdle. If I can get output names in a stable/reliable way that (ideally) doesn't vary between compositors, the bar can at least run under different compositors.

The workspaces can probably be ported to wlr_ext_workspace_unstable_v1 as you say, although I'll need to find out more about that.

The other two modules I've no idea currently - if you've any knowledge on how I could get window events agnostically let me know!

---

But I'm willing to add support for Hyprland as a pr in the future, and it wouldn't be too hard as I have developed a crate to communicate with Hyprland.

I've got quite a large refactor I'm finishing up at the moment so I'd recommend holding off for now, but I'm definitely interested in knowing more about this!

<!-- gh-comment-id:1256537020 --> @JakeStanger commented on GitHub (Sep 23, 2022): Hey, thanks for the interest! I'd definitely like to make the bar independent from Sway. The biggest roadblock for me at the moment is I'm not too familiar with Wayland or wlroots under the hood (Sway's IPC server proved the easy option). The bar relies on Sway's IPC server in these places currently: - On startup, to get output names. This is used to parse multi-monitor config options and for the Workspaces module - In the workspaces module, to subscribe to workspace events - In the launcher and focused modules, to subscribe to window events The first one is the biggest hurdle. If I can get output names in a stable/reliable way that (ideally) doesn't vary between compositors, the bar can at least run under different compositors. The workspaces can probably be ported to `wlr_ext_workspace_unstable_v1` as you say, although I'll need to find out more about that. The other two modules I've no idea currently - if you've any knowledge on how I could get window events agnostically let me know! --- > But I'm willing to add support for Hyprland as a pr in the future, and it wouldn't be too hard as I have developed a crate to communicate with Hyprland. I've got quite a large refactor I'm finishing up at the moment so I'd recommend holding off for now, but I'm definitely interested in knowing more about this!

JakeStanger commented 2026-05-23 01:52:11 +01:00

Author

Owner

Copy link

@yavko commented on GitHub (Sep 24, 2022):

I'll try to find suitable protocols, but i know the outputs can definitely done with a wlr ext protocol, for the window events i think there might have been one though ill have to do more research

<!-- gh-comment-id:1256809564 --> @yavko commented on GitHub (Sep 24, 2022): I'll try to find suitable protocols, but i know the outputs can definitely done with a wlr ext protocol, for the window events i think there might have been one though ill have to do more research

JakeStanger commented 2026-05-23 01:52:11 +01:00

Author

Owner

Copy link

@yavko commented on GitHub (Sep 24, 2022):

I've got quite a large refactor I'm finishing up at the moment so I'd recommend holding off for now, but I'm definitely interested in knowing more about this!

Sounds good!

<!-- gh-comment-id:1256809875 --> @yavko commented on GitHub (Sep 24, 2022): > I've got quite a large refactor I'm finishing up at the moment so I'd recommend holding off for now, but I'm definitely interested in knowing more about this! Sounds good!

JakeStanger commented 2026-05-23 01:52:11 +01:00

Author

Owner

Copy link

@yavko commented on GitHub (Sep 25, 2022):

For outputs the https://wayland.app/protocols/wlr-output-management-unstable-v1 protocol can be used!

<!-- gh-comment-id:1257097111 --> @yavko commented on GitHub (Sep 25, 2022): For outputs the https://wayland.app/protocols/wlr-output-management-unstable-v1 protocol can be used!

JakeStanger commented 2026-05-23 01:52:11 +01:00

Author

Owner

Copy link

@yavko commented on GitHub (Sep 25, 2022):

And https://wayland.app/protocols/wlr-foreign-toplevel-management-unstable-v1 for window events!

<!-- gh-comment-id:1257097338 --> @yavko commented on GitHub (Sep 25, 2022): And https://wayland.app/protocols/wlr-foreign-toplevel-management-unstable-v1 for window events!

JakeStanger commented 2026-05-23 01:52:11 +01:00

Author

Owner

Copy link

@yavko commented on GitHub (Sep 25, 2022):

Found a crate that provides bindings to wlr specific wayland protocols https://crates.io/crates/wayland-protocols-wlr (which uses wayland-scanner), though it may be better just to use wayland-rs' wayland-scanner and wayland-rs

<!-- gh-comment-id:1257098616 --> @yavko commented on GitHub (Sep 25, 2022): Found a crate that provides bindings to wlr specific wayland protocols https://crates.io/crates/wayland-protocols-wlr (which uses wayland-scanner), though it may be better just to use wayland-rs' wayland-scanner and wayland-rs

JakeStanger commented 2026-05-23 01:52:11 +01:00

Author

Owner

Copy link

@JakeStanger commented on GitHub (Sep 25, 2022):

Awesome thanks for these! Getting output names through Wayland doesn't look too tricky, so I should be able to get the bar running outside Sway pretty quickly. I'll tackle the others after as I suspect those will need a bit more work

<!-- gh-comment-id:1257171294 --> @JakeStanger commented on GitHub (Sep 25, 2022): Awesome thanks for these! Getting output names through Wayland doesn't look too tricky, so I should be able to get the bar running outside Sway pretty quickly. I'll tackle the others after as I suspect those will need a bit more work

JakeStanger commented 2026-05-23 01:52:11 +01:00

Author

Owner

Copy link

@JakeStanger commented on GitHub (Sep 26, 2022):

First step! I've got a bit of tidying/testing to do before it gets pushed up, but I've got the bar running in Hyprland:

Monitor names and ordering look to line up with what Sway reports so that's great, and all modules except focused/launcher/workspaces should work straight away.

The animations even work for the popup which I guess makes sense, but is very cool to see!

<!-- gh-comment-id:1258672740 --> @JakeStanger commented on GitHub (Sep 26, 2022): First step! I've got a bit of tidying/testing to do before it gets pushed up, but I've got the bar running in Hyprland:   Monitor names and ordering look to line up with what Sway reports so that's great, and all modules except focused/launcher/workspaces should work straight away. The animations even work for the popup which I guess makes sense, but is very cool to see!

JakeStanger commented 2026-05-23 01:52:11 +01:00

Author

Owner

Copy link

@yavko commented on GitHub (Sep 26, 2022):

Great progress! Can't wait for full support!

<!-- gh-comment-id:1258736383 --> @yavko commented on GitHub (Sep 26, 2022): Great progress! Can't wait for full support!

JakeStanger commented 2026-05-23 01:52:11 +01:00

Author

Owner

Copy link

@JakeStanger commented on GitHub (Sep 28, 2022):

Quick update. I've managed to get as far with the toplevel management as to get a list of windows out so just need to figure out properly listening to events, which is the hard bit.

Unfortunately it looks like the workspace protocol hasn't actually been merged into wlroots or sway yet so I won't be able to port that off the Sway IPC server. If the aforementioned Hyprland crate can handle that we can look at abstracting the calls behind a trait & being able to pick between the Sway/Hyprland/whatever else clients.

<!-- gh-comment-id:1261482255 --> @JakeStanger commented on GitHub (Sep 28, 2022): Quick update. I've managed to get as far with the toplevel management as to get a list of windows out so just need to figure out properly listening to events, which is the hard bit. Unfortunately it looks like the workspace protocol [hasn't actually been merged](https://gitlab.freedesktop.org/wlroots/wlroots/-/merge_requests/2357) into wlroots or sway yet so I won't be able to port that off the Sway IPC server. If the aforementioned Hyprland crate can handle that we can look at abstracting the calls behind a trait & being able to pick between the Sway/Hyprland/whatever else clients.

JakeStanger commented 2026-05-23 01:52:11 +01:00

Author

Owner

Copy link

@yavko commented on GitHub (Sep 28, 2022):

I think the way it should be done is to create a unix socket, and then it can receive events from it. For example someone can write a shell script that uses socat to listen to their wm, and then use socat to write to ironbar, so its wm independant.

<!-- gh-comment-id:1261538889 --> @yavko commented on GitHub (Sep 28, 2022): I think the way it should be done is to create a unix socket, and then it can receive events from it. For example someone can write a shell script that uses socat to listen to their wm, and then use socat to write to ironbar, so its wm independant.

JakeStanger commented 2026-05-23 01:52:11 +01:00

Author

Owner

Copy link

@JakeStanger commented on GitHub (Sep 28, 2022):

That's a clever idea and I'm all for that, but I think that should be added in the long-term as a fallback option. If I can feasibly add native support that means users don't need to set up a second process, which is definitely preferable (I'd rather the bar was batteries included).

If anybody on an unsupported compositor then wants to use the bar, they could then write a script.

<!-- gh-comment-id:1261551799 --> @JakeStanger commented on GitHub (Sep 28, 2022): That's a clever idea and I'm all for that, but I think that should be added in the long-term as a fallback option. If I can feasibly add native support that means users don't need to set up a second process, which is definitely preferable (I'd rather the bar was batteries included). If anybody on an unsupported compositor then wants to use the bar, they could then write a script.

JakeStanger commented 2026-05-23 01:52:12 +01:00

Author

Owner

Copy link

@yavko commented on GitHub (Sep 28, 2022):

Yeah thats how it should be done!

<!-- gh-comment-id:1261565013 --> @yavko commented on GitHub (Sep 28, 2022): Yeah thats how it should be done!

JakeStanger commented 2026-05-23 01:52:12 +01:00

Author

Owner

Copy link

@JakeStanger commented on GitHub (Oct 4, 2022):

I've just pushed a big update on the feat/wayland-protocols branch that integrates wlr-foreign-toplevel-management-unstable-v1 and ports the focused module over to it.

It seems to work in both Sway and Hyprland for me, but could you build it and see if it works for you too please?

<!-- gh-comment-id:1267664319 --> @JakeStanger commented on GitHub (Oct 4, 2022): I've just pushed a big update on the `feat/wayland-protocols` branch that integrates `wlr-foreign-toplevel-management-unstable-v1` and ports the `focused` module over to it. It seems to work in both Sway and Hyprland for me, but could you build it and see if it works for you too please? 

JakeStanger commented 2026-05-23 01:52:12 +01:00

Author

Owner

Copy link

@yavko commented on GitHub (Oct 5, 2022):

Doesn't open

Details

2022-10-05T03:18:28.107317Z  INFO ironbar: Ironbar version 0.5.2
2022-10-05T03:18:28.107336Z  INFO ironbar: Starting application
2022-10-05T03:18:28.192483Z  INFO ironbar: Creating bar on 'eDP-1'
The application panicked (crashed).
Message:  internal error: entered unreachable code
Location: /home/yavor/.cargo/git/checkouts/swayipc-rs-8bf762d2a36edf0b/6464c41/async/src/socket.rs:19

  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
                                ⋮ 7 frames hidden ⋮                               
   8: core::panicking::panic::hbe0e36c7510ee8e3
      at /rustc/060e47f74a91b28c3db28d80a6a9d6841ca51026/library/core/src/panicking.rs:48
   9: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll::h05919756fef3461f
      at <unknown source file>:<unknown line>
  10: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll::h4987e99dd62068a7
      at <unknown source file>:<unknown line>
  11: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll::hf31b4c41a592f1e8
      at <unknown source file>:<unknown line>
  12: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll::h7da629fd7657bb3d
      at <unknown source file>:<unknown line>
  13: std::thread::local::LocalKey<T>::with::h41d1f7ba92474673
      at <unknown source file>:<unknown line>
  14: tokio::park::thread::CachedParkThread::block_on::h9d696311f351feff
      at <unknown source file>:<unknown line>
  15: tokio::runtime::handle::Handle::block_on::h08591b114eab6b5d
      at <unknown source file>:<unknown line>
  16: tokio::runtime::enter::exit::h94fd083791e0bdce
      at <unknown source file>:<unknown line>
  17: tokio::runtime::scheduler::multi_thread::worker::block_in_place::hb3e5015292147077
      at <unknown source file>:<unknown line>
  18: <ironbar::modules::workspaces::WorkspacesModule as ironbar::modules::Module<gtk::auto::box_::Box>>::spawn_controller::hc99723603e4e8cb9
      at <unknown source file>:<unknown line>
  19: ironbar::bar::add_modules::hce6abb4336c8e147
      at <unknown source file>:<unknown line>
  20: ironbar::bar::create_bar::h8f4116077ad20c08
      at <unknown source file>:<unknown line>
  21: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll::h226fe8e8312e4b75
      at <unknown source file>:<unknown line>
  22: std::thread::local::LocalKey<T>::with::h9192df796939cc66
      at <unknown source file>:<unknown line>
  23: tokio::park::thread::CachedParkThread::block_on::hb1d4ea8b0205ef49
      at <unknown source file>:<unknown line>
  24: tokio::runtime::handle::Handle::block_on::h20203de41fc3dea0
      at <unknown source file>:<unknown line>
  25: tokio::runtime::enter::exit::h61e669521ce6f409
      at <unknown source file>:<unknown line>
  26: tokio::runtime::scheduler::multi_thread::worker::block_in_place::h5632fbba6c484958
      at <unknown source file>:<unknown line>
  27: <O as gio::auto::application::ApplicationExt>::connect_activate::activate_trampoline::ha6554fc4c3946ece
      at <unknown source file>:<unknown line>
  28: g_closure_invoke<unknown>
      at <unknown source file>:<unknown line>
  29: g_signal_emit_valist<unknown>
      at <unknown source file>:<unknown line>
  30: g_signal_emit<unknown>
      at <unknown source file>:<unknown line>
  31: g_application_run<unknown>
      at <unknown source file>:<unknown line>
  32: <O as gio::application::ApplicationExtManual>::run_with_args::h331634c7871cb578
      at <unknown source file>:<unknown line>
  33: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll::h40cf4dbf09a0680d
      at <unknown source file>:<unknown line>
  34: std::thread::local::LocalKey<T>::with::h8575ab078cb14c73
      at <unknown source file>:<unknown line>
  35: tokio::park::thread::CachedParkThread::block_on::h76a1d49c024562f8
      at <unknown source file>:<unknown line>
  36: tokio::runtime::scheduler::multi_thread::MultiThread::block_on::hc865733a62c9d202
      at <unknown source file>:<unknown line>
  37: tokio::runtime::Runtime::block_on::h4509df460ce7e0e1
      at <unknown source file>:<unknown line>
  38: ironbar::main::ha7f6c29b79275860
      at <unknown source file>:<unknown line>
  39: std::sys_common::backtrace::__rust_begin_short_backtrace::ha6f017eed1811fac
      at <unknown source file>:<unknown line>
  40: std::rt::lang_start::{{closure}}::h9b65f9fe3470925a
      at <unknown source file>:<unknown line>
  41: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::hed7373fa9659f259
      at /rustc/060e47f74a91b28c3db28d80a6a9d6841ca51026/library/core/src/ops/function.rs:280
  42: std::panicking::try::do_call::h60869ea5a827d812
      at /rustc/060e47f74a91b28c3db28d80a6a9d6841ca51026/library/std/src/panicking.rs:492
  43: std::panicking::try::he306a2f2634a9efa
      at /rustc/060e47f74a91b28c3db28d80a6a9d6841ca51026/library/std/src/panicking.rs:456
  44: std::panic::catch_unwind::hd1d792c621528cfe
      at /rustc/060e47f74a91b28c3db28d80a6a9d6841ca51026/library/std/src/panic.rs:137
  45: std::rt::lang_start_internal::{{closure}}::h30ae6a495b5c3af9
      at /rustc/060e47f74a91b28c3db28d80a6a9d6841ca51026/library/std/src/rt.rs:128
  46: std::panicking::try::do_call::h6f1b5a7cf2085723
      at /rustc/060e47f74a91b28c3db28d80a6a9d6841ca51026/library/std/src/panicking.rs:492
  47: std::panicking::try::haed14f11242573f1
      at /rustc/060e47f74a91b28c3db28d80a6a9d6841ca51026/library/std/src/panicking.rs:456
  48: std::panic::catch_unwind::he2604d2aa152a0fc
      at /rustc/060e47f74a91b28c3db28d80a6a9d6841ca51026/library/std/src/panic.rs:137
  49: std::rt::lang_start_internal::h8856a10dcbd75374
      at /rustc/060e47f74a91b28c3db28d80a6a9d6841ca51026/library/std/src/rt.rs:128
  50: main<unknown>
      at <unknown source file>:<unknown line>
  51: __libc_start_main<unknown>
      at <unknown source file>:<unknown line>
  52: _start<unknown>
      at /build/glibc/src/glibc/csu/../sysdeps/x86_64/start.S:115

Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.

<!-- gh-comment-id:1267872555 --> @yavko commented on GitHub (Oct 5, 2022): Doesn't open <details> <summary>Details</summary> ``` 2022-10-05T03:18:28.107317Z INFO ironbar: Ironbar version 0.5.2 2022-10-05T03:18:28.107336Z INFO ironbar: Starting application 2022-10-05T03:18:28.192483Z INFO ironbar: Creating bar on 'eDP-1' The application panicked (crashed). Message: internal error: entered unreachable code Location: /home/yavor/.cargo/git/checkouts/swayipc-rs-8bf762d2a36edf0b/6464c41/async/src/socket.rs:19 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ⋮ 7 frames hidden ⋮ 8: core::panicking::panic::hbe0e36c7510ee8e3 at /rustc/060e47f74a91b28c3db28d80a6a9d6841ca51026/library/core/src/panicking.rs:48 9: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll::h05919756fef3461f at <unknown source file>:<unknown line> 10: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll::h4987e99dd62068a7 at <unknown source file>:<unknown line> 11: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll::hf31b4c41a592f1e8 at <unknown source file>:<unknown line> 12: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll::h7da629fd7657bb3d at <unknown source file>:<unknown line> 13: std::thread::local::LocalKey<T>::with::h41d1f7ba92474673 at <unknown source file>:<unknown line> 14: tokio::park::thread::CachedParkThread::block_on::h9d696311f351feff at <unknown source file>:<unknown line> 15: tokio::runtime::handle::Handle::block_on::h08591b114eab6b5d at <unknown source file>:<unknown line> 16: tokio::runtime::enter::exit::h94fd083791e0bdce at <unknown source file>:<unknown line> 17: tokio::runtime::scheduler::multi_thread::worker::block_in_place::hb3e5015292147077 at <unknown source file>:<unknown line> 18: <ironbar::modules::workspaces::WorkspacesModule as ironbar::modules::Module<gtk::auto::box_::Box>>::spawn_controller::hc99723603e4e8cb9 at <unknown source file>:<unknown line> 19: ironbar::bar::add_modules::hce6abb4336c8e147 at <unknown source file>:<unknown line> 20: ironbar::bar::create_bar::h8f4116077ad20c08 at <unknown source file>:<unknown line> 21: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll::h226fe8e8312e4b75 at <unknown source file>:<unknown line> 22: std::thread::local::LocalKey<T>::with::h9192df796939cc66 at <unknown source file>:<unknown line> 23: tokio::park::thread::CachedParkThread::block_on::hb1d4ea8b0205ef49 at <unknown source file>:<unknown line> 24: tokio::runtime::handle::Handle::block_on::h20203de41fc3dea0 at <unknown source file>:<unknown line> 25: tokio::runtime::enter::exit::h61e669521ce6f409 at <unknown source file>:<unknown line> 26: tokio::runtime::scheduler::multi_thread::worker::block_in_place::h5632fbba6c484958 at <unknown source file>:<unknown line> 27: <O as gio::auto::application::ApplicationExt>::connect_activate::activate_trampoline::ha6554fc4c3946ece at <unknown source file>:<unknown line> 28: g_closure_invoke<unknown> at <unknown source file>:<unknown line> 29: g_signal_emit_valist<unknown> at <unknown source file>:<unknown line> 30: g_signal_emit<unknown> at <unknown source file>:<unknown line> 31: g_application_run<unknown> at <unknown source file>:<unknown line> 32: <O as gio::application::ApplicationExtManual>::run_with_args::h331634c7871cb578 at <unknown source file>:<unknown line> 33: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll::h40cf4dbf09a0680d at <unknown source file>:<unknown line> 34: std::thread::local::LocalKey<T>::with::h8575ab078cb14c73 at <unknown source file>:<unknown line> 35: tokio::park::thread::CachedParkThread::block_on::h76a1d49c024562f8 at <unknown source file>:<unknown line> 36: tokio::runtime::scheduler::multi_thread::MultiThread::block_on::hc865733a62c9d202 at <unknown source file>:<unknown line> 37: tokio::runtime::Runtime::block_on::h4509df460ce7e0e1 at <unknown source file>:<unknown line> 38: ironbar::main::ha7f6c29b79275860 at <unknown source file>:<unknown line> 39: std::sys_common::backtrace::__rust_begin_short_backtrace::ha6f017eed1811fac at <unknown source file>:<unknown line> 40: std::rt::lang_start::{{closure}}::h9b65f9fe3470925a at <unknown source file>:<unknown line> 41: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::hed7373fa9659f259 at /rustc/060e47f74a91b28c3db28d80a6a9d6841ca51026/library/core/src/ops/function.rs:280 42: std::panicking::try::do_call::h60869ea5a827d812 at /rustc/060e47f74a91b28c3db28d80a6a9d6841ca51026/library/std/src/panicking.rs:492 43: std::panicking::try::he306a2f2634a9efa at /rustc/060e47f74a91b28c3db28d80a6a9d6841ca51026/library/std/src/panicking.rs:456 44: std::panic::catch_unwind::hd1d792c621528cfe at /rustc/060e47f74a91b28c3db28d80a6a9d6841ca51026/library/std/src/panic.rs:137 45: std::rt::lang_start_internal::{{closure}}::h30ae6a495b5c3af9 at /rustc/060e47f74a91b28c3db28d80a6a9d6841ca51026/library/std/src/rt.rs:128 46: std::panicking::try::do_call::h6f1b5a7cf2085723 at /rustc/060e47f74a91b28c3db28d80a6a9d6841ca51026/library/std/src/panicking.rs:492 47: std::panicking::try::haed14f11242573f1 at /rustc/060e47f74a91b28c3db28d80a6a9d6841ca51026/library/std/src/panicking.rs:456 48: std::panic::catch_unwind::he2604d2aa152a0fc at /rustc/060e47f74a91b28c3db28d80a6a9d6841ca51026/library/std/src/panic.rs:137 49: std::rt::lang_start_internal::h8856a10dcbd75374 at /rustc/060e47f74a91b28c3db28d80a6a9d6841ca51026/library/std/src/rt.rs:128 50: main<unknown> at <unknown source file>:<unknown line> 51: __libc_start_main<unknown> at <unknown source file>:<unknown line> 52: _start<unknown> at /build/glibc/src/glibc/csu/../sysdeps/x86_64/start.S:115 Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering. ``` </details>

JakeStanger commented 2026-05-23 01:52:12 +01:00

Author

Owner

Copy link

@JakeStanger commented on GitHub (Oct 5, 2022):

Thanks for trying. I can see in the backtrace it's trying to load the workspaces module which is still sway-only (as is the launcher module). Can you check your config and test again please?

If you get focused working I will work on porting the other two.

<!-- gh-comment-id:1268074789 --> @JakeStanger commented on GitHub (Oct 5, 2022): Thanks for trying. I can see in the backtrace it's trying to load the `workspaces` module which is still sway-only (as is the `launcher` module). Can you check your config and test again please? If you get `focused` working I will work on porting the other two.

JakeStanger commented 2026-05-23 01:52:12 +01:00

Author

Owner

Copy link

@yavko commented on GitHub (Oct 5, 2022):

Strange i removed it from my config

<!-- gh-comment-id:1268085258 --> @yavko commented on GitHub (Oct 5, 2022): Strange i removed it from my config

JakeStanger commented 2026-05-23 01:52:12 +01:00

Author

Owner

Copy link

@JakeStanger commented on GitHub (Oct 5, 2022):

If that's the case could you please share:

• The contents of your config directory
• The contents config file you believe is being loaded

I can then try and investigate what's going on. At the moment I've got nothing to go on.

<!-- gh-comment-id:1268098472 --> @JakeStanger commented on GitHub (Oct 5, 2022): If that's the case could you please share: - The contents of your config directory - The contents config file you believe is being loaded I can then try and investigate what's going on. At the moment I've got nothing to go on.

JakeStanger commented 2026-05-23 01:52:12 +01:00

Author

Owner

Copy link

@JakeStanger commented on GitHub (Oct 10, 2022):

I've ported over the launcher module, although there's some glaring room for optimisation at the moment, which I'll look at before next release.

<!-- gh-comment-id:1273834830 --> @JakeStanger commented on GitHub (Oct 10, 2022): I've ported over the `launcher` module, although there's some glaring room for optimisation at the moment, which I'll look at before next release.

JakeStanger commented 2026-05-23 01:52:12 +01:00

Author

Owner

Copy link

@heisfer commented on GitHub (Oct 11, 2022):

Seems like launcher, focus, sysinfo, clock and tray is working on hyprland. (upper is waybar and little bit below is ironbar)

<!-- gh-comment-id:1274884292 --> @heisfer commented on GitHub (Oct 11, 2022):  Seems like launcher, focus, sysinfo, clock and tray is working on hyprland. (upper is waybar and little bit below is ironbar)

JakeStanger commented 2026-05-23 01:52:12 +01:00

Author

Owner

Copy link

@heisfer commented on GitHub (Oct 11, 2022):

At first for me too new update didn't work (sway ipc error) but for some reason git didn't pull new updates (I checked if I was in a right branch). but after deleting and re downloading it worked so..

<!-- gh-comment-id:1274887313 --> @heisfer commented on GitHub (Oct 11, 2022): At first for me too new update didn't work (sway ipc error) but for some reason git didn't pull new updates (I checked if I was in a right branch). but after deleting and re downloading it worked so..

JakeStanger commented 2026-05-23 01:52:12 +01:00

Author

Owner

Copy link

@JakeStanger commented on GitHub (Oct 14, 2022):

I'm going to merge the changes into master as-is as I think they're ready, but I'm holding off the workspaces module until the linked hyperland-rs bug is resolved.

<!-- gh-comment-id:1279476683 --> @JakeStanger commented on GitHub (Oct 14, 2022): I'm going to merge the changes into master as-is as I think they're ready, but I'm holding off the `workspaces` module until the linked `hyperland-rs` bug is resolved.

JakeStanger commented 2026-05-23 01:52:12 +01:00

Author

Owner

Copy link

@yavko commented on GitHub (Oct 15, 2022):

👍

<!-- gh-comment-id:1279609596 --> @yavko commented on GitHub (Oct 15, 2022): 👍

JakeStanger commented 2026-05-23 01:52:12 +01:00

Author

Owner

Copy link

@yavko commented on GitHub (Jan 3, 2023):

I'm going to merge the changes into master as-is as I think they're ready, but I'm holding off the workspaces module until the linked hyperland-rs bug is resolved.

The Hyprland-rs bug was fixed, I can publish a alpha release if you'd prefer to use a release instead of master, as atm I'm still polishing it for a full major release, tho API has mostly stabilized

<!-- gh-comment-id:1369360733 --> @yavko commented on GitHub (Jan 3, 2023): > I'm going to merge the changes into master as-is as I think they're ready, but I'm holding off the `workspaces` module until the linked `hyperland-rs` bug is resolved. The `Hyprland-rs` bug was fixed, I can publish a alpha release if you'd prefer to use a release instead of master, as atm I'm still polishing it for a full major release, tho API has mostly stabilized

JakeStanger commented 2026-05-23 01:52:12 +01:00

Author

Owner

Copy link

@JakeStanger commented on GitHub (Jan 3, 2023):

Awesome! I won't be able to get a release out until there's a Hyperland-rs release since crates.io doesn't let you publish git/path deps. I can start working on support and get that pushed up to its own branch/master soon though

<!-- gh-comment-id:1370337687 --> @JakeStanger commented on GitHub (Jan 3, 2023): Awesome! I won't be able to get a release out until there's a Hyperland-rs release since crates.io doesn't let you publish git/path deps. I can start working on support and get that pushed up to its own branch/master soon though

JakeStanger commented 2026-05-23 01:52:13 +01:00

Author

Owner

Copy link

@yavko commented on GitHub (Jan 6, 2023):

Ah, I'll work on getting a release out once im back home. Thanks for telling me!

<!-- gh-comment-id:1373203739 --> @yavko commented on GitHub (Jan 6, 2023): Ah, I'll work on getting a release out once im back home. Thanks for telling me!

JakeStanger commented 2026-05-23 01:52:13 +01:00

Author

Owner

Copy link

@yavko commented on GitHub (Jan 17, 2023):

Awesome! I won't be able to get a release out until there's a Hyperland-rs release since crates.io doesn't let you publish git/path deps. I can start working on support and get that pushed up to its own branch/master soon though

I've release an alpha release, its now on crates.io as well! https://github.com/hyprland-community/hyprland-rs/releases/tag/0.3.0-alpha.0

<!-- gh-comment-id:1384699105 --> @yavko commented on GitHub (Jan 17, 2023): > Awesome! I won't be able to get a release out until there's a Hyperland-rs release since crates.io doesn't let you publish git/path deps. I can start working on support and get that pushed up to its own branch/master soon though I've release an alpha release, its now on crates.io as well! https://github.com/hyprland-community/hyprland-rs/releases/tag/0.3.0-alpha.0

JakeStanger commented 2026-05-23 01:52:13 +01:00

Author

Owner

Copy link

@JakeStanger commented on GitHub (Jan 27, 2023):

PR finally pushed!

No configuration should be needed to get it working. If anybody on Hyprland can give it a go and double-check it all works (I've only tested inside a Hyprland session nested in Sway with the default config) please let me know how it goes.

It also comes with some general improvements to the workspaces module.

<!-- gh-comment-id:1407025612 --> @JakeStanger commented on GitHub (Jan 27, 2023): PR finally pushed! No configuration should be needed to get it working. If anybody on Hyprland can give it a go and double-check it all works (I've only tested inside a Hyprland session nested in Sway with the default config) please let me know how it goes. It also comes with some general improvements to the workspaces module.

JakeStanger commented 2026-05-23 01:52:13 +01:00

Author

Owner

Copy link

@yavko commented on GitHub (Jan 28, 2023):

I know you just merged this, but I released a full release of Hyprland-rs like 10 mins ago 💀
https://github.com/hyprland-community/hyprland-rs/releases/tag/0.3.0

<!-- gh-comment-id:1407285302 --> @yavko commented on GitHub (Jan 28, 2023): I know you just merged this, but I released a full release of Hyprland-rs like 10 mins ago 💀 https://github.com/hyprland-community/hyprland-rs/releases/tag/0.3.0

JakeStanger commented 2026-05-23 01:52:13 +01:00

Author

Owner

Copy link

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

That's cool, I've got a few other deps to update so I'll just add it to the list

<!-- gh-comment-id:1407396289 --> @JakeStanger commented on GitHub (Jan 28, 2023): That's cool, I've got a few other deps to update so I'll just add it to the list

JakeStanger commented 2026-05-23 01:52:13 +01:00

Author

Owner

Copy link

@yffengdong commented on GitHub (Apr 7, 2023):

I tested in wayfire, it support now except workspace
archlinux

<!-- gh-comment-id:1499941620 --> @yffengdong commented on GitHub (Apr 7, 2023): I tested in wayfire, it support now except workspace archlinux

JakeStanger commented 2026-05-23 01:52:13 +01:00

Author

Owner

Copy link

@yavko commented on GitHub (Apr 7, 2023):

I tested in wayfire, it support now except workspace archlinux

Wayfire doesn't have IPC does it?

<!-- gh-comment-id:1499941969 --> @yavko commented on GitHub (Apr 7, 2023): > I tested in wayfire, it support now except workspace archlinux Wayfire doesn't have IPC does it?

JakeStanger commented 2026-05-23 01:52:13 +01:00

Author

Owner

Copy link

@yffengdong commented on GitHub (Apr 7, 2023):

I tested in wayfire, it support now except workspace archlinux

Wayfire doesn't have IPC does it?

Doesn't have, and they may use dbus
about workspace, for now use api, may support workspace protocol after
https://github.com/WayfireWM/wayfire/issues/49#issuecomment-650819625

<!-- gh-comment-id:1499944656 --> @yffengdong commented on GitHub (Apr 7, 2023): > > I tested in wayfire, it support now except workspace archlinux > > Wayfire doesn't have IPC does it? Doesn't have, and they may use dbus about workspace, for now use api, may support workspace protocol after https://github.com/WayfireWM/wayfire/issues/49#issuecomment-650819625

JakeStanger commented 2026-05-23 01:52:13 +01:00

Author

Owner

Copy link

@yavko commented on GitHub (Apr 7, 2023):

I tested in wayfire, it support now except workspace archlinux

Wayfire doesn't have IPC does it?

Doesn't have, and they may use dbus WayfireWM/wayfire#49

Yeah, so support can't be added, unless wayfire also supports the unfinished workspaces protocol, which would also require support for it to be added here.

<!-- gh-comment-id:1499947895 --> @yavko commented on GitHub (Apr 7, 2023): > > > I tested in wayfire, it support now except workspace archlinux > > > > > > Wayfire doesn't have IPC does it? > > Doesn't have, and they may use dbus [WayfireWM/wayfire#49](https://github.com/WayfireWM/wayfire/issues/49) Yeah, so support can't be added, unless wayfire also supports the unfinished workspaces protocol, which would also require support for it to be added here.

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

master

update_flake_lock_action

docs/starlight

fix/brightness-scroll

feat/log-commit

fix/tray-icon

refactor/clippy

fix/volume-defaults

fix/default-profiles

fix/volume-crash2

fix/sink-input-names

feat/ext-workspaces

refactor/tracing-subscriber

fix/menu-popup

feat/hot-reload

feat/thresholds

feat/image-inspector

refactor/miette

feat/launcher-previews

v0.19.0

v0.18.0

v0.17.1

v0.17.0

v0.16.1

v0.16.0

v0.15.1

v0.15.0

v0.14.1

v0.14.0

v0.13.0

v0.12.1

v0.12.0

v0.11.0

v0.10.0

v0.9.0

v0.8.0

v0.7.0

v0.6.0

v0.5.2

v0.5.1

v0.5.0

v0.4.0

v0.3.0

v0.2.0

v0.1.0

Labels

Clear labels   

A:Build

  

A:CI

  

A:Client

  

A:Config

  

A:Core

  

A:Documentation

  

A:Documentation

  

A:IPC

  

A:Testing

  

A:UX/UI

  

blocked

  

BREAKING CHANGE

  

duplicate

  

good first issue

  

GTK4

  

help wanted

  

invalid

  

M:Battery

  

M:Battery

  

M:Bindmode

  

M:Bluetooth

  

M:Brightness

  

M:Cairo

  

M:Clipboard

  

M:Clock

  

M:Clock

  

M:Custom

  

M:Focused

  

M:Keyboard

  

M:Launcher

  

M:Menu

  

M:Music

  

M:Music

  

M:Music

  

M:Network Manager

  

M:Notifications

  

M:SysInfo

  

M:Tray

  

M:Volume

  

M:Workspaces

  

partially resolved

  

P:Critical

  

P:High

  

P:Low

  

P:Medium

  

pull-request

Mirrored from GitHub Pull Request

  

T:Bug

  

T:Bug

  

T:Core Enhancement

  

T:Module Enhancement

  

T:New Module

  

T:Question

  

wontfix

No labels

A:Build

A:CI

A:Client

A:Config

A:Core

A:Documentation

A:Documentation

A:IPC

A:Testing

A:UX/UI

blocked

BREAKING CHANGE

duplicate

good first issue

GTK4

help wanted

invalid

M:Battery

M:Battery

M:Bindmode

M:Bluetooth

M:Brightness

M:Cairo

M:Clipboard

M:Clock

M:Clock

M:Custom

M:Focused

M:Keyboard

M:Launcher

M:Menu

M:Music

M:Music

M:Music

M:Network Manager

M:Notifications

M:SysInfo

M:Tray

M:Volume

M:Workspaces

partially resolved

P:Critical

P:High

P:Low

P:Medium

pull-request

T:Bug

T:Bug

T:Core Enhancement

T:Module Enhancement

T:New Module

T:Question

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

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#5641

No description provided.