Here's a Flatpak story: The other day, my best friend told me that he had switched to Linux! Arch Linux with KDE Plasma, a noble choice in my opinion. He's a smart guy, but he was having some issues that he couldn't figure out: Firefox' maximise and minimise buttons were missing, drag and drop from archives wasn't working, his selected theme wasn't applied everywhere, and many other small issues I can't remember now.
I tried reproducing his issues on my machine, but everything worked fine for me. We were confused. Is there missing libraries? We went through packages to find out what my system had that his didn't. It was weird, everything was kinda working, but the devil was always in the details, for every single app.
And then we found it: All those applications he had issues with were Flatpaks! He simply didn't pay attention when installing them through the Discover store. He didn't even know what Flatpak meant.
I helped him remove Flatpak from his system and install the system packages instead, and all issues were gone.
Man, Flatpaks suck. How does anyone prefer Flatpaks over system packages? How does anyone think this was a good idea? Stop trying to invent new things to solve old problems and instead go back and fix the problems.
Containers, Flatpak, Immutable distros, it's all wasted effort. There is no magical solution that will solve all our problems. The only way to solve all problems is by solving each problem individually one by one. And that is exactly what countless distribution and package maintainers are doing on your behalf every single day.
@nixCraft if thats the case, than for me my last Weekend was the "Weekend of the Linux-Desktop" (on my Laptop) but even that was just because I tried to do too much of the basic plumbing on my new #arch install without helpful scripts or installers - as soon as I gave up and used the script "archinstall" even audio and video drivers didn't create any hazzle. 😄
Looks like I'll shortly need to decide what OS to put on my #Framework 16 :)
Likely I'll go back to #Arch, but I'm tempted to try #Alpine for the first time. I do need to be able to install zoom though, which looks like it might be a challenge on alpine?
Why does plymouthd do this moments after boot starts?
It displays the mobo logo and the spinner for a second or two, then that screen disappears and does this. It stays like this for 5 seconds or so then puts me at sddm login screen just fine.