KDE developer Méven Car has resolved a 15-year-old bug in the KIO framework that caused file copy progress bars to inaccurately report completion while data remained in RAM. This issue, originally reported in 2011, particularly affected removable and network storage, as the system prematurely deleted source files after declaring a copy complete. The fix, included in KDE Frameworks 6.32, improves accuracy by implementing an adaptive writeback window that ensures progress bars reflect actual data transfer to storage devices. While the update is significant for users of removable and network storage, it does not alter the behavior of local disk copying

KDE Fixes 15-Year-Old File Copy Bug That Lied About Progress

KDE developer Méven Car has fixed a 15-year-old bug in KIO, the I/O framework behind Dolphin, that made file copies report completion while data was still sitting in RAM instead of on the device. Filed in 2011 as bug 281270, it grew worst of all because moves deleted sources prematurely, prompting a solution built on sync_file_range() and an adaptive writeback window that keeps copies honest without slowing them down. The work ships in KDE Frameworks 6.32, scheduled to release November 13, and mainly benefits removable and network storage while leaving local disks untouched. It's a quiet but meaningful win, delivering a progress bar that finally means something rather than a shiny new feature.

KDE Fixes 15-Year-Old File Copy Bug That Lied About Progress @ Linux Compatible