How to use the untrash feature on gdrive?

[spotter]

What is the problem you are having with rclone?

unsure how to use rclone backend untrash feature

What is your rclone version (output from rclone version)

rclone v1.53.1
- os/arch: linux/amd64
- go version: go1.15

Which OS you are using and how many bits (eg Windows 7, 64 bit)

ubuntu 20.4

Which cloud storage system are you using? (eg Google Drive)

google drive

The command you were trying to run (eg rclone copy /tmp remote:tmp)

$ rclone lsd --drive-trashed-only gdrive2:/gdrive/crypt/pc771bum0vcdadkj63seb3ggi6vv9on7qgsj39j2mqkb0egfr9i0/dnoqla9npp7ehi3sgspa7dqe4s/b2i2lbq67up3m9et9smhmsucmo/j2ik8j8cs1485b7hl6d3eoc5nc162h0uct6srt9spv34gde0umet34sn20fv0ckt10t6vg0o9c1b80g9i0rfvhjmnhic0osqsgfvpro
          -1 2020-10-17 09:37:23        -1 303ieeg5r7183ulcnrop9odfh8
          -1 2020-10-17 09:38:07        -1 i6a3qqo07v8pfijmmkqvt33fv8

$ rclone backend untrash gdrive2:/gdrive/crypt/pc771bum0vcdadkj63seb3ggi6vv9on7qgsj39j2mqkb0egfr9i0/dnoqla9npp7ehi3sgspa7dqe4s/b2i2lbq67up3m9et9smhmsucmo/j2ik8j8cs1485b7hl6d3eoc5nc162h0uct6srt9spv34gde0umet34sn20fv0ckt10t6vg0o9c1b80g9i0rfvhjmnhic0osqsgfvpro
{
	"Untrashed": 0,
	"Errors": 0
}

The rclone config contents with secrets removed.

[gdrive2]
type = drive
client_id = 
client_secret = 
token = <snipped>
root_folder_id = <snipped>

[gcrypt2]
type = crypt
remote = gdrive2:/gdrive/crypt
filename_encryption = standard
directory_name_encryption = true
password = <snipped>
password2 = <snipped

A log from the command with the -vv flag

ran same untrash command with --log-file /tmp/debug.log and nothing was output to it.

[asdffdsa (jojothehumanmonkey)]

so the debug log was empty, are you sure you ran the command correctly?
can you post the exact command you ran?

[spotter]

rclone --log-file /tmp/debug.log  backend untrash gdrive2:/gdrive/crypt/pc771bum0vcdadkj63seb3ggi6vv9on7qgsj39j2mqkb0egfr9i0/dnoqla9npp7ehi3sgspa7dqe4s/b2i2lbq67up3m9et9smhmsucmo/j2ik8j8cs1485b7hl6d3eoc5nc162h0uct6srt9spv34gde0umet34sn20fv0ckt10t6vg0o9c1b80g9i0rfvhjmnhic0osqsgfvpr

i.e. just add --log-file as I said

[spotter]

ok, unsue what happened (as noted in my other thread, what I thought was trashed, was apparently duped). I tried running the dedupe command and while it seemed to be erroring, it must have done something as the contents are now visible. but was't quite paying attention to exactly when it happened.