JakeStanger/ironbar

Fork 0

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

[GH-ISSUE #1020] Zombie gtk-launch processes leftover each time a gtk app is launched through menu module #1723

New issue

Closed

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

JakeStanger commented

2026-05-22 22:54:13 +01:00

Owner

Originally created by @JEC15 on GitHub (May 31, 2025).
Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/1020

Describe the bug
When launching gtk applications through the menu module, a zombie gtk-launch process is leftover for each time an application is launched. Only killing ironbar lets the processes terminate.

Edit: Applies to non-gtk applications as well.

To reproduce
Steps to reproduce the behavior:

Add module menu
Launch gtk application
Close launched gtk application
Inspect the output of ps -e | grep 'gtk-launch'. It will show one gtk-launch process marked as <defunct> (or more if a gtk application was launched through the menu module more than once)
Launch the same (or another) gtk application through the menu module
Close launched gtk application
Inspect the output of ps -e | grep 'gtk-launch' again. It will show one additional defunct gtk-launch process
Repeat from step 2

Expected behavior
gtk-launch processes should terminate after application quit.

System information:

Distro: Arch Linux
Compositor: Sway
Ironbar version: v0.16.1, commit b62d0d5

Configuration

Config

[[start]]
type = "menu"
width = 500

Originally created by @JEC15 on GitHub (May 31, 2025). Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/1020 **Describe the bug** When launching gtk applications through the menu module, a zombie gtk-launch process is leftover for each time an application is launched. Only killing ironbar lets the processes terminate. Edit: Applies to non-gtk applications as well. **To reproduce** Steps to reproduce the behavior: 1. Add module `menu` 2. Launch gtk application 3. Close launched gtk application 4. Inspect the output of `ps -e | grep 'gtk-launch'`. It will show one gtk-launch process marked as `<defunct>` (or more if a gtk application was launched through the `menu` module more than once) 5. Launch the same (or another) gtk application through the `menu` module 6. Close launched gtk application 7. Inspect the output of `ps -e | grep 'gtk-launch'` again. It will show one additional defunct gtk-launch process 8. Repeat from step 2 **Expected behavior** gtk-launch processes should terminate after application quit. **System information:** - Distro: Arch Linux - Compositor: Sway - Ironbar version: v0.16.1, commit [b62d0d5](https://github.com/JakeStanger/ironbar/commit/b62d0d58cbf0de5bd72b7615defd12a37ca982ad) **Configuration**  <details><summary>Config</summary> ``` [[start]] type = "menu" width = 500 ``` </details>

JakeStanger

2026-05-22 22:54:13 +01:00

closed this issue
added the
M:Menu

T:Bug

P:High

A:Client
labels

JakeStanger commented

2026-05-22 22:54:13 +01:00

Author

Owner

@JakeStanger commented on GitHub (Jun 3, 2025):

Thanks for reporting.

Can you confirm if you're seeing the same thing with the launcher module please?

@JakeStanger commented on GitHub (Jun 3, 2025): Thanks for reporting. Can you confirm if you're seeing the same thing with the `launcher` module please?

JakeStanger commented

2026-05-22 22:54:13 +01:00

Author

Owner

@JEC15 commented on GitHub (Jun 3, 2025):

Yeah, the launcher module shows the same behavior. Config used:

[[start]]
type = "launcher"
favorites = ["firefox", "pavucontrol-qt"]
show_names = false
show_icons = true
reversed = false

@JEC15 commented on GitHub (Jun 3, 2025): Yeah, the `launcher` module shows the same behavior. Config used: ``` [[start]] type = "launcher" favorites = ["firefox", "pavucontrol-qt"] show_names = false show_icons = true reversed = false ```

JakeStanger commented

2026-05-22 22:54:13 +01:00

Author

Owner

@JakeStanger commented on GitHub (Jul 14, 2025):

Should be sorted now, apologies for the delay. Let me know if you still have issues.

@JakeStanger commented on GitHub (Jul 14, 2025): Should be sorted now, apologies for the delay. Let me know if you still have issues.

JakeStanger commented

2026-05-22 22:54:13 +01:00

Author

Owner

@JEC15 commented on GitHub (Jul 17, 2025):

No worries, thanks for looking into it. Unfortunately, the issue is still present in my system, in the menu module. (For the sake of clarification, i did remember to rebuild ironbar, and am at commit 34da5ed now).

As for the launcher module, i am no longer able to launch applications from it by clicking on the icons for the favorites i have set in the config file. This was working correctly before. Switching between already running applications by clicking on their icons works, though. Let me know any additional info you need me to provide.

@JEC15 commented on GitHub (Jul 17, 2025): No worries, thanks for looking into it. Unfortunately, the issue is still present in my system, in the `menu` module. (For the sake of clarification, i did remember to rebuild ironbar, and am at commit [34da5ed](https://github.com/JakeStanger/ironbar/commit/34da5edfe0ed42180a78441e4999d4b33de0c4aa) now). As for the `launcher` module, i am no longer able to launch applications from it by clicking on the icons for the favorites i have set in the config file. This was working correctly before. Switching between already running applications by clicking on their icons works, though. Let me know any additional info you need me to provide.

JakeStanger commented

2026-05-22 22:54:14 +01:00

Author

Owner

@JakeStanger commented on GitHub (Jul 20, 2025):

My bad, I clearly did not test that previous fix as thoroughly as I should. I've got a new fix on the way that looks more hopeful

@JakeStanger commented on GitHub (Jul 20, 2025): My bad, I clearly did not test that previous fix as thoroughly as I should. I've got a new fix on the way that looks more hopeful

JakeStanger commented

2026-05-22 22:54:14 +01:00

Author

Owner

@JEC15 commented on GitHub (Jul 21, 2025):

Launching applications from the launcher module works again, and the original issue (in both the menu and launcher module) is also solved. Thank you!

@JEC15 commented on GitHub (Jul 21, 2025): Launching applications from the `launcher` module works again, and the original issue (in both the `menu` and `launcher` module) is also solved. Thank you!