Skip to content
This repository has been archived by the owner on Dec 1, 2021. It is now read-only.

Using trash-put from thrash-cli will make imv not respond to even SIGTERM #269

Open
freed00m opened this issue Jul 30, 2020 · 3 comments
Open

Comments

@freed00m
Copy link

My config is simple

[binds]
# Delete and then close an open image by pressing 'X'
<Shift+D> = exec trash-put "$imv_current_file"; close

just instead of rm I used trash-put, the program becomes unresponsive.
The file gets moved to the defined trash as it should but the brogram should not get stuck.

@freed00m
Copy link
Author

It happens only on my Arch installation not Manjaro installation I might have different issue :O

@freed00m
Copy link
Author

freed00m commented Jul 30, 2020

Using LUKS2 with systemd-homed,

the gvfs gets stuck in a loop, spamming messages like this

gvfsd-trash[1066]:     A trash files/ directory should only have files linked or unlinked (via moves or deletes).  Some other operation has been detected on a file in the directory (eg: a file has been modified).  Likely, the data reported by the trash backend will now be inconsistent
gvfsd-trash[1130]: *** Unsupported operation detected on trash directory
gvfsd-trash[1130]:   dir: /home/frdm/.local/share/Trash/files, file: files, type: 4
                                            

Spamming stops when I kill IMV

Probably not your bug though.

@freed00m
Copy link
Author

I've stopped using trash-cli as I found it to be very buggy and terrible.

I use "gio" now and have 0 problems. But imv should not die from trash-cli claiming illegal opperation.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant