Fleetscut

is your wifi braodcom? broadcom drivers arent supported by the kernel, and the repo usually doesnt get updated until a few days after the new kernel goes out. If you pulled in a new kernel with your pacman -Syu then a broadcom wifi chip will no longer work. you can either check the repo to see if the new driver is released then put it onto a usb and install it, or roll back your kernel and linux headers.

If you actually wrote a new file system to the partition then you are SOL. You would need a professional recovery service, and they would only be able to recover so much. But if all you did was change the partition table you could theoretically try to change it back to what the old scheme was. But you would need to have as much info as possible, like the starting block location and block size. You could also try to look for a tool that would look at various blocks and try to piece together which ones were part of the same file. But i think this might not work on drives that were too fragmented.

Its a lot easier to set up a virtual machine, especially if your intentions are just to mess around and learn. This also makes it easy to install a bunch of different distros and see which ones you like the most. Even if you do go into using linux for your job, unless there are very specific high performance demands (or you want to switch full time from windows) its still easier to use a VM.

It seems this is a GTK application. which means it will take on the system wide settings. You can use LXappearence to modify GTK theme settings and apply different icon packs, fonts, etc.

zsh is case insensitive for tab completion. just type cd desktop and hit tab, if there is only one match it will auto replace with the caplitalised version. If theres more than one you get the usual tab completion list

Heres the line. My setup never worked until i replaced the first line with this <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>

Code 43 is a generic error that means something went wrong starting the device. It could have any number of causes for any number of reasons. When working with virtual machines and gpu passthrough it is most likely due to nvidia drivers detecting the VM environment and not allowing itself to be started

theres one thing in that guide that i dont see mentioned. There is a line you need to add to the very top of the xml definition for your virtual machine otherwise none of the changes you made wont actually take effect. Im not home right now so i cant copy in the line here but im sure its searchable. Also make sure that you place the "<hidden state='on'/>" in the correct section otherwise it doesnt work.

Ive heard that ryzen is unstable when it comes to virtualization. what did you set up as the specs for the VM? The default settings you choose when creating the VM matter as choosing the wrong preset could effect how it boots

are you printing to the screen or a file? the reason printing to a screen is so slow is that the buffer used to hold the data has to be flushed constantly. if you dont want to see live updates of every line then look to see if the language you are using has a way to control how often the buffer is flushed to the screen. or just write to a file.

These are actually pretty fun. Heres my crack at 3

which package did you install then?

first you would need to remove busybox. However i believe you would also need to replace all the missing components that would create. I think you should try to reinstall coreutils as its the one mentioned in your original error. though i dont know what else busybox might have replaced. If you are not too attached to your current installation id say its easiest to reinstall fresh.

like i said, i dont think busy box was the package you needed to install. From what i can see wpa_supplicant only depends on libnl and a few optional ones none of them busybox.

the error is because you are getting dependency conflicts. This usually happens when manually installing packages because its up to you to keep track of dependencies. From the page that i linked those methods involve creating a list of all the dependencies that need to be installed with the package, downloading them from another machine, and then installing them on the original one. Ive never tried them but i would assume it could help your issue. also i dont think you should be installing busy box, thats usually for stripped down systems. The conflict is from trying to replace a core binary with one from busybox. also just found this https://askubuntu.com/questions/503397/how-do-i-install-wpa-supplicant-on-an-offline-server