[GH-ISSUE #948] Launcher: Buggy behavior with LibreOffice applications (and potentially others with a base launcher application) #1695

Open
opened 2026-05-22 22:54:03 +01:00 by JakeStanger · 0 comments
Owner

Originally created by @BowDown097 on GitHub (Apr 24, 2025).
Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/948

Describe the bug
When, for example, a file is opened directly with LibreOffice Writer, the instance of LibreOffice Writer is first launched through an instance of LibreOffice Base. Once this launching routine is finished, all that remains is a broken entry to the now nonexistent initial LibreOffice Base instance. As a result, the LibreOffice Writer instance is inaccessible. Furthermore, the broken entry does not go away until the bar is reloaded.

Interestingly, this does not happen when opening LibreOffice Writer plainly, with no target file. Perhaps the launching routine is different in this case, or launching with arguments is tripping something up in the bar code?

To Reproduce
Steps to reproduce the behavior:

  1. Add module launcher
  2. Open any LibreOffice application with a target file
  3. Observe remaining, broken LibreOffice Base entry

Expected behavior
The LibreOffice Base entry is replaced with a functional entry for the target LibreOffice application once it is launched.

System information:

  • Distro: Artix Linux
  • Compositor: Wayfire
  • Ironbar version: 0.16.1.r251.ga9508e6-1

Configuration
<-- Share your bar configuration and stylesheet as applicable: -->

Config
anchor_to_edges = true
position = "bottom"
icon_theme = "kora"
icon_overrides = { "com.hex-rays.ida" = "ida" }
height = 48

[[start]]
type = "launcher"
favorites = [
    "launcher",
    "pcmanfm-qt",
    "zen",
    "legcord",
    "Element",
    "mpc-qt",
    "URxvt",
    "QtCreator",
    "VSCodium",
    "QtTube"
]
icon_size = 48
show_names = false
show_icons = true
Styles

Screenshots
Image
The result of opening and closing a document two times with LibreOffice Writer.

Originally created by @BowDown097 on GitHub (Apr 24, 2025). Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/948 **Describe the bug** When, for example, a file is opened directly with LibreOffice Writer, the instance of LibreOffice Writer is first launched through an instance of LibreOffice Base. Once this launching routine is finished, all that remains is a broken entry to the now nonexistent initial LibreOffice Base instance. As a result, the LibreOffice Writer instance is inaccessible. Furthermore, the broken entry does not go away until the bar is reloaded. Interestingly, this does not happen when opening LibreOffice Writer plainly, with no target file. Perhaps the launching routine is different in this case, or launching with arguments is tripping something up in the bar code? **To Reproduce** Steps to reproduce the behavior: 1. Add module `launcher` 2. Open any LibreOffice application with a target file 3. Observe remaining, broken LibreOffice Base entry **Expected behavior** The LibreOffice Base entry is replaced with a functional entry for the target LibreOffice application once it is launched. **System information:** - Distro: Artix Linux - Compositor: Wayfire - Ironbar version: 0.16.1.r251.ga9508e6-1 **Configuration** <-- Share your bar configuration and stylesheet as applicable: --> <details><summary>Config</summary> ``` anchor_to_edges = true position = "bottom" icon_theme = "kora" icon_overrides = { "com.hex-rays.ida" = "ida" } height = 48 [[start]] type = "launcher" favorites = [ "launcher", "pcmanfm-qt", "zen", "legcord", "Element", "mpc-qt", "URxvt", "QtCreator", "VSCodium", "QtTube" ] icon_size = 48 show_names = false show_icons = true ``` </details> <details><summary>Styles</summary> ```css ``` </details> **Screenshots** ![Image](https://github.com/user-attachments/assets/a63824c2-f329-4dfa-a7ea-bc84d927b307) The result of opening and closing a document two times with LibreOffice Writer.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
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#1695
No description provided.