Drivers are on the computer, firmware is in the component. Firmware can be updated in both windows and Linux and will affect both systems. Drivers live solely on the OS, so fedora drivers will not be affecting windows. There’s an incredibly small chance that your firmware was updated and caused this, but I don’t recall a firmware update ever occurring automatically on Linux, I’ve always had to do it manually.

Libreoffice, OpenOffice was abandoned when oracle bought it

I’m in new mexico and saw a badger crossing the road while I was driving to work. It stopped in the middle of the road, turned towards me and waited, like it was deciding whether or not to fuck up the large metal thing coming towards it. Then slowly turned and continued on it’s way when it decided I wasn’t worth it. No fear whatsoever.

I used both tumbleweed and leap for a bit and they really are good. I’m actually using tumbleweed on a home server right now and it’s been a champ. But…

1. My biggest gripe is opensuse seems to use different package names than any of the other distros for basic packages. I had to install a package that used capitals in the package name, and coming from mostly debian based distros, that made me rationally angry when trying to find the package I needed. I think it was network-manager or something that’s usually installed by default and I wanted something familiar.

2. Online directions for setting something up usually has deb and/or fedora rpm directions, which is usually just some difference in package names and the equivalent install command, searching the base package will let you figure it out. I had very few issues following debian/Ubuntu directions and translating them for fedora. Opensuse is always non-existent so you always need to translate those directions for opensuse, which is usually like doing it for fedora until you run into point (1).