Comm: wpa_supplicant being the wifi function makes me suspicious of your wifi hardware as well before I saw the rest of your post. I’ve had the best success with PCIe based wifi cards (if this is a desktop pc)
Agreed, this wifi stick was mega cheap on AliExpress so I went for it. I may take a look at the PCB in detail if removing it restores order to my PC. Yes, desktop PC (still hanging on to 2012 hardware woohoo!)
Just Thunderbird is fine for me, has all the features I want and I already get my email there (but even if I didn’t I’d struggle to find an RSS reader with its features).
I self-host FreshRSS as a container with podman behind Traefik on a raspberry pi 5 and use the web interface on desktop and FeedMe on android. Pretty happy with the setup.
Wait what? I’m no fan of Wayland, but what you just said, I’m afraid, is all wrong.
Wayland, although being around for over a decade, is the newer protocol. The older protocol would be X11.
Pipewire is also the new kid on the block, for audio. PulseAudio would be the older one being replaced.
WINE is a Windows compatibility layer or wedge. It stands for Wine Is Not an Emulator, if I recall.
Wayland seeks to provide a newer display standard, as I keep being told (forcefully and repeatedly) X11 is not sustainable… There’s a lot about that we don’t need to rehash here, but long story short, In with the new (Wayland), and sooner or later, out with the old (X11).
Pipewire is meant to be a replacement for PulseAudio, and near as I can tell, quite backwards compatible.
WINE is to run Windows application on Linux. Like many Linux applications right now, it is being updated to support Wayland (I believe that’s well underway already) and it already works fine with Pipewire. WINE will work on X11 and Wayland.
Lastly, what do you mean by weaker systems? X11 is weak when it comes to being security conscious. Part of Wayland’s mission is to address that by being far more secure by default. Pipewire, while maintaining backwards compatibility, is able to do more things, as well, than the original PulseAudio.
I don’t like Ubuntu because of their forcing method to use Snap package manager.
I don’t like Manjaro because of its poor dependency management. Many dependencies are not declared, so that if you update a package, it won’t update the undeclared dependency and it won’t work any longer. You have to update everything or nothing, and when disk space becomes low, updating everything at once is impossible.
partial upgrades on distros without hard linked dependencies is a disaster caused by the user.
You should never have a system with less than 20% free space, but I mean system, not /home, not /var/cache/ of /var/cache/pacman,
Make partitions and mount things separately, especially /home
In a pinch you can live without man-pages remove /usr/share/{doc,man,html}/*
and on /usr/share/locale/* keep just the ones you use
I assume that Manj follows #Arch and doesn't improvise on sys dependencies. Definitely not poor.
Arch-archives by date, means you can build a system exactly as it was fully upgraded on a specific date, and the system works just like it used to.
Other systems that may carry 3 versions of the same library because different sw use different versions are the ones with the problem. Except for redundancy and space the system is not very coherent..
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.