Linux Mint 22 Compatibility Issues

[Majoraslayer]

Linux Mint 22 Compatibility Issues

[Majoraslayer]

Update on this. I recently received an update for Python. Now the native Python install method halts at the following error instead:

ERROR: Cannot uninstall psutil 5.9.8, RECORD file not found. Hint: The package was installed by debian.

Trying to uninstall psutil with "apt remove python3-psutil" inexplicably tries to autoremove the entire Cinnamon desktop environment.

[Majoraslayer]

^ While the above issue still prevents the direct Python installation method from working on Mint 22, the recent repository update to my Python seems to have fixed some other issues. I tried the venv method again, and it now seems to work. Because of that, I'm going to go ahead and close this issue. If anyone else runs across these issues, it seems venv should be a good method to install on Mint 22 as of 8/28/2024.

[IPv6]

Why not use conda? afaik Fooocus is tied to Python 3.10

[Majoraslayer]

I tried installing Anaconda, but some of the listed pre-requisites either weren't available to install or caused conflicts with sound libraries. I was able to install Miniconda, but that method still ran into the same issue with pytorch when trying to execute Fooocus.

[IPv6]

It seems that the problem is in combination of linux version, python version and hardware details, "No matching distribution found for torch" means that. You'd better find how to install torch for your situation at torch support forums (imho it is not purely a Mint issue, its just linux). Fooocus don`t do anything spicy here, it just need torch to be installed. May be there are custom distributions/repos or something like that.

[daedon]

I've been using Fooocus on Mint with XFCE for 4 months, zero problems.

[Majoraslayer]

I've been using Fooocus on Mint with XFCE for 4 months, zero problems.

Mint 22 just released last month, did you upgrade to the latest version?

[daedon]

No. I'm running Mint 21.3 with all the updates but I haven't done an upgrade. Python 3.10.12 Fooocus version: 2.5.5 same as yours My hardware is an MSI Aegis i7 137000F, 64G Ram, NVIDIA GeForce RTX 4060 8G A 1Tb SSD with Windows and a 4Tb SSD with Mint that runs the same software 5 to 10 times faster than on the Windows SSD. Aside from power outages, Fooocus has been running 24/7 with no problems. I'm relatively new to this, not sure it's Linux version related.

…

On Sun, Aug 25, 2024 at 5:38 PM Majoraslayer ***@***.***> wrote: I've been using Fooocus on Mint with XFCE for 4 months, zero problems. Mint 22 just released last month, did you upgrade to the latest version? — Reply to this email directly, view it on GitHub <#3535 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAZQBNL2L24R2NQE3L4373TZTJFHDAVCNFSM6AAAAABMURHTOSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBZGAYDGOBXGU> . You are receiving this because you commented.Message ID: ***@***.***>

-- Donald Edward This message is solely for the intended recipient and may contain confidential or privileged information. If you are not the intended recipient, any disclosure, copying, use, or distribution of the information included in this message is prohibited. If you have received this communication in error, please notify and immediately and permanently delete this message and any attachments. Thank you.

[Majoraslayer]

No. I'm running Mint 21.3 with all the updates but I haven't done an upgrade. Python 3.10.12 Fooocus version: 2.5.5 same as yours My hardware is an MSI Aegis i7 137000F, 64G Ram, NVIDIA GeForce RTX 4060 8G A 1Tb SSD with Windows and a 4Tb SSD with Mint that runs the same software 5 to 10 times faster than on the Windows SSD. Aside from power outages, Fooocus has been running 24/7 with no problems. I'm relatively new to this, not sure it's Linux version related.

It's been a few days since I dug into it, but if I remember correctly, I believe the dead end I came to involved a dependency on the libasound2 library. Mint 22 switches the audio backend from PulseAudio to Pipewire, and I suspect that may be causing conflicts with audio libraries that Python stuff like PyTorch look for and depend on. It's actually the second time I've encountered a problem in Mint 22 related to libasound2; the first was a dependency check with DaVinci Resolve, and trying to install it to fix it automatically uninstalled most of Cinnamon. If I remember, this specific issue causes problems with installing PyTorch, which means Fooocus can't run.

While it may be true that the finger can be pointed at PyTorch, Pipewire, or Linux Mint themselves, I reported this issue so the devs would be aware of it in case they want to develop a workaround fix or alternative way of doing things. It looks like Linux distros may be moving toward further adopting Pipewire, and if I'm right about that being the cause of problems with libasound2, it may be worth looking into. I've been running Fooocus in a Docker container from a dev who deleted their project and GitHub account, so it's no longer online with a maintainer. It would be great to see an OFFICIAL Docker image, or other self-contained alternative environment, as an officially supported install method. That's why I also opened a feature request to suggest it as a possible future-focused (no pun intended) solution to issues like these.

[daedon]

BTW: - I'm using XFCE, I wanted the most lightweight environment. - I'm using python venv (I haven't learned Docker yet) - If you're playing with LLMs and haven't yet, LMStudio and Qwen2 are amazing. - I would suggest describing your problem to ChatGPT, you can get some insightful replies.

…

On Sun, Aug 25, 2024 at 6:36 PM Majoraslayer ***@***.***> wrote: No. I'm running Mint 21.3 with all the updates but I haven't done an upgrade. Python 3.10.12 Fooocus version: 2.5.5 same as yours My hardware is an MSI Aegis i7 137000F, 64G Ram, NVIDIA GeForce RTX 4060 8G A 1Tb SSD with Windows and a 4Tb SSD with Mint that runs the same software 5 to 10 times faster than on the Windows SSD. Aside from power outages, Fooocus has been running 24/7 with no problems. I'm relatively new to this, not sure it's Linux version related. It's been a few weeks since I dug into it, but if I remember correctly, I believe the dead end I came to involved a dependency on the libasound2 library. Mint 22 switches the audio backend from PulseAudio to Pipewire, and I suspect that may be causing conflicts with audio libraries that Python stuff like PyTorch look for and depend on. It's actually the second time I've encountered a problem in Mint 22 related to libasound2; the first was a dependency check with DaVinci Resolve, and trying to install it to fix it automatically uninstalled most of Cinnamon. If I remember, this specific issue causes problems with installing PyTorch, which means Fooocus can't run. While it may be true that the finger can be pointed at PyTorch, Pipewire, or Linux Mint themselves, I reported this issue so the devs would be aware of it in case they want to develop a fix or alternative way of doing things. It looks like Linux distros may be moving toward further adopting Pipewire, and if I'm right about that being the cause of problems with libasound2, it may be worth looking into. I've been running Fooocus in a Docker container from a dev who deleted their project and GitHub account, so it's not longer online with a maintainer. It would be great to see an OFFICIAL Docker image, or other self-contained alternative environment, as an officially supported install method. That's why I also opened a feature request to suggest it as a possible future-focused (no pun intended) solution to issues like these. — Reply to this email directly, view it on GitHub <#3535 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAZQBNP7DNXKMKFL45APKR3ZTJL7VAVCNFSM6AAAAABMURHTOSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBZGAZDCNBZG4> . You are receiving this because you commented.Message ID: ***@***.***>

-- Donald Edward This message is solely for the intended recipient and may contain confidential or privileged information. If you are not the intended recipient, any disclosure, copying, use, or distribution of the information included in this message is prohibited. If you have received this communication in error, please notify and immediately and permanently delete this message and any attachments. Thank you.