PSA: Remember to also check hidden directories you don't even know about for waste of space


The media in this post is not displayed to visitors. To view it, please go to the original post.

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.
in reply to Lucy :3

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!!!
in reply to eldavi

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.

This entry was edited (Monday, November 11, 2024, 12:46 PM)
in reply to Lucy :3

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.

This entry was edited (Monday, November 11, 2024, 3:01 AM)
in reply to theshatterstone54

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.
in reply to cmnybo

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.
in reply to d_k_bo

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

in reply to Nanook

Depending on your file manager, you may be able to hold Shift while triggering the delete to get a hard delete.

Shift+Del is pretty much standardized as the keyboard shortcut. And here on KDE, I can hold Shift while clicking the "Move to Trash" menu entry, too (well, it actually replaces the menu entry with one for permanent deletion, but that's effectively the same).

in reply to Lucy :3

I use command trash-empty to 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: github.com/andreafrancia/trash… And my alias/function will show each file that is about being deleted (just put it in .bashrc, if you have installed trash-cli, which includes trash-empty):

::: spoiler 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 -f it deletes without asking.
This entry was edited (Monday, November 11, 2024, 3:00 AM)
in reply to lnxtx (xe/xem/xyr)

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.

in reply to Lucy :3

The media in this post is not displayed to visitors. To view it, please go to the original post.

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]

This entry was edited (Monday, November 11, 2024, 2:02 PM)

This website uses cookies. If you continue browsing this website, you agree to the usage of cookies.