A few days ago, I was genuinely worried about this release. KDE 6 on Wayland is known for breaking quite a few workflows, so I prepared a checklist in advance of things I absolutely needed to test in Fedora 40 KDE (no X11 by default). You can find that checklist here: https://www.unmanarc.com/en/2024/02/things-to-test-in-fedora-40-kde-no-x11/. Let’s see how things actually turned out.
First of all, I want to clarify that I’m not an audio expert—just an enthusiast—so don’t expect anything too scientific or magical from what I’m about to share. For a long time, I used an old SoundBlaster X-Fi (honestly, nothing special) connected through its RCA outputs and adapted to 3.5 mm. Eventually, I decided to upgrade to a FiiO BTR15 DAC, expecting a clear improvement. To my surprise, with newer and supposedly better hardware, I couldn’t initially reach the audio quality I was used to with the SoundBlaster.
Spoiler alert: this journey turned out to be way crazier than expected. Audio is not always as “plug and play” as one might hope. After digging deeper and carefully reviewing configurations, I finally found a few parameters that made a very noticeable difference in sound quality.
When running OpenVPN in an LXC environment, users may encounter a specific error that prevents the OpenVPN service from operating correctly. The error manifests as follows:
Jan 08 00:56:47 fw openvpn[404]: openvpn_execve: unable to fork: Resource temporarily unavailable (errno=11)
Jan 08 00:56:47 fw openvpn[404]: Exiting due to fatal error
Jan 08 00:56:47 fw systemd[1]: openvpn-client@yourvpn.service: Main process exited, code=exited, status=1/FAILURE
Long-term data retention in storage media is a real and often underestimated problem. Data stored on devices such as SD cards, USB flash drives, and SSDs can slowly degrade over time due to physical limitations of the underlying technology. Factors like age, temperature, humidity, manufacturing quality, and prior wear all influence how long data can be reliably preserved.
There are many discussions about to use or not a password manager. However, most experts agree that you must use a strong password in every system/service (+2fa, but we are not going to elaborate about it today).
This is a simple/short how to for installing VirtualBox 7 in OpenSUSE 15
Here we are handling two problems:
There is no repo for OpenSUSE 15.4 (we need to do a trick)
There is no documentation on how to create proper UEFI secure boot MOK’s (owner keys) for the newer OpenSUSE which demands that the key will have special attributes like “codeSigning“
Most security assessments only includes CVE’s and known vulnerabilities but many fail to address the true potential security risks. And this will create a big problem for your organization.
The problem starts because most organizations only wants to have a security analysis based on know-existent vulnerabilities, like a “tell me what KB to patch”, but this approach is not good and fails to protect you in two ways: