4 ms·

https://bugs.launchpad.net/bugs/1966800 https://bugs.launchpad.net/bugs/1966800 looks like a potentially related Ubuntu bug, although the underlying bug is in s

by dgl 4y ago

https://bugs.launchpad.net/bugs/1966800 https://bugs.launchpad.net/bugs/1966800 looks like a potentially related Ubuntu bug, although the underlying bug is in systemd. The commit that fixed it was in 2021: https://github.com/systemd/systemd-stable/commit/a8b66ca9af811148b67ee952ab32748f88b8bba3 https://github.com/systemd/systemd-stable/commit/a8b66ca9af8... The Ubuntu bug is from 2022. Curious that proxmox is hit in 2023. Proxmox must happen to have a particular systemd timer event setup by default that triggers this.

throw0101b 4y ago
Proxmox runs Debian under the hood. Proxmox 7.x is based on Debian 11.x: * https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_7.0 https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_7.0
- happymellon 4y ago
  This is just another one of those reasons I just can't use Debian responsibly. Backport hacks always come back to bite you in the end when your distro is running unsupported software, and it feels like I see something at least annually about Debian's "ensure everything is old so all bugs are predictable" ends up just causing pain.
  - pas 4y ago
    It's the same for every distro. Millions of 5+ year old Ubuntu LTS boxes everywhere. End of life this April. And predictably people will just double down, and keep using an unsupported thing, because upgrades are scary/hard/etc.