Welcome to a new issue of "This Week in Plasma"! Every week we cover the highlights of what's happening in the world of KDE Plasma and its associated apps like Discover, System Monitor, and more.
File transfer progress bars generally aren’t worth shit, I have no idea how this is still a problem. It dates back to the early 90’s, and it’s still not done properly.
Almost everything to do with file transfer report it to be finished before it actually is, because it doesn’t consider write back cache. So it’s only the reading part that is finished, not the writing part. Meaning the transfer isn’t actually finished.
Never never never trust it is my motto. Personally I’d rather not have the dysfunctional progress bar, if I could have an actually accurate completion notification.
PS: I just switched back to KDE/Plasma after many years. Overall I’m pretty pleased, but also a bit puzzled about a lot of the simplifications.
like inability to disable caps lock, and the inability to change double click speed for the mouse. So now I need a startup command for the caps lock, and I needed to edit an ini file for the mouse for such simple things, that used to be accessible through settings???
But they finally added the ability to use numpad for hotkeys, which I found out, and was what made me switch back to KDE. Now I only miss the ability to use the scroll wheel on hotkeys too. To finally have similar functionality like I had 10-15 years ago with Compiz. 😜
very noticeable and annoying when transferring to slower media like usb sticks, sometimes it takes tens of minutes to unmount after copying a large file because its actually still writing.
i bet MANY people are left with halfway stuff written on their usbs after being in a rush and removing it insecurely on linux after the transfer is “done”. this should absolutely NOT be a thing.
i bet MANY people are left with halfway stuff written on their usbs after being in a rush and removing it insecurely on linux after the transfer is “done”.
AFAIK it can actually destroy the USB if it’s removed while being written.
You can use sync in terminal. But it’s tricky because it sometimes returns even when the writing isn’t finished.
My method is to use sync multiple time, if it returns immediately 2 times it should be clear,
Only then do i dismount the stick, because I don’t like to dismount a device with pending operations.
But when the dismount says the stick is ready to be removed, you should be clear.
What annoys me is that this was an issue as far back as the early 90’s. On DOS and Windows 3.11. It’s such an annoyance that I don’t get how this problem still exist?!
If the unmount function can see if write is finished, a file copy function should obviously be able to see it’¨s own copy state.
File transfer progress bars generally aren’t worth shit, I have no idea how this is still a problem. It dates back to the early 90’s, and it’s still not done properly.
Almost everything to do with file transfer report it to be finished before it actually is, because it doesn’t consider write back cache. So it’s only the reading part that is finished, not the writing part. Meaning the transfer isn’t actually finished. Never never never trust it is my motto. Personally I’d rather not have the dysfunctional progress bar, if I could have an actually accurate completion notification.
PS: I just switched back to KDE/Plasma after many years. Overall I’m pretty pleased, but also a bit puzzled about a lot of the simplifications.
like inability to disable caps lock, and the inability to change double click speed for the mouse. So now I need a startup command for the caps lock, and I needed to edit an ini file for the mouse for such simple things, that used to be accessible through settings???
But they finally added the ability to use numpad for hotkeys, which I found out, and was what made me switch back to KDE. Now I only miss the ability to use the scroll wheel on hotkeys too. To finally have similar functionality like I had 10-15 years ago with Compiz. 😜
Yeah I learned that the hardway when comparing MacOS/linux USB speed…
Took like “seconds” on Linux. I looked quite dumb asking a question and asking for help on Lemmy while shitting (again) on my Mac !
I have somewhere in my notes a command to show interactively how the memory cache gets dumped into my USB stick.
Kinda boggus that’s an over 20 years old known “issue”.
GNOME does exactly the same thing.
very noticeable and annoying when transferring to slower media like usb sticks, sometimes it takes tens of minutes to unmount after copying a large file because its actually still writing.
i bet MANY people are left with halfway stuff written on their usbs after being in a rush and removing it insecurely on linux after the transfer is “done”. this should absolutely NOT be a thing.
AFAIK it can actually destroy the USB if it’s removed while being written.
no way to know for sure if its still writing if the progress bar is inaccurate.
You can use sync in terminal. But it’s tricky because it sometimes returns even when the writing isn’t finished.
My method is to use sync multiple time, if it returns immediately 2 times it should be clear,
Only then do i dismount the stick, because I don’t like to dismount a device with pending operations. But when the dismount says the stick is ready to be removed, you should be clear.
exactly. thats unnecessarily complicated for someone on a rush because of something that should be a functional progress bar.
What annoys me is that this was an issue as far back as the early 90’s. On DOS and Windows 3.11. It’s such an annoyance that I don’t get how this problem still exist?!
If the unmount function can see if write is finished, a file copy function should obviously be able to see it’¨s own copy state.
I’m pretty sure you can disable caps lock (or at least rebind it)
I currently have caps lock rebound to backspace. Maybe it’s a Wayland only feature and you’re using x11? idk
I’m using X11 so that could be. I just don’t get why it would be different between X11 and Wayland?
I’m not entirely sure. It could be similar to HDR support (only available on Wayland), but I would need to look into it to be completely sure.