There's a lot of things this can be but you need to rule out the possibility that your system is experiencing a hardware issue. It's the type of thing that if you don't get on top of it right away you can experience data loss. Check /var/log/syslog
for disk/SMART errors ASAP.
Here's how to check the SMART status of your drives... Install some SMART-checking packages:
sudo apt install libatasmart-bin smartmontools
Now run this command for every disk you've got:
sudo skdump /dev/sda # Replace sda with your disk(s)
This is what you're looking for:
SMART Disk Health Good: yes
If you want more details about the status of your drive you can use smartctl
:
sudo smartctl --all /dev/sda
Though honestly, unless you really know what you're doing that output isn't usually as helpful as skdump.
There's a few other more mundane things that can really slow Dolphin down:
- A directory with a ton of files in it. So if restores the last open tabs when you open it and one of those directories has a ton of files... There ya go. Change the tabs to stuff that's quicker to open and close Dolphin so that next time it'll open fast. Alternatively, just configure it to "Show on startup:" your home directory instead of restoring the last session's tabs.
- A network-based KIOslave/remote directory that's currently down or just has a lot of files in it (or is just generally slow like some webdav thing). Same sort of problem as the last bullet.
- It's opening a directory with lots of files that can have thumbnails/previews that aren't getting cached (or can't be cached or the cache is being regularly deleted). Normally Dolphin generates previews in the background while you're looking at any given directory but if it thinks there's cached previews/thumbnails for a large directory of files and all those files are now missing that can really slow it down.
Another thing to check: Instead of opening Dolphin from the menu/launcher open up a terminal and just run dolphin
. That way you'll get to see any warnings/errors as they occur while you're using it. You can ignore most QT-related warnings/errors like, "BadWindow". Look for words like, "timed out" or "timeout" as that can be a smoking gun.