Delete to Recycle Bin - gio-trash vs gvfs-trash

*** Please report new bugs here! ***

Moderators: xnview, Dreamer

User avatar
KPAH
Posts: 31
Joined: Thu Mar 11, 2010 8:26 am
Location: Snowierasha

Delete to Recycle Bin - gio-trash vs gvfs-trash

Post by KPAH »

I'm on Arch Linux, and I was never able to get Delete to recycle bin working since migrating from Debian-based distro. It seemed to be working in Debian though.

Despite Delete to Recycle bin enabled, the files are still deleted forever.
In the terminal, the following is displayed:
#### check gio 2
====> 1 127
## ==> gvfs-trash has problem!!deleteIndexes 1 - 1
So it seems to be checking for GIO (cli command to move to trash in Arch is gio trash), but then defaults to gvfs-trash which is for GTK-based apps.

gio trash works from terminal no problem, and I can also delete to recycle bin through file system file manager, but nof from XnView

I'm using 1.8.6 appmage with local config and home folders next to appimage (i.e. portable mode).
User avatar
KPAH
Posts: 31
Joined: Thu Mar 11, 2010 8:26 am
Location: Snowierasha

Re: Delete to Recycle Bin - gio-trash vs gvfs-trash

Post by KPAH »

gvfs-trash is actually deprecated for 7 years at least
I tried creating a bash script with the same name, but the error in Xnview still persists.
User avatar
xnview
Author of XnView
Posts: 47726
Joined: Mon Oct 13, 2003 7:31 am
Location: France

Re: Delete to Recycle Bin - gio-trash vs gvfs-trash

Post by xnview »

KPAH wrote: Thu Feb 27, 2025 2:37 pm gvfs-trash is actually deprecated for 7 years at least
do you have gio?
Pierre.
GracyScott
Posts: 7
Joined: Fri Mar 07, 2025 10:13 am

Re: Delete to Recycle Bin - gio-trash vs gvfs-trash

Post by GracyScott »

XnView is usually pretty robust, but sometimes the database and the actual file EXIF data get out of alignment, especially after a batch move or rename.
If the "Update Files from Catalog" command isn't doing the trick, it might be worth checking if the files have some weird permission settings or if the headers are slightly malformed. I’ve found that running problematic files through a quick image inspector or a metadata validator can sometimes reveal why the software is having trouble "seeing" the labels you’ve applied.