<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/kde-fixes-15-year-old-bug-over-inaccurate-notifications-when-copying-files-to-usb-drives-xa6z0pyhc" -->

---
title: KDE Fixes 15 Year Old Bug Over Inaccurate Notifications...
description: KDE Frameworks 6.32 fixes a 15 year old bug that made file copy notifications to USB drives inaccurate. The desktop previously reported copies as complete once...
canonical: https://daily.dev/posts/kde-fixes-15-year-old-bug-over-inaccurate-notifications-when-copying-files-to-usb-drives-xa6z0pyhc
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: KDE Fixes 15 Year Old Bug Over Inaccurate Notifications When Copying Files To USB Drives | daily.dev
og:description: KDE Frameworks 6.32 fixes a 15 year old bug that made file copy notifications to USB drives inaccurate. The desktop previously reported copies as complete once...
og:url: https://daily.dev/posts/kde-fixes-15-year-old-bug-over-inaccurate-notifications-when-copying-files-to-usb-drives-xa6z0pyhc
og:image: https://api.daily.dev/og/posts/Xa6Z0pYHC.png
og:image:alt: KDE Fixes 15 Year Old Bug Over Inaccurate Notifications When Copying Files To USB Drives
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# KDE Fixes 15 Year Old Bug Over Inaccurate Notifications When Copying Files To USB Drives

**[Phoronix](https://daily.dev/sources/phoronix)** · 3 min read · 0 upvotes · 0 comments

## Summary

KDE Frameworks 6.32 fixes a 15 year old bug that made file copy notifications to USB drives inaccurate. The desktop previously reported copies as complete once data hit the local cache, not when actually written to removable storage. The bug report dates to 2011 and gathered 77+ comments and 17+ duplicates. KDE developer Méven Car detailed the fix's long history: Christoph Feck asked about a way to learn when data is on disk, and Alan Stern's answer, sync_file_range(), was passed on in 2011 and called exactly what we need. In 2021 Nate Graham raised the bug to the highest priority because a move deletes the source files while the copies are still in memory. In 2024 Christoph tested the cachestat() call of Linux 6.5, which reports dirty memory only for one file at a time. The eventual fix waits for the writeback of the window before the one just written, which is what makes it work.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://www.phoronix.com/news/KDE-Fixes-15-Year-Old-Bugs>

## Questions this post answers

### Why does KDE show a file copy as complete before it's actually written to my USB drive?

KDE's copy notifications historically reflected only when data reached the local cache, not when it was actually written to removable storage, a bug reported in 2011. This caused moves to delete source files while copies still sat in memory. KDE Frameworks 6.32 fixes it by using the sync_file_range() call to wait for the actual writeback to disk before marking the copy complete.

_Track filesystem and KDE storage fixes like this on daily.dev before they bite your workflow._

### What is sync_file_range() used for in Linux file copy operations?

sync_file_range() lets a program learn when data has actually been written to disk without the performance cost of a full sync call. KDE identified it in 2011 as the right tool for accurate copy-completion notifications, but getting it working correctly took until KDE Frameworks 6.32, since early attempts waited on the wrong write-back window and never actually blocked until the data was flushed.

_Developers debugging storage write-back timing can follow fixes like this one on daily.dev._

## Similar posts on daily.dev

- [KDE Developer Fixing Long-Standing Bug Over Very Long Small-File Copy Times](https://daily.dev/posts/kde-developer-fixing-long-standing-bug-over-very-long-small-file-copy-times-h5lvfafmi) · Phoronix · 0 upvotes · 0 comments
- [Making KIO copy many files fast](https://daily.dev/posts/making-kio-copy-many-files-fast-2txcmavkj) · Lobsters · 0 upvotes · 0 comments
- [Car: Dolphin 26.08 and KIO performance improvements](https://daily.dev/posts/car-dolphin-26-08-and-kio-performance-improvements-c7lwnkvk9) · LWN.net · 0 upvotes · 0 comments

---

Tags: [#linux](https://daily.dev/tags/linux), [#filesystems](https://daily.dev/tags/filesystems)

[View this post on daily.dev](https://daily.dev/posts/kde-fixes-15-year-old-bug-over-inaccurate-notifications-when-copying-files-to-usb-drives-xa6z0pyhc)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"KDE Fixes 15 Year Old Bug Over Inaccurate Notifications When Copying Files To USB Drives","url":"https://daily.dev/posts/kde-fixes-15-year-old-bug-over-inaccurate-notifications-when-copying-files-to-usb-drives-xa6z0pyhc","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/kde-fixes-15-year-old-bug-over-inaccurate-notifications-when-copying-files-to-usb-drives-xa6z0pyhc"},"datePublished":"2026-10-27T17:02:45.334Z","dateModified":"2026-10-27T17:06:31.813Z","description":"KDE Frameworks 6.32 fixes a 15 year old bug that made file copy notifications to USB drives inaccurate. The desktop previously reported copies as complete once...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/b236c4d45a4584b9f6c2d6fb35696e0a?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/b236c4d45a4584b9f6c2d6fb35696e0a?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Phoronix","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Phoronix","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/6a26ba379dd64932830aa0c9803dd7ee","url":"https://daily.dev/sources/phoronix"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/kde-fixes-15-year-old-bug-over-inaccurate-notifications-when-copying-files-to-usb-drives-xa6z0pyhc","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"linux,filesystems","timeRequired":"PT3M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Phoronix","item":"https://daily.dev/sources/phoronix"},{"@type":"ListItem","position":3,"name":"KDE Fixes 15 Year Old Bug Over Inaccurate Notifications When Copying Files To USB Drives"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/kde-fixes-15-year-old-bug-over-inaccurate-notifications-when-copying-files-to-usb-drives-xa6z0pyhc#faq","mainEntity":[{"@type":"Question","name":"Why does KDE show a file copy as complete before it's actually written to my USB drive?","acceptedAnswer":{"@type":"Answer","text":"KDE's copy notifications historically reflected only when data reached the local cache, not when it was actually written to removable storage, a bug reported in 2011. This caused moves to delete source files while copies still sat in memory. KDE Frameworks 6.32 fixes it by using the sync_file_range() call to wait for the actual writeback to disk before marking the copy complete. Track filesystem and KDE storage fixes like this on daily.dev before they bite your workflow."}},{"@type":"Question","name":"What is sync_file_range() used for in Linux file copy operations?","acceptedAnswer":{"@type":"Answer","text":"sync_file_range() lets a program learn when data has actually been written to disk without the performance cost of a full sync call. KDE identified it in 2011 as the right tool for accurate copy-completion notifications, but getting it working correctly took until KDE Frameworks 6.32, since early attempts waited on the wrong write-back window and never actually blocked until the data was flushed. Developers debugging storage write-back timing can follow fixes like this one on daily.dev."}}]}
```

