https://bugs.kde.org/show_bug.cgi?id=508845
--- Comment #7 from stellarpower <[email protected]> --- (In reply to Andrius Štikonas from comment #6) > (In reply to stellarpower from comment #5) > > So even for e.g. security patches, are you saying it's up to the package > > maintainers to cherry-pick lines and merge those in? There aren't occasions > > where something is severe enough to go back to previous branches and cut a > > new release for downstream to take up? Just wanting to understand if that is > > the case as this would differ from some other projects. > > Right now Partition Manager is part of automated KDE Gear yy.mm.patch > release schedule, so you only have the standard monthly or so releases. Once > yy.mm.3 release is out, there wouldn't be any releases of that branch. I > think it's technically not even possible because we wouldn't even have a > corresponding translation branch (at the moment translations are in SVN and > there are master and stable branches there). > > Anyway, even before that, when KDE Partition Manager had standalone > releases, I once created a bugfix release of current stable branch that > fixed security bug with an assigned CVE. Luckily that bug didn't affect any > of the earlier versions. All the distros either took a patch that fixed CVE > or a new release except for Ubuntu. Still not fixed there > https://bugs.launchpad.net/ubuntu/+source/kpmcore/+bug/1903774. Ubuntu 20.04 > still has that local root privilege escalation. So given that you are on > Ubuntu derivative, new releases won't help you, I don't think they care. > > fsck for 24 hours seem excessive... But again, it's unlikely that --repair > causes it. If it's stuck, most likely just simple btrfs filesystem check > would also get stuck. But unless your disk was already corrupted, I don't > think killing btrfsck process would do any harm. I see. The declining stability of Ubuntu is one reason I switched, as if the packages aren't tested thoroughly then I thought I would try a semi rolling-release as if it's gonna have bugs at least I can update easily and it might be fixed. In the meantime I managed to attach ptrace and once a minute or so I can see it's writing something and doing a sync. I've seen other threads mentioning taking a week or well over that to do a full repair, presumably these are much larger datasets but I don't know by how much. I can go and trace through the code but should any output from it be displayed immediately in PM? It should have spat out something on starting but the window is completely empty, not sure if it's buffered, or that is an issue that has since been fixed, or if it really is just spinning very early on. -- You are receiving this mail because: You are watching all bug changes.
