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] Can not start Version 0.9.29 #296

Closed
Schievel1 opened this issue May 2, 2024 · 2 comments · Fixed by #297
Closed

[BUG] Can not start Version 0.9.29 #296

Schievel1 opened this issue May 2, 2024 · 2 comments · Fixed by #297

Comments

@Schievel1
Copy link
Contributor

Schievel1 commented May 2, 2024

Describe the bug
When I try to start nwg-panel it will not start and shows the following message:

 ➜ nwg-panel
Traceback (most recent call last):
  File "/usr/lib/python-exec/python3.11/nwg-panel", line 5, in <module>
    from nwg_panel.main import main
  File "/usr/lib/python3.11/site-packages/nwg_panel/main.py", line 162
    hypr_dir = f"{os.getenv("XDG_RUNTIME_DIR")}/hypr" if os.path.isdir(
                             ^^^^^^^^^^^^^^^
SyntaxError: f-string: unmatched '('

To Reproduce

  1. start nwg-panel (version 0.9.29)

Expected behavior
Nwg-panel starts

Desktop (please complete the following information):

  • Gentoo Linux
  • Hyprland, built from branch at commit fe7b748eb668136dd0558b7c8279bfcd7ab4d759 (props: bump version to 0.39.1).
    Date: Tue Apr 16 16:01:03 2024
    Tag: v0.39.1, commits: 4460
  • Panel version 0.9.29
  • Python 3.11.9

This also happens with 0.9.28
Also XDG_RUNTIME_DIR exists on my system:

➜echo $XDG_RUNTIME_DIR                                            took 61ms
/run/user/1000
@Schievel1
Copy link
Contributor Author

Schievel1 commented May 2, 2024

Seems like I should migrate to python 3.12

https://docs.python.org/3/whatsnew/3.12.html#whatsnew312-pep701

@nwg-piotr
Copy link
Owner

Thanks. I've been trying to understand this bug for 2 days, as it was reported from nwg-displays (I used exactly the same few lines of code), and I'm unable to reproduce it in my environment. Use of f-string was my choice, not a must. Let me take a closer look at it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants