Xfce Forum

fooj68

Member

Registered: 2024-10-21

Posts: 1

Possible problem with how XFCE/Thunar implements/works with Trash?

I've been having some sporadic performance issues & log flooding for a while now on my XFCE machines (Fedora 40) relating to when files are deleted. Specifically, when I delete files, I will get journal logs like the following for every deleted file

Oct 21 14:23:49 fooj gvfsd-trash[3035]: GFileInfo created without standard::name
Oct 21 14:23:49 fooj gvfsd-trash[3035]: file ../gio/gfileinfo.c: line 1698 (g_file_info_get_name): should not be reached

This also happens when remote directories are mounted and their Trash directories are often (automatically) enumerated and traversed, which can end up causing significant performance problems and I will often see gvfsd-trash in the task manager using an entire CPU thread for a long period of time.

This happens even when remote directories are not mounted at all, I tested this as I thought at first it might be some issue with how remote severs were handling Trash or combined local+remote Trash management. Also, I do not experience this problem on systems with different DE's, such as Cinnamon on the same distro, which I believe also uses gvfsd-trash.

I've found a few people posting logs referencing this same log message referencing standard::name (although not in the context of this issue, but relating to other things) - and only when using XFCE.

Here is one for Arch XFCE (referencing the exact same line of code in gvfsd-trash), and here is another log from an XFCE user referencing line 1699. This thread here also references it, noting that it might have been fixed with glib 2.76, although I am running Thunar 4.18.11-1.fc40 and glib 2.80.3-1.fc40 - I'm not sure that glib bug is the same problem however as it doesn't specifically reference standard::name as far as I can tell.

Has anyone else seen this or have any ideas of as to what could be done on my end to mitigate this?

Edit: I grepped my system journal for the past 2 months roughly, and it counted over 570,000 matches for the string "without standard::name", and at least one instance where 100k+ messages were suppressed (I think it might be a lot more as my journal logs seemed to have rotated as a result of this)

Last edited by fooj68 (2024-10-21 23:36:16)

ToZ

Administrator

From: Canada

Registered: 2011-06-02

Posts: 12,311

Re: Possible problem with how XFCE/Thunar implements/works with Trash?

Hello and welcome.

Reminds me of this bug and this bug, but apparently it was fixed in versions previous to the version you are running.

Might be a good idea to create another bug report.

---

Mark solved threads as [SOLVED] to make it easier for others to find solutions.
--- How To Ask For Help | FAQ | Developer Wiki  |  Community | Contribute ---