Focus might be a bit much,
I only have a single feature wish, and that is to have file copy operation progress show correctly.
As it is, if I copy a few gigabytes to an USB stick, it very quickly shows as finished.
But it can take up to a couple of minutes before the operation is actually finished, and the stick can be unmounted and removed.The easiest way to check I know of, is tom open a terminal and simply use sync. And it seems immensely primitive to me that I have to do that.
This is an age old problem for copying files that began to occur on PC systems way back around 1991, when write cache became a thing for disk operations. And honestly it makes me sad that this problem still isn’t solved now 35 years later. 😥
Otherwise I think KDE is doing great with their desktop, except I think it should just be called KDE desktop, and not that other thing they call it now.
I don’t think this is a KDE problem, but more the way Linux operates. I looked into this once and it’s basically because Linux considers the operation done when the source file is completely read and committed to the destination, but not actually written yet. I see this same behavior with my USB backup drives where something finishes but then I have to wait a minute or two when actually unmounting the drive. I think there’s a way to change this but I’ve never done it.
P.S. I just want KDE to make activities great again :(
Wow, I’m really glad this topic came up. As a recent convert from Windows, it’s still muscle memory for me to yank out a flash drive as soon as the copy dialog completes. (Yes, I know ejecting a drive first is still the proper thing to do on Windows, but skipping that has not been an issue once in hundreds of cases.)
A simple
syncwould show you when it actually finishes. However, it has system-wide effects. Perhaps KDE could lobby for a similar action to become available that is limited to e.g. a specific process id?I would settle for checked-by-default “sync and wait” option. That way I can choose whether to cause a sync or not.
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
I know this is a weirdo hope, but I personally would wish to see KDE take a more clear stance against LLM code submissions, and to move away from relying on systemd so much. But I suppose most regular users would prefer more tangible features and changes.
Do they still do 15 minute bugs? That could still use some work.
Occasionally I get an itch to try Plasma and immediately get disappointed every time as I encounter some sort of bug just setting up the panel. Last time I tried was 6.6.5, so it wasn’t just a point 0 software issue.
As a side note, I still get so confused by the “new” panel/desktop edit mode introduced in 6.1.
Anyone passionate about KDE and has a vision to share is welcome to submit a proposal.
i’m out.
