DevCuber

cross-posted from: https://sh.itjust.works/post/27097438

I store my programs in a cryptomator vault which uses a fuse virtual drive (The default on Linux), but when trying to update pip inside a venv I get an error, then any subsequent use of pip also throws an error and {path_to_venv}/lib/python3.12/site-packages/pip/ becomes empty.

I imagine this is an issue that would happen in any FUSE drive although I don't know how to test that.

Here are the logs

• OS : Fedora 40
• pip version: 23.3.2 updating to 24.2
• python version: 3.12.7

I already made a bug report on the github

Does anyone know a temporary workaround for this ?

I store my programs in a cryptomator vault which uses a fuse virtual drive (The default on Linux), but when trying to update pip inside a venv I get an error, then any subsequent use of pip also throws an error and {path_to_venv}/lib/python3.12/site-packages/pip/ becomes empty.

I imagine this is an issue that would happen in any FUSE drive although I don't know how to test that.

Here are the logs

• OS : Fedora 40
• pip version: 23.3.2 updating to 24.2
• python version: 3.12.7

I already made a bug report on the github

Does anyone know a temporary workaround for this ?

After selecting the boot option (no matter if it's the live iso or the installed distro, and no matter the kernel version) I get stuck on that screen, at that point the only thing I can do is reboot by pressing the power button.

This only seems to happen on this computer.

Here are some system information :

• motherboard : ASUS PRIME A320M-K
• BIOS version : 5603 (latest available version)
• CPU : AMD Ryzen 5 2600
• GPU : Nvidia GeForce GTX 1660

The only way I was able to install the system was by using the acpi=off boot option but I understand it can negatively impact the system. Does anyone know why this happens and how to fix it ?