Public bug reported:

Ubuntu release:
Ubuntu 26.04.1 LTS (resolute)

Kernel:
7.0.0-31-generic

gvfs:
1.60.0-1

systemd:
259.5-0ubuntu3.4


Summary
-------

On a laptop with CIFS/SMB shares managed by native systemd .mount/.automount
units, gvfsd-recent repeatedly accesses an automounted network share after
it has been released.

systemd then receives a new automount request from gvfsd-recent and mounts
the CIFS share again. This interferes with reliably releasing network
filesystems as part of laptop suspend preparation.

The journal directly identifies gvfsd-recent as the automount trigger.


Observed behavior
-----------------

The affected shares are similar to:

    /mnt/synology/home
    /mnt/synology/library

with systemd units:

    mnt-synology-home.mount
    mnt-synology-home.automount
    mnt-synology-library.mount
    mnt-synology-library.automount

During testing, the journal repeatedly recorded events such as:

    mnt-synology-library.automount:
    Got automount request for /mnt/synology/library,
    triggered by 13487 (gvfsd-recent)

Eleven separate gvfsd-recent-triggered automount events were recorded during
the test session.

This is distinct from a genuine busy-filesystem condition. As a control test,
I deliberately placed a bash shell's current working directory inside the
CIFS share. fuser correctly identified that shell as a holder. After changing
the shell back to a local directory, no userspace holder remained, but
gvfsd-recent could still trigger the automount independently.


Expected behavior
-----------------

Desktop Recent-file processing should not cause a network filesystem that is
being deliberately released for suspend to be immediately automounted again.

A CIFS filesystem should be able to remain released during the suspend
transition, while its systemd .automount unit remains available for normal
access after resume.


Tested mitigation
-----------------

The following sequence prevented the unwanted remount and allowed clean
suspend:

1. Remove GNOME Recent history:

       ~/.local/share/recently-used.xbel

2. Recycle gvfsd-recent:

       pkill -u "$USER" -x gvfsd-recent

3. Release systemd-managed CIFS mounts through their .mount units:

       systemctl stop <corresponding>.mount

4. Leave the .automount units available for subsequent legitimate
access.

5. Verify that no CIFS filesystem remains mounted before suspend.

With this handling, repeated lid-close tests suspended and resumed
cleanly.

gvfsd-recent respawns normally afterward, so the mitigation does not
permanently disable GVFS Recent.


Additional evidence
-------------------

I have a journal extract containing the suspend tests, CIFS mount/unmount
events, and the repeated systemd messages explicitly naming gvfsd-recent as
the automount trigger.

This appears to be an interaction between gvfsd-recent, systemd automounts,
CIFS/SMB shares, and desktop suspend handling. I am filing against gvfs
because gvfsd-recent is explicitly identified by systemd as the process
triggering the unwanted automounts.

ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: gvfs 1.60.0-1
ProcVersionSignature: Ubuntu 7.0.0-31.31-generic 7.0.14
Uname: Linux 7.0.0-31-generic x86_64
ApportVersion: 2.34.1-0ubuntu0.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep  5 14:51:46 2026
InstallationDate: Installed on 2025-10-16 (325 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=<set>
SourcePackage: gvfs
UpgradeStatus: Upgraded to resolute on 2026-05-18 (111 days ago)

** Affects: gvfs (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug automount cifs gvfs resolute suspend

** Attachment added: "Journal extract showing gvfsd-recent-triggered automounts 
and CIFS suspend/recovery tests"
   
https://bugs.launchpad.net/bugs/2166582/+attachment/5997774/+files/CIFS-Suspend-Bug-Evidence-2026-09-05.txt

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/2166582

Title:
  gvfsd-recent retriggers CIFS automounts and interferes with suspend

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2166582/+subscriptions


-- 
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Reply via email to