mirror of
https://github.com/JakeStanger/ironbar.git
synced 2026-07-11 09:15:22 +01:00
[GH-ISSUE #528] exiting session causes broken pipe error spam #4390
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
JakeStanger/ironbar#4390
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @aquifolly on GitHub (Apr 1, 2024).
Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/528
Describe the bug
when i exit the session, the logs are spammed with broken pipe errors
To Reproduce
Steps to reproduce the behavior:
Expected behavior
ironbar exits cleanly with the session
System information:
Screenshots
@JakeStanger commented on GitHub (Apr 1, 2024):
How is Ironbar started? Are you using a systemd service?
The errors make sense as Ironbar is staying open once your compositor closes for some reason, which obviously isn't going to work. The question is how we ensure it closes.
@aquifolly commented on GitHub (Apr 1, 2024):
ah, I'm starting it inside the sway config
https://git.gay/pinkcreeper100/nix-config/src/branch/main/modules/home/desktop/sway/default.nix#L158
@aquifolly commented on GitHub (Apr 1, 2024):
that'd make sense
@JakeStanger commented on GitHub (Apr 1, 2024):
What if you set it as a bar rather than a startup command? Hopefully sway would handle shutting it down then. If not I'll have to change the wayland client logic to exit on error.
@aquifolly commented on GitHub (Apr 2, 2024):
when i looked in btop, there were two ironbar processes, so i've removed it from the
startupand will check if it still works@aquifolly commented on GitHub (Apr 2, 2024):
the systemd unit works
@JakeStanger commented on GitHub (Apr 2, 2024):
What systemd unit? Define 'works'. Did you test my suggestions?
Pleae give me something to go on here.
@aquifolly commented on GitHub (Apr 2, 2024):
I removed ironbar from the startup section in my sway config, and just using the systemd unit provided by the nix module, i no longer seem to encounter the error
@JakeStanger commented on GitHub (Apr 2, 2024):
In that case I'll close this issue. Any further issues let me know and we can reopen
@aquifolly commented on GitHub (Apr 2, 2024):
it may still be a good idea to do this, as there may be users who don't use the systemd unit, or just aren't using systemd at all
@yavko commented on GitHub (Apr 2, 2024):
Glad my code works