https://bugs.kde.org/show_bug.cgi?id=508845
--- Comment #4 from Andrius Štikonas <[email protected]> --- (In reply to stellarpower from comment #3) > Is there any chance of backporting this change? I'm using a live USB > (LUbuntu 24.04, released 2025-08-05) and now am seriously concerned I've > just killed a partition that was working perfectly fine just because I > wanted more free space. On top of the default checking, there's no output, > it's been running for two hours on a ~500G partition (from GParted or ext4 > it's usually a few-minute job before resizing). The progress is 0% and I see > it using one whole core and a lot of memory in htop but otherwise I have no > idea what it's doing. > > I'm on PartitionManager 23.08.5 and from that tag, the readme says there > aren't any open bugs for anything serious that could cause data loss. > Admittedly the bug won't have been open at the time, but hopefully you see > what I'm saying. Whilst maybe this will end up turning out fine, I'm quite > concerned about severe data loss, and pretty recent distro releases (same > month as the original date of this issue) evidently are shipping a version > of PartitionManager that could be wiping out people's discs. I see some > mention of similarish situations here and just through google where it may > have been attempted through the CLI to worry it's a common enough situation. > Could this issue be considered high enough of a concern to patch that one > line back into older releases and try to get it through different > distributions? Even if you run with --repair it's unlikely to cause any problems, e.g. I never had problems on my system. There is probably a bit of confirmation bias if you search online for it though. Anyway, it's up to distros to make backports. KDE does not do releases from such old branches anyway. -- You are receiving this mail because: You are watching all bug changes.
