[GH-ISSUE #960] Taking screenshots on Hyprland with grimblast crashes the workspaces module #4510

New issue

Closed

opened 2026-05-23 00:53:59 +01:00 by JakeStanger · 3 comments

JakeStanger commented

2026-05-23 00:53:59 +01:00

Owner

Originally created by @Funtimes909 on GitHub (May 8, 2025).
Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/960

Describe the bug
Taking screenshots with grimblast on hyprland crashes* ironbar

*The bar stays open and continues working as expected except the workspaces module freezes completely and stops registering new workspaces or workspace changes

To Reproduce
Steps to reproduce the behavior:

Open Hyprland
Start ironbar
run grimblast with this command "grimblast --cursor copysave active ${LOCATION}"

Expected behavior
Taking screenshots should not crash the workspaces module

System information:

Distro: Arch Linux
Compositor: Hyprland
Ironbar version: 0.16.1 (Also happens on versions compiled from source)

Configuration
All my bar configurations are in my dotfiles repo here

Additional context
This problem occurs on both latest stable release and compiled from source

Screenshots

Log output when it crashes

Originally created by @Funtimes909 on GitHub (May 8, 2025). Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/960 **Describe the bug** Taking screenshots with grimblast on hyprland crashes* ironbar *The bar stays open and continues working as expected except the workspaces module freezes completely and stops registering new workspaces or workspace changes **To Reproduce** Steps to reproduce the behavior: 1. Open Hyprland 2. Start ironbar 3. run grimblast with this command "grimblast --cursor copysave active ${LOCATION}" **Expected behavior** Taking screenshots should not crash the workspaces module **System information:** - Distro: Arch Linux - Compositor: Hyprland - Ironbar version: 0.16.1 (Also happens on versions compiled from source) **Configuration** All my bar configurations are in my dotfiles repo [here](https://git.funtimes909.xyz/Funtimes909/dotfiles/src/branch/main/ironbar) **Additional context** This problem occurs on both latest stable release and compiled from source **Screenshots** ![Image](https://github.com/user-attachments/assets/bbfb59ee-8d26-4c3e-bf5b-3975617870e2) Log output when it crashes

JakeStanger

2026-05-23 00:53:59 +01:00

closed this issue
added the
M:Workspaces

P:High

A:Client

T:Bug
labels

JakeStanger commented

2026-05-23 00:53:59 +01:00

Author

Owner

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

Thanks for reporting. The actual error looks like an upstream issue with the hyprland-rs crate to me, although Ironbar shouldn't crash due to that.

@JakeStanger commented on GitHub (May 8, 2025): Thanks for reporting. The actual error looks like an upstream issue with the hyprland-rs crate to me, although Ironbar shouldn't crash due to that.

JakeStanger commented

2026-05-23 00:53:59 +01:00

Author

Owner

@Funtimes909 commented on GitHub (May 9, 2025):

Shall I report this upstream to hyprland-rs as well then? Thanks for your response

@Funtimes909 commented on GitHub (May 9, 2025): Shall I report this upstream to hyprland-rs as well then? Thanks for your response

JakeStanger commented

2026-05-23 00:53:59 +01:00

Author

Owner

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

Yes I think so, I'd use RUST_BACKTRACE=1 to get more detail as to where exactly inside the crate it's crashing, but the library should never error handling a response from the Hyprland IPC.

I'd hold off until I get a patch in place first though. I'm going to update the Hyprland crate as well as prevent it from crashing under the same error. The crate update may include a fix.

@JakeStanger commented on GitHub (May 16, 2025): Yes I think so, I'd use `RUST_BACKTRACE=1` to get more detail as to where exactly inside the crate it's crashing, but the library should never error handling a response from the Hyprland IPC. I'd hold off until I get a patch in place first though. I'm going to update the Hyprland crate as well as prevent it from crashing under the same error. The crate update may include a fix.