Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG/cosmetic] Fail to parse hyprctl version #97

Closed
taschenlampe opened this issue Apr 29, 2024 · 3 comments
Closed

[BUG/cosmetic] Fail to parse hyprctl version #97

taschenlampe opened this issue Apr 29, 2024 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@taschenlampe
Copy link

taschenlampe commented Apr 29, 2024

Pyprland Version

2.2.15

Pyprland is running smoothly in terms of functionality – no complaints there. But, I've noticed an error popping up in the startup logs about version parsing. It doesn't mess with the app's operation.

Here’s the error message:

pyprland - Fail to parse hyprctl version: Expecting value: line 8 column 16 (char 136) // pyprland.py:18

It's linked to this bit in the code:

self.log.error("Fail to parse hyprctl version: %s", e)

And here's a link to the full log for more context: OpenSUSE Paste Link

Steps to Reproduce

Just by firing up pypr

Ideally, it’d be great if the app could start up without this little hiccup.

Workaround

For now, I just nixed the version check by hardcoding:

state.hyprland_version = VersionInfo(0, 0, 0)

This stops the error from showing up, though I'm a bit worried it might cause issues down the road.
Cheers!

Almost forgot -> Thanks for all the awesome work on Pyprland! It’s a fantastic tool and I’m really enjoying using it. Keep up the great work!

@taschenlampe taschenlampe added the bug Something isn't working label Apr 29, 2024
@fdev31
Copy link
Collaborator

fdev31 commented Apr 29, 2024

It looks like a duplicate of #96 - it turns to be a bug in Hyprland mainstream.

Problems shouldn't be hidden... this should happen in case of real issue either with Hyprland or with its packaging.

But first, what is the output of your hyprctl -j version ?

@fdev31
Copy link
Collaborator

fdev31 commented Apr 29, 2024

Btw, I'm worried you needed a workaround, it should be "automatic", without it what happened wrong?

@taschenlampe
Copy link
Author

Everything is functioning as expected with pypr.
I've discovered a bug report relevant to my situation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants