JakeStanger/ironbar

Fork 0

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

[GH-ISSUE #1400] Closing bars causes crash #3233

New issue

Open

opened 2026-05-22 23:54:57 +01:00 by JakeStanger · 6 comments

JakeStanger commented

2026-05-22 23:54:57 +01:00

Owner

Originally created by @ildar on GitHub (Feb 24, 2026).
Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/1400

Describe the bug
Ironbar stops in two cases where it did not in 0.17.1

To reproduce
Steps to reproduce the behavior:

run ironbar reload
ironbar stops

Another scenario:

run ironbar
unplug a screen where one bar was placed
ironbar stops

Expected behavior
keep running

System information:

Distro: ALTLinux p11
Compositor: Pinnacle
Ironbar version: 0.18.0

Configuration

Config

``` monitors: eDP-1: - name: "top-panel" ... HDMI-A-2: - name: "HDMI-panel" ... ```

Additional context
It did not happen on 0.17.1
log:

2026-02-24T11:33:24.259971Z  INFO ironbar::clients::outputs: 74: Monitor HDMI-A-2 disconnected
2026-02-24T11:33:24.265938Z  INFO GTK: 109: [Gdk] MESSAGE: Lost connection to Wayland compositor.

Originally created by @ildar on GitHub (Feb 24, 2026). Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/1400 **Describe the bug** Ironbar stops in two cases where it did not in 0.17.1 **To reproduce** Steps to reproduce the behavior: 1. run `ironbar reload` 2. ironbar stops Another scenario: 1. run ironbar 2. unplug a screen where one bar was placed 3. ironbar stops **Expected behavior** keep running **System information:** - Distro: ALTLinux p11 - Compositor: Pinnacle - Ironbar version: 0.18.0 **Configuration** <details><summary>Config</summary> ``` monitors: eDP-1: - name: "top-panel" ... HDMI-A-2: - name: "HDMI-panel" ... ``` </details> **Additional context** It did not happen on 0.17.1 log: ``` 2026-02-24T11:33:24.259971Z INFO ironbar::clients::outputs: 74: Monitor HDMI-A-2 disconnected 2026-02-24T11:33:24.265938Z INFO GTK: 109: [Gdk] MESSAGE: Lost connection to Wayland compositor. ```

JakeStanger added the

A:Core

T:Bug

P:Critical

labels

2026-05-22 23:54:57 +01:00

JakeStanger commented

2026-05-22 23:54:57 +01:00

Author

Owner

@ildar commented on GitHub (Feb 24, 2026):

logs for ironbar reload:

2026-02-24T19:57:33.050080Z  INFO ironbar::ipc::server: 137: Closing existing bars
2026-02-24T19:57:33.059262Z  INFO ironbar::bar: 125: Initializing bar 'top-panel' on 'eDP-1'
2026-02-24T19:57:33.069386Z  WARN GTK: 108: [Gdk] vkGetPhysicalDeviceSurfaceFormatsKHR(): A surface is no longer available. (VK_ERROR_SURFACE_LOST_KHR) (-1000000000)
2026-02-24T19:57:33.069445Z  WARN GTK: 108: [Gdk] vkGetPhysicalDeviceSurfaceFormatsKHR(): A surface is no longer available. (VK_ERROR_SURFACE_LOST_KHR) (-1000000000)
2026-02-24T19:57:33.074093Z  WARN GTK: 108: [Gdk] vkGetPhysicalDeviceSurfaceCapabilitiesKHR(): A surface is no longer available. (VK_ERROR_SURFACE_LOST_KHR) (-1000000000)
2026-02-24T19:57:33.078000Z  WARN GTK: 108: [Gdk] vkGetPhysicalDeviceSurfaceFormatsKHR(): A surface is no longer available. (VK_ERROR_SURFACE_LOST_KHR) (-1000000000)
2026-02-24T19:57:33.078051Z  WARN GTK: 108: [Gdk] vkGetPhysicalDeviceSurfaceFormatsKHR(): A surface is no longer available. (VK_ERROR_SURFACE_LOST_KHR) (-1000000000)
2026-02-24T19:57:33.078621Z  WARN GTK: 108: [Gdk] vkGetPhysicalDeviceSurfaceCapabilitiesKHR(): A surface is no longer available. (VK_ERROR_SURFACE_LOST_KHR) (-1000000000)
2026-02-24T19:57:33.103766Z  INFO GTK: 109: [Gdk] MESSAGE: Error flushing display: Соединение разорвано другой стороной

@ildar commented on GitHub (Feb 24, 2026): logs for `ironbar reload`: ``` 2026-02-24T19:57:33.050080Z INFO ironbar::ipc::server: 137: Closing existing bars 2026-02-24T19:57:33.059262Z INFO ironbar::bar: 125: Initializing bar 'top-panel' on 'eDP-1' 2026-02-24T19:57:33.069386Z WARN GTK: 108: [Gdk] vkGetPhysicalDeviceSurfaceFormatsKHR(): A surface is no longer available. (VK_ERROR_SURFACE_LOST_KHR) (-1000000000) 2026-02-24T19:57:33.069445Z WARN GTK: 108: [Gdk] vkGetPhysicalDeviceSurfaceFormatsKHR(): A surface is no longer available. (VK_ERROR_SURFACE_LOST_KHR) (-1000000000) 2026-02-24T19:57:33.074093Z WARN GTK: 108: [Gdk] vkGetPhysicalDeviceSurfaceCapabilitiesKHR(): A surface is no longer available. (VK_ERROR_SURFACE_LOST_KHR) (-1000000000) 2026-02-24T19:57:33.078000Z WARN GTK: 108: [Gdk] vkGetPhysicalDeviceSurfaceFormatsKHR(): A surface is no longer available. (VK_ERROR_SURFACE_LOST_KHR) (-1000000000) 2026-02-24T19:57:33.078051Z WARN GTK: 108: [Gdk] vkGetPhysicalDeviceSurfaceFormatsKHR(): A surface is no longer available. (VK_ERROR_SURFACE_LOST_KHR) (-1000000000) 2026-02-24T19:57:33.078621Z WARN GTK: 108: [Gdk] vkGetPhysicalDeviceSurfaceCapabilitiesKHR(): A surface is no longer available. (VK_ERROR_SURFACE_LOST_KHR) (-1000000000) 2026-02-24T19:57:33.103766Z INFO GTK: 109: [Gdk] MESSAGE: Error flushing display: Соединение разорвано другой стороной ```

JakeStanger commented

2026-05-22 23:54:57 +01:00

Author

Owner

@JakeStanger commented on GitHub (Feb 24, 2026):

I'll leave this open in case anybody else hits it and has any extra info, but I'm fairly sure this isn't anything Ironbar is doing (all I do is ask GTK to close & open some windows, and hook the new windows into layer-shell).

I believe this is a problem with one of the lower-level components - either the GTK Vulkan renderer, the compositor or GPU drivers.

Alternatively it might be fixed on -git and I may have forgotten - could you try building the repo from source and see if it still occurs please?

@JakeStanger commented on GitHub (Feb 24, 2026): I'll leave this open in case anybody else hits it and has any extra info, but I'm fairly sure this isn't anything Ironbar is doing (all I do is ask GTK to close & open some windows, and hook the new windows into layer-shell). I believe this is a problem with one of the lower-level components - either the GTK Vulkan renderer, the compositor or GPU drivers. Alternatively it might be fixed on -git and I may have forgotten - could you try building the repo from source and see if it still occurs please?

JakeStanger commented

2026-05-22 23:54:57 +01:00

Author

Owner

@ildar commented on GitHub (Feb 25, 2026):

@JakeStanger , I'll try the git HEAD a little later. Meanwhile:

INFO GTK: 109: [Gdk] MESSAGE: Lost connection to Wayland compositor.

This shows that IB sees something is happening with the screen and exits. This never happened before (in 0.17.1) and I think it's the regression.

Also can you please confirm that ironbar reload actually works? For me it crashes even without any config file.

@ildar commented on GitHub (Feb 25, 2026): @JakeStanger , I'll try the git HEAD a little later. Meanwhile: > INFO GTK: 109: [Gdk] MESSAGE: Lost connection to Wayland compositor. This shows that IB sees something is happening with the screen and exits. This never happened before (in 0.17.1) and I think it's the regression. Also can you please confirm that `ironbar reload` actually works? For me it crashes even without any config file.

JakeStanger commented

2026-05-22 23:54:57 +01:00

Author

Owner

@JakeStanger commented on GitHub (Feb 25, 2026):

This shows that IB sees something is happening with the screen and exits.

The log is from GDK, not Ironbar. 0.18 switches to GTK4, which includes new versions of GDK, a new rendering stack, and a new version of gtk-layer-shell. There's a lot of things that could go wrong under the hood, and the most likely culprits are the ones I listed before.

can you please confirm that ironbar reload actually works?

Yes, it works.

@JakeStanger commented on GitHub (Feb 25, 2026): > This shows that IB sees something is happening with the screen and exits. The log is from GDK, not Ironbar. 0.18 switches to GTK4, which includes new versions of GDK, a new rendering stack, and a new version of gtk-layer-shell. There's a lot of things that could go wrong under the hood, and the most likely culprits are the ones I listed before. > can you please confirm that ironbar reload actually works? Yes, it works.

JakeStanger commented

2026-05-22 23:54:58 +01:00

Author

Owner

@ildar commented on GitHub (Feb 25, 2026):

2026-02-24T11:33:24.259971Z  INFO ironbar::clients::outputs: 74: Monitor HDMI-A-2 disconnected
2026-02-24T11:33:24.265938Z  INFO GTK: 109: [Gdk] MESSAGE: Lost connection to Wayland compositor.

Can this event be handled? Maybe reload or restart the bar?

@ildar commented on GitHub (Feb 25, 2026): ``` 2026-02-24T11:33:24.259971Z INFO ironbar::clients::outputs: 74: Monitor HDMI-A-2 disconnected 2026-02-24T11:33:24.265938Z INFO GTK: 109: [Gdk] MESSAGE: Lost connection to Wayland compositor. ``` Can this event be handled? Maybe reload or restart the bar?

JakeStanger commented

2026-05-22 23:54:58 +01:00

Author

Owner

@JakeStanger commented on GitHub (Feb 25, 2026):

No, that's not a part of the stack I have control of, and it's a fatal error.

I'd test if it happens with any other gtk4-layer-shell apps for you.

@JakeStanger commented on GitHub (Feb 25, 2026): No, that's not a part of the stack I have control of, and it's a fatal error. I'd test if it happens with any other gtk4-layer-shell apps for you.