I’m experiencing this problem.
I moved a bunch of files into a subdirectory and when I tried to empty the trash, I got the permissions error mentioned above. This is in a shared Google Drive folder.
Setting aside the permissions problem for the moment, I just moved some 140 files. And the empty trash operation stops after a single error. So I’ve now got to repeat this process another 139 times… Empty trash > OK > accept error. Super frustrating!
Back to the problem at hand: it looks like a limitation with the Google Drive API. I think the only way to “delete” these files is to remove all privileges for the file.
Moving files are similarly complicated: do you actually want to just move files and retain privileges as is, or duplicate the files and delete permissions to the originals? I see the need for both…
The good news is, once I figured that part out and deleted things with Drive’s web interface, odrive did the right thing so I didn’t actually have to empty trash another 139 times. Just ~5 times before I started looking for alternatives.
The not so good news is that this was part of a cleanup involving multiple links. I’d moved files from another account to this shared folder. When I removed this shared folder (which I owned), the files that were supposed to move into it just vanished. They got deleted from their original account, and never made it to the shared folder. I suspect this is a separate issue though… If it helps, I’d noticed odrive had this file move queued up. I assumed it was stuck waiting for the trash to be emptied, and it did disappear once I resolved the issue above.
I feel that if there was a way to enable immediate trashing, these problems would have been visible right away and then I’d have the ability to fix it right away. Instead, it took a while for me to notice that the changes weren’t going through and by then there were a lot of actions queued up.