First, thanks to Amazon for not letting me watch the UHD Hobbit I bought from them in full quality unless I use their app on a smart TV / Android / etc. On Linux, Windows, or macOS in a browser you get a low-resolution, low-bitrate stream because… honestly I have no idea why.
Screw you anyway, Bezos.
But I like to actually own the things I buy, so life found a way and I ended up with my film in proper UHD — around 100 GB. I wanted to move it to my external M.2 drive to bring over to a friend’s place and watch together. And that’s where the fun started.
Across several drives (Samsung PM991, WD 2TB), different USB-C / Type-A ports, and two different enclosures (UGREEN w/ JMicron JMS583, ORICO w/ Realtek RTL9210B), write speeds were abysmal — a brief ~1 GB/s burst for the first ~13 GB, then a collapse to ~100 MB/s, or as low as ~40 MB/s. There’s one culprit I ruled out before getting to the actual point, because it muddies these reports and people will bring it up:
The UGREEN’s JMicron JMS583 bridge has broken UAS firmware under Linux — it reset-storms under sustained writes (uas_eh_abort_handler / reset SuperSpeed looping in dmesg), which tanks speed. I had to manually disable UAS via a kernel quirk (options usb-storage quirks=152d:0583:u) to stabilize it. That’s a JMicron problem, not KDE. With a proper data cable and the quirk in place, lsusb -t confirmed the device on a 10000M bus — full 10 Gbit/s, stable.
Here’s the part that is on KDE. After fixing the link and the bridge — confirmed 10 Gbit/s, confirmed stable — the speed was still garbage in Dolphin. So I benchmarked properly. Raw dd with oflag=direct (bypassing page cache entirely) copied the actual 100 GB file at 579 MB/s sustained, dead flat, no cliff. An 80 GB synthetic write held 725 MB/s.
Then I copied the film’s file with every file manager I came to mind:
| Tool | Time / effective speed | Backend |
|---|---|---|
| Thunar | ~1 min | GIO/GVfs |
| Nautilus | ~1 min | GIO/GVfs |
| Nemo | ~1 min | GIO/GVfs |
| PCManFM-Qt | ~1.5 min | thin/GIO |
dd (oflag=direct) |
3 min / 579 MB/s | raw syscalls |
| Dolphin | many minutes / ~40–300 MB/s | KIO |
And as I’ve discovered this isn’t new. The same complaints show up in Google going back over a decade - 2014. KDE’s own bug tracker has it as an open issue — [LINK: bug #402276, “Dolphin transfer speeds moderately slower than other file managers,” still open, last touched Jan 2026].
Baloo and KIO in general have a notorious reputation for terrible performance.
The sad part is that I genuinely love Dolphin. Functionality and UI/UX-wise it’s my favorite file manager by a mile — the thumbnailing alone (it’ll generate a preview for damn near anything) is best-in-class in my opinion.


