Apparently, Prism Launcher chose to adhere to the idiotic principle of the hidden “trashbin”, .Trash-$(uid), invented by Ubuntu. Even though it’s based on QT. This can’t be disabled. It accumulated 139 GB of literal Trash, fully replaceable, over time. Just … why? There’s even an open issue about this, for over a year, referenced multiple times. I guess I have another point on my agenda.
the hidden “trashbin”, .Trash-$(uid), invented by Ubuntu
This isn’t some “idiotic principle invented by Ubuntu”, it just follows the freedesktop.org Trash specification. For many users, it can be really beneficial, see also the spec’s introduction:
An ability to recover accidentally deleted files has become the de facto standard for today’s desktop user experience.
Users do not expect that anything they delete is permanently gone. Instead, they are used to a “Trash can” metaphor. A deleted document ends up in a “Trash can”, and stays there at least for some time — until the can is manually or automatically cleaned.
Whether an application like Prism Launcher should use the trash can or delete the files directly is an entirely different question.
and proper trashing is actually really helpful, so you can trash files on encrypted volumes without leaking them to a unencrypted trash dir.
trashing saves time and has a more continous workflow, as you don’t have to confirm each file to prevent accidents, because you can restore if you deleted too much
But why wouldn’t they use .local/share/Trash instead? Isn’t that supposed to be a unified directory for that very purpose?
Because that would take a long time if you deleted a large file in another partition or drive. You could also end up not having enough space to move the file to trash and if the trash directory is on an SSD, it would add a lot of unnecessary wear to it.
To explain it a bit further: when you move a file/directory on the same mount point, moving the file/directory is essentially just a rename operation, which doesn’t involve copying the data itself and is a very cheap operation. If you move a file/directory across mount points, you need to (recursively) copy the file/directory, copy file metadata and (recursively) delete the old file/directory, which is slow and error-prone.
This isn’t some “idiotic principle invented by Ubuntu”, it just follows the freedesktop Trash specification
So an idiotic spec invented by freedesktop then
Maybe checkout kdirstat (gui) and ncdu (tui)
I use ncdu. It shows what folders/files are actually eating up all your space.
I was about to suggest this. It comes with a nice TUI that sorts by highest disk usage.
Neat! I kept using du and df and work my way to the culprit. On PC’s with GNOME I use baobab.
I’m more of a dust man, myself. It runs recursively so it’s easy to pinpoint the culprit.
[Image source: the project’s README]
Doesn’t people use a disk usage scanner every once in a while to find out if there’s something hogging space?
If you have 4 TB disk, you don’t care until it is getting full.
I do, because it is the same with a 4 TB disk and 100 GB games as it is with a 256 GB disk and png’s & office stuff.
I have several 4 and 8 TB disks filled up with various stuff just waiting to be cleaned up. Why do you think I’m preaching about storage space management?
My dual 10’s are starting to fill up because I don’t move stuff off-site as I should. And then reclaiming space through disk analyser and freeing up reserved space is a life saver.
I do, except I always used du -hs *, which does not include hidden (.-Prefixed) files. So a double trap.
shopt -s dotglobwill make*include .dotfiles.
Your desktop environment should have settings for when to clear the trash. You can also use autotrash to clear it automatically.
The Problem is: I don’t have a DE, and therefore didn’t realize programs would still try to use trashbins.
I use command
trash-emptyto empty all trashcan of all the users, after each system update. It’s a non standard program, but most likely available in your distributions repository: https://github.com/andreafrancia/trash-cli And my alias/function will show each file that is about being deleted (just put it in .bashrc, if you have installedtrash-cli, which includestrash-empty):old function (click to expand)
empty() { echo "Files to delete:" trash-empty -f --dry-run | awk '{print $3}' | grep -vF '/info/' echo trash-empty }Edit: After I posted I just realized there is a more straightforward way of doing it:
New and more simple alias:
alias empty='trash-empty -f --dry-run ; trash-empty'This searches all trash cans, lists all files it has found to be deleted, then lists all directories it looked under and then asks if you want really delete. With
trash-empty -fit deletes without asking.All .Trash-1000 files appears in your trashbin no? At least is how is working for me.
ncduIsn’t it common that file managers have a trash bin? Thunar does.
@30p87 @hyperreal ncdu is great for that
I did this yesterday while trying to make a backup before formatting and then updating my work rig and I’m SO GLAD that the decades have taught me to take knee-jerk/automatic actions that forces me to make entire volume backups; otherwise this last month of work life would have been AWFUL!!!
You can easily set it up to do this automatically with something like timeshift…
I recently switched to an Atomic distro (Bazzite), and they have made it so easy to rollback to previous commits without any additional software.
I use rsync on a cron job and it do it automatically every time i add a new drive or volume.
This is why I use gdu on servers
