A.I.

Error “Group(s) not found: ui (via –with)” installing PrivateGPT 0.4 on WSL

Note: the below assumes you already have followed any other guide, but you have gotten an error up to that point. The below will pick up directly where you left off in the your original guide.

As of a few days ago, when you try to install PrivateGPT with Poetry on WSL following various guides, the commands: “cd privateGPT”, “poetry install –with ui”, “poetry install –with local”, Poetry returns the errors.

Group(s) not found: ui (via –with)
Group(s) not found: local (via –with)

When going through the commit (which can be found here: 45f0571), it turns out that ui is moved from its own group and has moved to the “extras” group. It’s unclear to me where “local” went though.

A.I.

PrivateGPT: ImportError: docx2txt is required to read Microsoft Word files

When trying to interact with Microsoft Word files, PrivateGPT throws out an error and does not want to parse it:
ImportError: docx2txt is required to read Microsoft Word files: pip install docx2txt

When actually installing docx2txt with pip, the error is still there. For some strange reason, PrivateGPT is still recommending pip, while it has moved away from pip for quite a while now. To resolve the issue, the answer is simple: Do Not Use Pip to install docx2txt (or whisper or any of the other converters you may need to upload your files.

Ubuntu 22.04

Veeam warning: “Unable to initialize indexing: mlocate was not found” on Ubuntu Server 22.04

After playing with Veeam 11 for a bit, I decided to get my Linux Docker physical host on the backup schedule. The hardware is getting older (Some would call it vintage or just plain ancient as it’s a 2nd gen i7, but it gets the job done) and it won’t last forever. The onboarding of this physical machine was deceptively simple. A few mouse-clicks here, an IP address there and some SSH credentials. This was just too easy, so I decided to manually run the job and keep an eye on it. I didn’t have to wait long.
After a few minutes, the job completed already. With a warning. I knew it had been too good to be true.

Linux

Ubuntu displays print_req_error: I/O error, dev fd0, sector 0

With a new install as a virtual server, Ubuntu repeatedly displays the error:

print_req_error: I/O error, dev fd0, sector 0

The reason is the virtual server does not have a floppy drive. To resolve:

# sudo rmmod floppy
# echo “blacklist floppy” | tee /etc/modprobe.d/blacklist-floppy.conf
# sudo dpkg-reconfigure initramfs-tools

The message should now be gone for good.