Files stuck in Trash

Question

So I recently had to reinstall my OS on my MBP. After the reinstall I attempted to open Chrome, but it would not open...I forget the error message. It was like there was a file missing or something. So, I tried to reinstall it and this was a struggle too, since I had to do it multiple times before it took. One of the things I had to do was delete the old copy of Chrome and I used App Zapper for that, since I could not remove it any other way. After deleting the App, I ended up with a bunch of folders in the Trash that I cannot delete no matter what I try. These folders are mostly empty with the exception of one which is basically full of what appears to be folders containing all the various languages that Chrome supports, however those folders are all empty too. When I try to delete these files, I get a message saying that they cannot be deleted because they are being used, yet when I check Activity Monitor, I cannot find them anywhere. I do not use Chrome often, so i don't understand how these files can be in use but they can't be found running anywhere. I have taken them out of Trash, put them in a different folder that I renamed and tried to delete them, but nothing. I have tried commands from the Command Prompt, like -rm and I don't remember what else, but that doesn't work. I have uninstalled Chrome again, and tried to delete them and nothing. What can I do? [] []2 []3 []4 []5

And this just continues through all the language files, so you get the idea... So let me reiterate, NONE of these files are actually in use no matter where I search for them, I can't find them. So how do you delete files that not being used but the OS claims they are....?

Here is the result of the rm -r * Terminal command:

Answer 1

How about:

• Type the following with empty space at the end into Terminal:

  sudo rm -rf

• Drag the files you want to delete (from the trash) into the Terminal window and hit ender.

• Enter your password. Done?

Disclaimer: Caution! The in this way deleted files are deleted forcefully and cannot be back easily. But I think you want exactly that...

Answer 2

• Open Terminal
• cd ~/.Trash
• ls and verify that these are indeed the files/folders in the trash
• rm -r *

Answer 3

Try using /Applications/Automator to create a System Service to delete items immediately.

When you create a new document in Automator, choose Service as the type. For "Service receives..." in the pop-up at the top, select "Files or Folders", and in the App pop-up choose Finder.app.

Add the "Run shell script" action. Settings:

Shell: /bin/bash

Pass input: As Arguments

script contents:

for f in "$@"
do
rm -r "$f"
done

Save the service with a name you can find easily, such as "Multi_instant_delete". Open the trash folder, select the unwanted items, perform a contextual click on one of them, and choose "Multi_instant_delete" from the Services item in the pop-up menu. You'll be prompted for your admin password.

If nothing happens, you could try executing the same steps while logged in as root. To temporarily enable the root user with /System/Library/CoreServices/Applications/Directory Utility.app, open Directory Utility, click the lock and authenticate, then choose "Enable Root User" from the Edit menu. You will now see "Other" in the login window, which you will choose, then enter "root" as the user name, and the password you assigned using Directory Utility. After you have logged in as root, you can view the .Trash folder in the home folder of the account of the user with the issue. You may then be able to select the items and move them to the trash then delete. If you can't see the items, you may need to search for .Trash folders that exist elsewhere on your boot volume. You may want to create the Service as the root user. When you create the Service, you may need to move it from "/var/root/Library/Services" to "/Library/Services" for it to appear in Root's contextual menu. Use ⇧⌘+. to see the .Trash folder(s).

Try leaving the original user logged in first, and if that doesn't work, then try by logging out of that user's account before logging in as root.

Be very careful when using that Service while logged in as root! Don't forget to disable the root user in Directory Utility, if desired.