mirror of
https://github.com/JakeStanger/ironbar.git
synced 2026-07-11 07:15:19 +01:00
[GH-ISSUE #808] Hyprland client crashes when encountering invalid characters #4469
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#4469
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 @salahoued on GitHub (Dec 9, 2024).
Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/808
Describe the bug
The workspace module (Hyprland) stops working after some time from starting up and no longer shows the active workspace if any other new workspace,
Terminal logs
To Reproduce
ironbarExpected behavior
Workspaces do not crash
System information:
Configuration
Config
Styles
Screenshots

@JakeStanger commented on GitHub (Dec 9, 2024):
From the logs it looks like this is an issue immediately at startup, rather than one that occurs after some time. Are you able to confirm please?
It also looks like a Hyprland issue, or at least one with the IPC client. Are you able to confirm the version (or commit if on -git) of Hyprland you're using?
@salahoued commented on GitHub (Dec 9, 2024):
The issue doesn't occur immediately at startup, it occurs after some time had passed, from the logs above I started
ironbarat 10:45 and the issue occured at 13:46, the current instance is started at 14:51 and it's still working now at 18:01Hyprland -vfrom openSUSE Tumblweed repos@JakeStanger commented on GitHub (Dec 9, 2024):
Oh you're right sorry, I missed that
@JakeStanger commented on GitHub (Dec 9, 2024):
Have you seen this happen a few times? I'm trying to work out what would even cause a UTF 8 error and the only thing that comes to mind is the actual data scream is interrupted between the Hyprland socket and client.
@salahoued commented on GitHub (Dec 9, 2024):
Yes, It did happen, I'd say every time I start
ironbar, it's been a few days now that I started using hyprland+ironbar@salahoued commented on GitHub (Dec 9, 2024):
Yes, It did happen, I'd say every time I start
ironbar, it's been a few days now that I started using hyprland+ironbar@JakeStanger commented on GitHub (Dec 10, 2024):
Still not 100% sure why it's happening but it looks to be a problem with the
hyprland-rscrate rather than Ironbar.I've just parsed the byte string in the error, which shows:
So for some reason it's not liking the
é, despite being valid UTF-8.@salahoued commented on GitHub (Dec 10, 2024):
It seems right, right after running
vlcthe error is encountered, and after restartingironbarwithvlcstill running there is no error and seems to be working fine,I'm not sure could it have any effect on #809 ?
@JakeStanger commented on GitHub (Dec 10, 2024):
No that won't be related. I suspect that's flatpak-related but I've not had a chance to look yet
@salahoued commented on GitHub (Dec 10, 2024):
OK, Thanks