1. Copy 1Gb movie to flash drive, says it's done in 10 seconds. Try to remove the flash drive, still in use. Turns out it's actually still copying.

This ia not distro related but GNU/Linux and a known "issue" for over a decade ! Everything gets into you ram memory and gets dumped from there into your USB storage device.

watch grep -e Dirty: -e Writeback: /proc/meminfo

unix.stackexchange.com/questio…

Solving the USB drive/mass storage stall issue

Sadly the issue reported and described here: Pernicious USB-stick stall problem. Reverting workaround fix? and Is "writeback throttling" a solution to the "USB-stick stall problem&qu...

^{Unix & Linux Stack Exchange}

Thanks for the info.

I tried installing PCManFM-Qt and deleting from there. Works as you'd expect, deletes instantly.

Did you have to add a udev rule or did it work for you out of the box? I'll definitely try it out!

Been using Tumbleweed as well. May I ask if you encountered these 2 issues:

Haven't experienced either of those issues.
Have you tried to isolate KDE in those cases? Not sure how you'd do it with the deletion because there's no Trash for the terminal, but you could try the copy operation and see if your device is still blocked when it's finished in the terminal?

Those are both file operations so they don't strike me as strictly DE-related.

KDE Manjaro running on 4 or 5 of my machines, pure stability. It sounds like a hardware issue.

Here are my suggestions to diagnose this.

Option 1. Setup an ssh server, connect from a second computer (or phone via Termux), execute $journalctl -fe, and observe the journal from your second device when the crash occurs. That should help pinpoint the issue.

Option 2. If you don't have a second device, use a non-gui tty, access via Ctrl+Alt+F1. (Usually terminals are available F1 thru F6). Once again execute $journalctl -fe and observe it during the crash.

Tbh option 2 may just be easier especially if you have minimal knowledge of ssh. Good luck, ping me back if you find this helpful and would like more perspective, and apologies if this doesn't help you.

If the entire computer crashes, boot into a terminal and browse journalctl history of previous boots, sorry I don't have these commands off the top of my head but if you need them and ask I will get them for you.

Thanks! I'll try that out today!

Why quotation marks? Issue is an issue, decades or days old. 😄

Copying mechanism itself isn't an issue here; false reporting that something is done when it's not is.

The question marks are because I read somethere that Linus himself doesn't see it like an issue by itself but more like a feature? And that's why it hasn't been resolved for soo long ! I can't exactly remember what he said but that's the gist !

But I do agree, I also see it as an issue :/ and most people who aren't aware probably fucked up some USB sticks that way...

I think Linux nerds are clowns who don't understand that not everyone wants to learn what -xvf means just to extract a goddammed file.

Kde is solid and requires zero fuckery in my experience to work well. This is in fedora, suse, arch (endeavour), void.

KDE just works on my machine, which is lower specs than yours. I've never had it crash. I use Endeavor OS, so it came with it by default (which was part of the reason I chose it).

Edit: I don't do much tweaking of the KDE settings other than the main color scheme. I also have never had an issue with waking from sleep on Endeavor (but I recall in years past that was an issue with most distros I tried and unrelated to KDE since I was less a fan of its style back then and didn't use KDE). My set up is a normal desktop PC that I use daily for everything, including gaming.

It's an issue according to any UX pattern. If something says that it's done when it's not, it's misrepresenting the state of the action.

Hard to believe that modifying the counter to include the necessary time for actual writing to the flash drive would break everything. Target flash drives only etc.

System functioning as intended doesn't mean that it's a good UX.