Dear Maintainer,

Casually using Thunar causes the following errors to be logged in journalctl:

May 07 20:07:17 laplace gvfsd-trash[2996]: GFileInfo created without standard::name
May 07 20:07:17 laplace gvfsd-trash[2996]: file ../../../gio/gfileinfo.c: line 1698 (g_file_info_get_name): should not be reached
May 07 20:07:17 laplace gvfsd-trash[2996]: GFileInfo created without standard::name
May 07 20:07:17 laplace gvfsd-trash[2996]: file ../../../gio/gfileinfo.c: line 1698 (g_file_info_get_name): should not be reached

Because of this, every time I delete a file (i.e. move it to trash), coincidentally my whole system
including my desktop significantly slows down and on one occasion has forced me to reboot by holding
the power button. I am not exactly sure of what could be the issue here, but it hinders my workflow
significantly and judging by the error message, an assertion in the source code is not being fulfilled.
If I can provide any additional information, please let me know.

Yours,
Kamila Szewczyk

This error still exist for version 1.57.2-2

I too have noticed this problem. With the added fun that the
syslog-forwarded logs are running my loghost out of diskspace.

In my case, my Trash folder on my network share contains about 2000 files,
most of which were relative symlinks, created by hand but later trashed
from within geeqie.

I removed all the symlinks (and their trashinfo):

   find -type l|while read f;do rm -f "$f" "$(echo $f|sed 's/^/..\/info\//;s/$/.trashinfo/')";done

While this ran, there was unbelievable amounts of syslog spam:

    [snip]
    2025-08-25T20:28:36+08:00 joyola gvfsd-trash[3607]: GFileInfo created without standard::name
    2025-08-25T20:28:36+08:00 joyola gvfsd-trash[3607]: file ../../../gio/gfileinfo.c: line 1713 (g_file_info_get_name): should not be reached
    2025-08-25T20:28:36+08:00 joyola gvfsd-trash[3607]: GFileInfo created without standard::name
    2025-08-25T20:28:36+08:00 joyola gvfsd-trash[3607]: file ../../../gio/gfileinfo.c: line 1713 (g_file_info_get_name): should not be reached
    2025-08-25T20:28:36+08:00 joyola gvfsd-trash[3607]: GFileInfo created without standard::name
    2025-08-25T20:28:36+08:00 joyola gvfsd-trash[3607]: file ../../../gio/gfileinfo.c: line 1713 (g_file_info_get_name): should not be reached
    2025-08-25T20:28:36+08:00 joyola gvfsd-trash[3607]: GFileInfo created without standard::name
    2025-08-25T20:28:36+08:00 joyola gvfsd-trash[3607]: file ../../../gio/gfileinfo.c: line 1713 (g_file_info_get_name): should not be reached
    2025-08-25T20:28:36+08:00 joyola gvfsd-trash[3607]: GFileInfo created without standard::name
    2025-08-25T20:28:36+08:00 joyola gvfsd-trash[3607]: file ../../../gio/gfileinfo.c: line 1713 (g_file_info_get_name): should not be reached
    2025-08-25T20:28:36+08:00 joyola gvfsd-trash[3607]: GFileInfo created without standard::name
    2025-08-25T20:28:36+08:00 joyola gvfsd-trash[3607]: file ../../../gio/gfileinfo.c: line 1713 (g_file_info_get_name): should not be reached
    2025-08-25T20:28:36+08:00 joyola gvfsd-trash[3607]: GFileInfo created without standard::name
    2025-08-25T20:28:36+08:00 joyola gvfsd-trash[3607]: file ../../../gio/gfileinfo.c: line 1713 (g_file_info_get_name): should not be reached
    [snip]

`grep -Fc '2025-08-25T20:28:' user.log` revealed that half a million lines
had just been added to syslog files.  Another half a million would have been
added to /var/log/syslog too.

I created a test symlink (on a local filesystem), and deleted it using
Thundar (476 lines added to logs) and then restored it (474 lines added to
logs).

The takeaway I'm getting here is that having a nontrivial number of files in
Trash/Rubbish is something to be avoided due to this bug.

The fix has not yet made it into a release, though.