https://bugs.kde.org/show_bug.cgi?id=401088
SoftExpert <softexp...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |softexp...@gmail.com
--- Comment #46 from SoftExpert <softexp...@gmail.com> ---
My 2 cents here: I believe the issue is outside Plasma entirely and purely
systemd related (more precisely systemd-fstab-generator related); I had the
same errors described here since the upgrade to Plasma 6.0.x and I seem to have
fixed the intempestive notifications by altering the parameters in fstab
related to the nfs mounts.
Following line corresponds to my current settings in fstab and I was able to
boot several times without having the random locations unavailable
notifications; prior to the current set of parameters, for 90 seconds after the
login, the plasmoids on the desktop appeared to be frozen (I have several
showing the CPU frequency graphs, temperatures, hdd I/O). After the
modification they behave normally right since the login.
Example of my current config (the relevant part):
> noatime,nofail,users,async,_netdev,retry=7,x-systemd.automount,x-systemd.after=network-online.target,x-systemd.device-timeout=50s,x-systemd.mount-timeout=90s,timeo=15,x-systemd.idle-timeout=2min
> 0 0
My changes:
- added async (the big help seems to come from this one)
- added _netdev (just making sure systemd-fstab-generator will correctly
schedule the mount - after the network becomes available)
- added retry=7 (7 was my choice, it does not have a particular meaning for
you)
- changed x-systemd.device-timeout=15 to x-systemd.device-timeout=50s (it
appears necessary to specify time measure unit, systemd can be that picky)
- added x-systemd.mount-timeout=90s
Hopefully this can be your solution as well ...
--
You are receiving this mail because:
You are watching all bug changes.
