Interesting that the last person mentioned Caja - there is potential progress in narrowing down where the problem lies in their issue tracker (https://github.com/mate-desktop/caja/issues/528).
Nautilus, Caja and Nemo all exhibit this same behaviour. In the Caja issue tracker zaps666 suggested that when the problem occurs, dbus (in glib) is waiting for a long time for a notification from somewhere, and that commenting out dbus in the glib move file code fixes the problem, but isn't a solution.
If it's a glib issue, then https://bugzilla.gnome.org is the relevant place for bug reporting; it could also be something to do with the way nautilus uses glib, in which case bugzilla.gnome.org is still the best place to report a bug for nautilus. It's worth having a look there in any case to see if there's already something relevant, as this bug has been around for a while.
Interesting that the last person mentioned Caja - there is potential progress in narrowing down where the problem lies in their issue tracker (https:/ /github. com/mate- desktop/ caja/issues/ 528).
Nautilus, Caja and Nemo all exhibit this same behaviour. In the Caja issue tracker zaps666 suggested that when the problem occurs, dbus (in glib) is waiting for a long time for a notification from somewhere, and that commenting out dbus in the glib move file code fixes the problem, but isn't a solution.
If it's a glib issue, then https:/ /bugzilla. gnome.org is the relevant place for bug reporting; it could also be something to do with the way nautilus uses glib, in which case bugzilla.gnome.org is still the best place to report a bug for nautilus. It's worth having a look there in any case to see if there's already something relevant, as this bug has been around for a while.