Nemo: Long delay when opening Nemo / file dialogs

[mikehaertl]

```

• Nemo version 4.6.5
• Is issue with desktop or windowed nemo? both
• Distribution - Mint 20
• Graphics hardware and driver used
  Graphics: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics vendor: ASRock driver: i915 v: kernel
  bus ID: 00:02.0 chip ID: 8086:0412
  Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1200~60Hz
  OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) v: 4.5 Mesa 20.0.8 compat-v: 3.0 direct render: Yes
• 64 bit
  ```

Issue

Sometimes suddenly opening Nemo (and any other file dialog from other programs) is delayed by 25 seconds. It probably has to do with gvfsd-trash not responding, see below.

Steps to reproduce

There is no clear procedure to reproduce.

Expected behaviour

It should open immediately.

Other information

• Upstream issue in Gnome: https://gitlab.gnome.org/GNOME/gvfs/-/issues/485 (and related: https://gitlab.gnome.org/GNOME/glib/-/issues/1941)
• Forum discussion: https://forums.linuxmint.com/viewtopic.php?f=47&t=328966.

Opening the issue here as per suggestion of forum member smurphos.

Workaround

killall gvfsd-trash fixes the issue without a reboot.

[starsep]

I confirm the bug, workaround works. Without it is takes more than 25 seconds, with it less than 2.

[Rinkaa]

I have a similar issue. Sometimes suddenly it takes more than 60 seconds to start a new nemo window (even when there is an existing dialog). killall gvfsd-trash does not fix the issue but killall gvfsd does in my case.

[My-Random-Thoughts]

I have a similar issue on version 4.4.2. I "fixed" it by reinstalling all the gvfs* packages (7 in my case). That was before I saw this open bug! :)

EDIT: Using Ubuntu 20.04 with Cinnamon

[mikehaertl]

The upstream issue in Gnome has been fixed now: https://gitlab.gnome.org/GNOME/gvfs/-/issues/485.

@icarter09 I assume that we just have to wait until the fix makes it into the Ubuntu gvfs-daemons package, right? Or is there anything we could do to speed this up?

[icarter09]

@mikehaertl thanks for the heads up that it's been fixed upstream. I'll see about what can be done to get it implemented sooner.