Bug 506241

Summary: Free Space Notifier causes Plasma session delay when NFS mount is unavailable
Product: [Plasma] plasmashell Reporter: Fred <fred>
Component: Startup processAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: major CC: iivanich, kde, kdedev, sitter
Priority: VHI    
Version First Reported In: 6.4.0   
Target Milestone: 1.0   
Platform: openSUSE   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=272361
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Fred 2025-06-26 22:22:14 UTC 
Summary:
When an NFS share defined in fstab with nofail,x-systemd.automount is unreachable (e.g. NAS is powered off), KDE Plasma session is delayed by ~60 seconds at login due to the Free Space Notifier background service. Disabling the Free Space Notifier service (or commenting out the fstab entry and reloading the daemon) will resolve the issue

Steps to reproduce:
1. Define an NFS mount in /etc/fstab:
my.nas.local:/NAS /srv/NAS nfs defaults,nofail,x-systemd.automount,x-systemd.idle-timeout=60s 0 0
2. Enable Free Space Notifier via System Settings > Background Services.
3. Reboot or re-login with the NAS powered off.
4. Observe:
- Login stalls at black screen with cursor for ~1 minute.
- Journal shows plasma-plasmashell.service timing out and restarting.
- System eventually recovers.

Workaround:
Disabling Free Space Notifier removes the delay.

Expected behavior:
Free Space Notifier should not delay session startup if a disk is unreachable or unmounted.
Comment 1 ml 2025-06-27 09:42:49 UTC 
Having the same issue, disabling Free Space Notifier via kcmshell6 kcm_kded helped.
Comment 2 TraceyC 2025-07-01 17:34:04 UTC 
This is part of an underlying issue with frameworks-kio that unfortunately has been a long standing problem. I'm merging this report in with the main report 272361. 

This may be able to be mitigated in the Free Space Notifier code, I'll let the developers make that determination.
Comment 3 Harald Sitter 2025-07-05 15:26:25 UTC 

*** This bug has been marked as a duplicate of bug 506488 ***