Nautilus doesn't load and gives GVFS-WARNING

Thank you for your bug report, could you give details on how you do the cifs mount, be specific if possible with example of configuration and cmd used so others can try to reproduce your setup.

It might also be useful to report to upstream on https://gitlab.gnome.org/GNOME/nautilus/-/issues

I can reproduce this with

    sudo mount -t cifs -o noauto,rw,uid=1000,gid=1000,guest,nounix,noserverino,file_mode=0660,dir_mode=0755,iocharset=utf8,vers=2.1 //192.168.1.1/backup/ /media/grumpy/brick

followed by running

    nautilus

The network drive is a USB hard disk attached to my router. It's formatted to NTFS.

Status changed to 'Confirmed' because the bug affects multiple users.

I've been experiencing the same (intermittent) symptom on a relatively new install. It's hard to be sure, but I think I've resolved it by disabling keybase.

I can confirm the same intermittent issue and I also have Keybase installed. I don't recall having the issue prior to installing it.

just ran into the same issue after an `apt upgrade`. Disabling keybase helped for me too, but there weren't any issues before the upgrade.

I have exactly this issue, including not begin able to open file dialogs for opening files or saving files as. When I shut down Keybase, everything work again like expected.

I have exactly the same issue but keybase is not installed on my system.
I am running stock Ubuntu 22.04 .
This issue happened after I did apt dist-upgrade a couple of days ago (May 4th?).
I upgraded my system to 22.04 from 21.10 when 22.04 was publicly released.
I used the software-updater to do the upgrade.
Since then I had not had any issues at all.
This issue only started after my apt dist-upgrade on around May 4th.
Due to this issue I cannot run Atom as well.

I get this error when Atom crashes.

Just a bunch of "this is deprecated"
"
/usr/bin/atom: line 195: 16065 Killed nohup "$ATOM_PATH" --executed-from="$(pwd)" --pid=$$ "$@" > "$ATOM_HOME/nohup.out" 2>&1
(node:16144) Electron: Loading non-context-aware native module in renderer: '/usr/share/atom/resources/app.asar.unpacked/node_modules/superstring/build/Release/superstring.node'. This is deprecated, see https://github.com/electron/electron/issues/18397.
"

Atom not opening my project folder was what led me to realize that Nautilus was also not opening.

I was able to open nautilus after turning WiFi off. Atom also was then able to open the project folder.

I'd forgotten about this until now. It's been working for me lately. I don't know what changed apart from updating to 22.10 last year.

$ apt-cache policy nautilus gvfs
nautilus:
  Installed: 1:43.0-1ubuntu2.1
  Candidate: 1:43.0-1ubuntu2.1
  Version table:
 *** 1:43.0-1ubuntu2.1 500
        500 http://au.archive.ubuntu.com/ubuntu kinetic-updates/main amd64 Packages
        500 http://au.archive.ubuntu.com/ubuntu kinetic-security/main amd64 Packages
        100 /var/lib/dpkg/status
     1:43.0-1ubuntu1 500
        500 http://au.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
gvfs:
  Installed: 1.50.2-2
  Candidate: 1.50.2-2
  Version table:
 *** 1.50.2-2 500
        500 http://au.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
        100 /var/lib/dpkg/status

When I invoke thunar from my arm 32 bit chromeboo I have this error :

(thunar:2313): GVFS-WARNING **: 13:49:56.399: The peer-to-peer connection failed: Timeout was reached. Falling back to the session bus. Your application is probably missing --filesystem=xdg-run/gvfsd privileges.

I'm using ubuntu 22.04 for armhf and I'm connecting to the arm chromebook via ssh forwarding. Instead,
thunar works if I run it directly on the chromebook.