Audio still broken
▲ 714 r/linuxsucks+1 crossposts

Audio still broken

I fight with this for a month already. I regret connecting Debian server to my TV "to have my own smart TV". If you don't believe me look up this crap online and see ridiculous amount of threads which are as old as 6 months, or 12 years

Edit: the audio randomly starts and stops working after reboot. No matter the drivers, DE, kernel parameters... Once HDMI disappears from outputs, once it exists but doesn't play any sound, once aplay plays sound but pipewire doesn't, and the same issue happens on 2, independent computers. I am glad it works for you - for me and big amount of people it doesn't.

u/al2klimov — 1 day ago
▲ 222 r/linuxsucks+1 crossposts

Telling Linux users to “go Mac” for reporting GNOME bugs is exactly the kind of attitude that hurts desktop Linux

u/al2klimov — 4 days ago
▲ 150 r/linuxsucks+1 crossposts

Interestingly long list of 9.8 scoring CVEs Today

https://github.com/CVEProject/cvelistV5

  • CVE-2026-53309
  • CVE-2026-53260
  • CVE-2026-53247
  • CVE-2026-53246
  • CVE-2026-53228
  • CVE-2026-53221
  • CVE-2026-53216
  • CVE-2026-53215
  • CVE-2026-53176
  • CVE-2026-53175
  • CVE-2026-53151
  • CVE-2026-53088
  • CVE-2026-53086
  • CVE-2026-53055
  • CVE-2026-53049
  • CVE-2026-53046
  • CVE-2026-53045
  • CVE-2026-53010
  • CVE-2026-53006
  • CVE-2026-53002
  • CVE-2026-52993
  • CVE-2026-52989
  • CVE-2026-52986
  • CVE-2026-52955
  • CVE-2026-52931
  • CVE-2026-52924
  • CVE-2026-52914
  • CVE-2026-46325
  • CVE-2026-46289

And updates to some older ones:

  • CVE-2026-52982
  • CVE-2026-46195
  • CVE-2026-45972
  • CVE-2026-45898
  • CVE-2026-43501
  • CVE-2026-43198
  • CVE-2026-43125
  • CVE-2026-43038
  • CVE-2026-43037
  • CVE-2026-31607
  • CVE-2026-31402
u/al2klimov — 5 days ago
▲ 450 r/linuxsucks+1 crossposts

Logging was wearing out my SSD

Just a reminder for amateurs like myself to check on journald, my elderly SSD has been wearing faster than it should and I just realised a Jellyfin process has been crash dumping every second for the last year. Journald was logging about 1.6GB per hour as a result, or around 14TB of writes a year. Nearly a terabyte per day. Whoopsie

Edit:

Didn't notice jellyfin crashing because I switched to plex. 14TB isn't a lot in the scheme of things but my old Evo 960 was nearly at 4x expected TBW so this possibly pushed it over into failure/noticeable performance loss.

I used iotop to figure it out then viewed journald live with journalctl -f

EDIT 2:

So I looked back through the SMART logs and the SSD has been writing nearly a F*CKIN TERABYTE EACH DAY for at least the last six months. How you might ask. Well systemd-coredump is doing a ~250mb write for every crash, however I couldn't see it in iotop because it's too fast - the coredump process starts and exits too quickly to see most times at the default refresh rate. Because of the fast NVME write speed it takes place in much less than a second. If I set the iotop refresh manually to 0.1 seconds you start to see it. No wonder its been running warm! WHOOPSIE

reddit.com
u/Tashi999 — 7 days ago
▲ 156 r/linuxsucks+1 crossposts

DirtyClone (CVE-2026-43503): The Linux Kernel Flaw That Leaves No Trace

On June 25, 2026, JFrog Security Research published a working exploit walkthrough for a Linux kernel privilege escalation they named DirtyClone. Tracked as CVE-2026-43503 with a CVSS score of 8.8, it lets any local user on an unpatched system escalate to root — and the attack leaves nothing on disk for forensic tools to find.

https://blog.kalfaoglu.net/posts/2026-06-28-dirtyclone-cve-2026-43503-linux-lpe-en/

u/Grumpy-Man19 — 7 days ago

Oh, you "don't have to use the terminal"?

Well, except you're on Fedora with a slow af WiFi. Then your graphical updater may just fail to download everything. In contrast, `dnf upgrade --offline` worked for me.

reddit.com
u/al2klimov — 9 days ago
▲ 8 r/linuxsucks+1 crossposts

Oracle Linux didn't restore all my RAIDed partitions after upgrade - legacy_async_del_gendisk error (Solved)

I upgraded my Oracle Linux 9 server today which included an update to the UEK kernel from 5.15.0-321.202.5.1.el9uek to 5.15.0-321.202.5.2.el9uek and an update mdadm, going from 4.4-2.0.1.el9.x86_64 to 4.4-4.0.1.el9_7.x86_64.

This update failed to assemble some of my RAID partitions, with the error: mdadm: Can't open /sys/module/md_mod/parameters/legacy_async_del_gendisk

Looks like the big O failed to properly incorporate some patches into their "unbreakable" (sic) kernel.

The fix for me was to boot into the newest RHCK kernel on the system, 5.14.0-687.5.3.el9_8.x86_64. Once I did that, all my filesystems were available and everything's running as expected again.

reddit.com
u/12stringPlayer — 13 days ago