ComfyUI errors after install the core requirements since Version 1.13.1, tested also with Version 1.14.0 #404
Labels
linux
Linux related
Comments
|
It fails to import a rather basic/popular package ( |
|
It gave the following output: |
|
Hm, it looks perfectly fine. Not sure why the encoding matters, but you can check output of |
|
|
|
Looks okay also. Do you get the error also when running the server from the command line? the plugin uses following command to enforce UTF-8, maybe it's related |
|
It's weird because it worked well with the older versions |
|
If you're inside Yes it's strange, but newer plugin versions also use a newer ComfyUI, and the import that is causing issues may have been added recently. |
|
Hey, Logs: Running it through command line, enforcing the encoding or not, returns this: |
|
@SkeletoMukit it somehow didn't even get as far as the plugin log, so still unclear if |
|
@Acly Yes, I ran it with -s, copy-pastet your code. |
|
You can also try without Another thing to try would be setting system locale/language to english, see if it changes anything. I tried setting my ubuntu to spanish but still can't reproduce this error though. |
|
Fixed starting it from command line Tried installing packaging as you said. Which returned this error: So I installed it with Starting it with the enforced encoding Starting it within Krita doesn't work. Outputs the same logs as before. Whole terminal fix: |
|
Thanks for testing. I suspect it has something to do with the environment the server process is started from. Which Linux are you using? And how did you install Krita? It would be interesting if the AppImage version of Krita has the same issue. If you want to try, download from krita.org, run and set the same resource path (Settings > Configure Krita > General > Resources), maybe it picks it up automatically. That should allow it to access the plugin and test it. |
|
I am using Linux Mint 21.3 Cinnamon with changed kernel to 6.5.0-17-generic. I tried installing the AppImage also version 5.2.2 and yes it works with the same resource path. :D Also tried granting the Flatpak version every permission i could in Flatseal(just a random thought) and it didn't change a thing. |
In my case I installed Krita with Flatpak, and this is my system: |
Acly
added a commit
that referenced
this issue
Feb 15, 2024
|
I tried the Flatpak on my laptop (Fedora), but couldn't reproduce it there either. I noticed that when installing the server from Flatpak-Krita, it will use a Python that comes from the Flatpak environment, not your system Python (not even sure if that's accessible at all). In my case the For now I can only recommend using the AppImage as a workaround. There are some other issues like #344 that probably don't have a solution because installing things from within a Flatpak app is kind of against its design. |
|
Testing the latest version with a Krita flatpak: Testing it with Krita Appimage (not related with this bug report): |
|
Yes I tried to clear the environment of outside influence for flatpak, but it didn't help (I also didn't have much hope that it would). The AppImage should work if you |
Thanks now I could use it via Appimage meanwhile the Flatpak one is not working. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Logs:
The text was updated successfully, but these errors were encountered: