[Bug 2130843] Re: SSH sessions blocked on unavailable automounts by default in Ubuntu 25.10

[Nadzeya Hutsko]

Based on the debugging information above, it sounds like this is a bug
in rust-coreutils. Re-assigning tags for Foundations to have a look.

** Package changed: base-files (Ubuntu) => rust-coreutils (Ubuntu)

** Tags removed: dcr-incoming

** Tags added: rls-qq-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to rust-coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/2130843

Title:
  SSH sessions blocked on unavailable automounts by default in Ubuntu
  25.10

Status in rust-coreutils package in Ubuntu:
  New

Bug description:
  Since upgrading to 25.10, incoming ssh sessions hang when unavailable
  systemd automounts, local or remote, are present. The creation of the
  ssh session hangs from half a minute to several minutes depending on
  how many automounts it tries. Stopping the unavailable automounts
  fixes the problem. This did not happen prior to 25.10. Is this a bug
  or is there a new and preferred way of defining automounts in fstab so
  that PAM or systemd does not block incoming ssh sessions by trying to
  mount unavailable automounts?

  Here are 2 examples of fstab entries that are subsequently read by
  systemd and turned into automounts. If the device is not available
  then incoming ssh connections hang. This syntax has worked for many
  years.

  servername.local:/volume1/name /mnt/servername/name nfs
  x-systemd.automount,_netdev,x-systemd.device-
  timeout=10,nfsvers=3,noauto,user,rw,exec 0 0

  /dev/disk/by-label/corsair /media/myname/corsair auto
  x-systemd.automount,nosuid,nodev,nofail,x-gvfs-show,x-gvfs-
  name=corsair,user 0 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rust-coreutils/+bug/2130843/+subscriptions