I loved the glorious 3.5.x days. What a fantastic DE it was then. I compiled 3.5.0 from source when it was released because it was going to take the Fedora guys too long to package.

This is great! The first one was a lot of fun.

I can’t believe they’re up to 40. I remember installing Fedora Core 1 like it was yesterday. Yum (and now dnf) has come a long way. It used to have to individually retrieve metadata files for every available package, rather than using a single compressed index of all the packages available in the repository you were using. It made just getting to the stage where dependencies were calculated take forever.

Good riddance.

A bad SATA cable will cause this too.

I don’t do much scanning, perhaps 5 times a year, and it’s sufficient for my needs. I can definitely see how it leaves gaps if you do a ton of scanning.

Any SANE front-end will do. I usually use xsane.

I have a Brother MFC-L8900CDW and it works great for printing and scanning on Linux (I use Arch BTW). I use SANE for scanning. You can also set it up to scan to a Samba share or ftp location.

I’m pretty sure the Linux support was on day one. I was running Linux back then and played it quite a bit and it worked great.

I dumped Chase over a decade ago for a local credit union. It was a great decision. Jamie Dimon can burn in hell.

Definitely not from the team working on search on Windows then.

They didn’t make it the default until 2021 https://fedoramagazine.org/announcing-fedora-34/

Keep bugging them. I almost exclusively use signal for messaging these days and it’s fantastic. It took longer to convince some people than others

Use the pacrepairfile utility and you can set them to the distro shipped permissions easily https://man.archlinux.org/man/pacrepairfile.1

Not with modern package management systems. In the pacutils package is the pacrepairfile tool that is specifically made for repairing file permissions https://man.archlinux.org/man/pacrepairfile.1

Awesome! Enjoy!

Here’s your issue. Your selinux contexts are bad so you’re probably being denied access to your own data. To reset the contexts back to normal you can use the restorecon command:

restorecon -Rv /home/

The -R tells it to go through the specified path recursively, the v tells it to be verbose in the output and show you what it’s doing.

I used to have to occasionally run this but I’d say it has been at least a couple of years since I last had to. I was a pretty early adopter of pipewire because it solved some Bluetooth issues that pulseaudio had. It has improved immensely since I first started using it.

fuckspez

It didn’t work