Update after re-encountering this in July 2026: The fix (rust-coreutils 0.6.0, upstream PR #9078) was released into the 26.04 development series only — it was never SRU'd to 25.10, which still ships 0.2.2. So on 25.10 this bug is present for the release's entire supported life.
Additionally, the practical workaround (editing /usr/lib/ubuntu-release- upgrader/release-upgrade-motd and /usr/lib/update-notifier/update-motd- fsck-at-reboot to call GNU stat) silently regresses whenever the owning packages (ubuntu-release-upgrader-core, update-notifier-common) are updated, since the patched files are package-owned. My November edit was reverted by a later package update and the multi-minute SSH hangs returned; this may explain "it came back" reports from others. For anyone else hitting this on 25.10: 1. Confirm exposure: sudo sh -c 'command stat --version' — uutils < 0.6.0 is affected; an interactive shell may show GNU via aliases/~/bin and mislead you. 2. Re-apply the gnustat substitution in the two MOTD helpers above after any update of those packages. 3. Independently, cap the damage by adding x-systemd.device-timeout=5s to fstab automount entries for sometimes-absent devices — this bounds any future stat-triggered automount storm to seconds instead of minutes (the systemd default is 90 s per device). Upgrading to 26.04 (rust-coreutils 0.8.0) resolves this fully; verified ssh login time went from ~3 minutes to 0.22 s with the workaround, matching the fixed behavior. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2130843 Title: SSH sessions blocked on unavailable automounts by default in Ubuntu 25.10 To manage notifications about this bug go to: https://bugs.launchpad.net/rust-coreutils/+bug/2130843/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
