-
Notifications
You must be signed in to change notification settings - Fork 13
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
Calculate Anything extension crashed [ULauncher] #58
Comments
I am not sure if Ulauncher dev team has enabled a virtualenv per extension, but for now you should install the dependencies using |
In my case, this did the trick : sudo apt install python3-pint python3-simpleeval python3-parsedatetime python3-tz |
Updating these fixed it for me on Arch:
|
This person solved it in their nix config, which I copied for mine :D https://github.com/b3nj5m1n/dotfiles/blob/ca39a62644bc97ec9e61dea3ad63cfdfb4aa6ef1/nix/modules/nixos/ulauncher.nix |
Getting the same issue issue (I think?) under Bluefin (Silverblue / Universal Blue). I'm new to Linux desktops (well; that's not true, but I didn't run one in 15 years as my daily driver until today)...but I'm happy to help debug or whatnot! |
@toriacx, Do any of the solutions above work for you? Generally, the package issue is hard to fix. Normally, the extensions should run in their own virtual environment, and honestly, from the u-launcher perspective, it should not be that hard to implement. |
Describe the bug
Calculate Anything extension crashed after I added it to ULauncher
To Reproduce
I just added the extension and that happened.
Logs
I couldn't find any logs at
~/.cache/com.github.tchar.calculate-anything/log
.Screenshots
Desktop
Additional context
I am not a expert when it comes to installing python packages... especially on linux.
I don't know what is the best way to install pip packages as of PEP668.
I tried to install the dependencies (
requests pint simpleeval parsedatetime
) by creating a venv in/usr/local/venv
.If you have any better way of installing pip packages, feel free to tell me... Maybe the dependencies aren't recognised by the extension.
The text was updated successfully, but these errors were encountered: