Caja cannot find .Trash-1000

Support & Help Requests
4

I think I see the problem.

In the first screenshot you attached, you checked the option "Mount at system startup". This does not do what you might expect. When you instruct UDisks to mount a partition at system startup, UDisks literally mounts the disk at system startup, i.e. before you log in. UDisks can't know ahead of time which user you're going to log in as, so UDisks will mount the partition on root's behalf. This explains why the following appears in the mount -l output you attached (thank you):

(I added emphasis to the relevant section of the output.)

The user_id=0,group_id=0 tells the NTFS filesystem driver to set the owner of all files to root. You may wonder why you can't set ownership on specific files on NTFS volumes on Linux; for a multi-page diatribe about the reason for that, please see my post at Pi4 Mate 20.10 Gpart format ntfs partition on SDcard cannot uncheck "run as executable" in Caja - #2 by gordon. (Short answer: NTFS is not a UNIX-aware filesystem; therefore it lacks the ability to store UNIX ownership and permissions data on the filesystem, and due to a bug the NTFS driver doesn't return an outright error when you try to set UNIX-style permissions.)

TL;DR: There are several ways to fix / work around the issue. I haven't verified any of them to completion, however; if I wanted to really test them I'd have to reboot, and due to some processes that I have running that can't be interrupted, I can't reboot to test them right now. But here's the checklist anyway (in no particular order):

  • In the Disks utility, in the Mount Options dialog that you screenshotted above, in the field of mount options just above the field for the mount point: append ,user_id=1000,group_id=1000 to the list of mount options, to ensure the volume gets mounted on behalf of your user account every time the system boots. Oh yeah, and reboot the system right after making this change; the change won't take effect until you reboot next!

    This method requires the least changes to your current setup (among the other options listed here), but has one caveat: If you boot up and immediately log in as a user different from your normal user account (user 1000, named robert), then the user you log in to will not have ownership of the files on the partition. (However, that user will be able to read files since your mount options also include the allow_other option, which gives everybody read access to everything on the partition.)

  • If the multi-user-unfriendlyness of the above option turns you off, you can disable "Mount at system startup" and add this to each user's list of startup applications (search under the Brisk menu for Startup Applications):
    udisksctl mount -b /dev/sda2
    I got that command from 11.10 - Automatically mount NTFS drive when I login - Ask Ubuntu, though I have not verified myself that this works. Theoretically, it certainly should (but when was the last time that theory bought you a sandwich? :grin:).

  • I don't really understand how the following answer works, but it sounds intriguing anyway:
    raspberry pi - How can I make udisks-glue run at startup and mount drives as particular user? - Unix & Linux Stack Exchange

I hope that helps you in some way or another. I'm sorry I can't be of much more help than that right now.

I'm also sorry if the mass of information I just provided to you overwhelms you; I'd be overwhelmed right now if I were on the receiving end!