We are not Adobe scumbags. We actually care about your input.
Please share your ideas:
👉 https://blogs.kde.org/2026/06/20/kde-goals-call-for-submissions/
We are not Adobe scumbags. We actually care about your input.
Please share your ideas:
👉 https://blogs.kde.org/2026/06/20/kde-goals-call-for-submissions/
Yes this is absolutely how Linux operates, but it’s embarrassing and primitive, and it’s actually decidedly a bug.
I haven’t done much programming for many years, but you used to be able to see if you went a step deeper into the file system operations, whether the file you are copying still has parts in cache.
Just because nobody does it, doesn’t mean it’s not a bug.
There is no sense in showing a progress bar that is wrong anyway.
It’s not a bug, just a difference in prioritization. It makes more sense for a server and less for a desktop with removable devices
How is it not a bug? The info shown is decidedly wrong!
Would it also not be a bug if your weather app shows freezing 8 C° tomorrow when it’s going to be 40 C°?
Because there’s a perfectly understandable explanation, that they only count to 32 because temperatures didn’t get higher than that 30 years ago, so it counts down from zero when it’s above 40, because that’s how we’ve done it for years.
Just because you know why, and it’s a little bit cumbersome to do it correctly doesn’t mean it’s not a bug.
It’s not only a bug, it’s a lazy ass bug.
If it’s lazy then the fix should be easy, right? Send a PR