On my system: Operating System: openSUSE Tumbleweed 20250630 KDE Plasma Version: 6.4.1 KDE Frameworks Version: 6.15.0 Qt Version: 6.9.1 Kernel Version: 6.15.3-2-default (64-bit) Graphics Platform: X11 I see for about two weeks now in the logs this error message: Jun 26 14:50:08 kernel: CIFS: VFS: Error connecting to socket. Aborting operation. Jun 26 14:50:08 kernel: CIFS: VFS: cifs_mount failed w/return code = -101 Jun 26 14:50:08 systemd[1]: Failed to mount /mnt/LAN/QNAP_Backups. which is produced every time I login. The error itself is perfectly explainable (no network available at login time) however the network resource in question is handled by this line in /etc/fstab: //192.168.100.19/Backups /mnt/LAN/QNAP_Backups cifs nofail,rw,_netdev,credentials=/PATH/TO/CREDENTIALS,uid=1000,gid=1000,sec=ntlmsspi,cache=none,nohandlecache,soft,x-systemd.automount,x-systemd.mount-timeout=30,x-systemd.idle-timeout=300s 0 0 To my understanding the network resource should only be mounted on demand, i.e when I try to access the device which I obviously will not do while the login process is still in progress. So I consider it a bug that an auto-mount-request is triggered (by kded6) during the login process for this network resource. Here some more information: If I boot my system (to graphical.target) but do not login and instead change to a virtual terminal (e.g. Ctrl+Alt+F3) and check the journal, the error has not yet occured. After login (I use SDDM as DisplayManager) the error is there. Inspecting the journal more closely I can see > journalctl --no-hostname --no-pager --full --utc -b 0 ... Jun 26 14:50:07 systemd[1864]: Started KDE Config Module Initialization. Jun 26 14:50:07 systemd[1864]: Starting KDE Daemon 6... Jun 26 14:50:07 systemd[1864]: Starting KDE Session Management Server... Jun 26 14:50:07 systemd[1864]: Starting KDE Window Manager... Jun 26 14:50:07 kded6[2044]: MESA: warning: Support for this platform is experimental with Xe KMD, bug reports may be ignored. Jun 26 14:50:07 systemd[1864]: Started KDE Daemon 6. Jun 26 14:50:07 systemd[1864]: Starting KDE Configuration Module Initialization (Phase 1)... Jun 26 14:50:07 ksmserver[2045]: MESA: warning: Support for this platform is experimental with Xe KMD, bug reports may be ignored. Jun 26 14:50:07 kwin_x11[2046]: MESA: warning: Support for this platform is experimental with Xe KMD, bug reports may be ignored. Jun 26 14:50:07 kded6[2044]: QDBusObjectPath: invalid path "/modules/wpad-detector" Jun 26 14:50:07 kded6[2044]: kf.dbusaddons: The kded module name "wpad-detector" is invalid! Jun 26 14:50:07 kcminit_startup[1996]: Initializing "/usr/lib64/qt6/plugins/plasma/kcms/systemsettings/kcm_touchpad.so" Jun 26 14:50:07 kcminit_startup[1996]: kcm_touchpad: Using X11 backend Jun 26 14:50:08 systemd[1864]: Finished KDE Configuration Module Initialization (Phase 1). Jun 26 14:50:08 systemd[1864]: Started KDE Session Management Server. Jun 26 14:50:08 systemd[1864]: Starting KDE Plasma Workspace... Jun 26 14:50:08 systemd[1864]: Started PipeWire PulseAudio. Jun 26 14:50:08 systemd[1864]: Started KDE Window Manager. Jun 26 14:50:08 rtkit-daemon[1896]: Successfully made thread 2170 of process 2170 owned by '1000' high priority at nice level -11. Jun 26 14:50:08 rtkit-daemon[1896]: Successfully made thread 2173 of process 2170 owned by '1000' RT at priority 20. Jun 26 14:50:08 systemd[1]: Starting Disk Manager... Jun 26 14:50:08 NetworkManager[1484]: <info> [1750949408.2074] agent-manager: agent[a2b1c621b1334a26,:1.35/org.kde.plasma.networkmanagement/1000]: agent registered Jun 26 14:50:08 udisksd[2178]: udisks daemon version 2.10.1 starting Jun 26 14:50:08 systemd[1]: Started Disk Manager. Jun 26 14:50:08 systemd[1]: Starting Daemon for power management... Jun 26 14:50:08 udisksd[2178]: Acquired the name org.freedesktop.UDisks2 on the system message bus Jun 26 14:50:08 systemd[1]: Started Daemon for power management. !!! !!! !!! Jun 26 14:50:08 systemd[1]: mnt-LAN-QNAP_Backups.automount: Got automount request for /mnt/LAN/QNAP_Backups, triggered by 2044 (kded6) !!! !!! !!! Jun 26 14:50:08 systemd[1]: Mounting /mnt/LAN/QNAP_Backups... Jun 26 14:50:08 kernel: netfs: FS-Cache loaded Jun 26 14:50:08 kernel: Key type dns_resolver registered Jun 26 14:50:08 mount[2194]: mount error(101): Network is unreachable Jun 26 14:50:08 mount[2194]: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) Jun 26 14:50:08 kernel: Key type cifs.spnego registered Jun 26 14:50:08 kernel: Key type cifs.idmap registered Jun 26 14:50:08 kernel: CIFS: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3.1.1), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3.1.1 (or even SMB3 or SMB2.1) specify vers=1.0 on mount. Jun 26 14:50:08 kernel: CIFS: enabling forceuid mount option implicitly because uid= option is specified Jun 26 14:50:08 kernel: CIFS: enabling forcegid mount option implicitly because gid= option is specified Jun 26 14:50:08 kernel: CIFS: Attempting to mount //192.168.100.19/Backups Jun 26 14:50:08 kernel: CIFS: VFS: Error connecting to socket. Aborting operation. Jun 26 14:50:08 kernel: CIFS: VFS: cifs_mount failed w/return code = -101 ... Some more information to take into consideration: My login sessions are always started as empty sessions. I use NetworkManager to handle all network connections and I will start any network connection only manually (via the plasma applet) when needed. I can say for sure that the behaviour described above did not show up with Operating System: openSUSE Tumbleweed 20250602, KDE Plasma Version: 6.3.5, KDE Frameworks Version: 6.14.0, Qt Version: 6.9.0, Kernel Version: 6.15.0-1-default (64-bit), Graphics Platform: X11 or before. And except of the nearly daily system updates there were no deliberated changes to the system configuration from my side. I have not discovered any further problems so far i.e. after login I can access the network resource in question without any problems. I consider it a bug that kded6 is triggering that auto-mount-request.
I discussed the problem on the openSUSE forum https://forums.opensuse.org/t/why-is-kded6-triggering-an-auto-mount-request-on-login/186092 without anyone showing up who could reproduce the problem. However the thread contains more information about my system.
I guess the freespacenotifier is triggering the automount and should probably be a bit smarter about monitoring automount mounts.
(In reply to Harald Sitter from comment #2) > I guess the freespacenotifier is triggering the automount and should > probably be a bit smarter about monitoring automount mounts. !!! WOW !!! That was fast! Thank you very much indeed. I disabled the freespacenotifier > qdbus6 org.kde.kded6 /kded org.kde.kded6.loadedModules dnssdwatcher colord gtkconfig networkmanagement bluedevil remotenotifier statusnotifierwatcher kameleon wpad-detector kded_touchpad oom-notifier kscreen audioshortcutsservice donationmessage ktimezoned devicenotifications desktopnotifier mprisservice plasma-session-shortcuts > and the error is gone. So this freespacenotifier must have got changes since KDE Plasma Version: 6.3.5, KDE Frameworks Version: 6.14.0, Qt Version: 6.9.0 which are causing that behaviour (which I consider a bug).
*** Bug 506241 has been marked as a duplicate of this bug. ***
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/5716
Git commit d4218baa77ba582278ccb586f55e404500e78330 by Niccolò Venerandi. Committed on 30/07/2025 at 08:29. Pushed by niccolove into branch 'master'. Only check the existance of CACHEDIR.TAG on mounted/accessible partitions Otherwise, the attempt to fetch the file might mount the partition; and, if the partition cannot be mounted, this action will result in a delay during startup. M +9 -6 freespacenotifier/module.cpp https://invent.kde.org/plasma/plasma-workspace/-/commit/d4218baa77ba582278ccb586f55e404500e78330