https://bugs.kde.org/show_bug.cgi?id=401088
Steve Vialle <stev...@orcon.net.nz> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |stev...@orcon.net.nz
--- Comment #43 from Steve Vialle <stev...@orcon.net.nz> ---
I have been seeing this for every filesystem (3 local filesystems on 2 RAID1
arrays , 5 NFS mounts), every login. Appears new(ish), as in I'm tracking
current plasma releases and I've only seen it in the last couple of updates.
The NFS mounts are indeed slow, as the network is firewalled until opensnitch's
GUI loads (or could be down entirely) and mounts are retrying in the background
(i.e. mounted with -o bg) but the messages regarding local arrays are entirely
incorrect - as verified by dropping (or booting direct to) a VT.
Those inaccessible NFS background mounts also completely prevent dolphin from
launching (or hang it if it's already open and they go down), as well as
freezing parts of plasmashell itself (including the panel and notifications).
The result is an unusable desktop for a few seconds until the NFS mounts
succeed, followed by a flurry of 8 "filesystem not responding" popups... which
only appear once the filesystem is no longer "not responding", by which time
they are completely pointless.
If the network is actually down, the desktop remains unusable until the
background mounts time out and fail - which could be 5 minutes, or it could be
_forever_ if they are hard mounts. This is not an acceptable user experience by
any stretch of the imagination, and I know of no other UI or file manager that
locks up completely if a single non-essential mount is down.
IOW, the behaviour of plasma/kio WRT inaccessible / unresponsive / slow
filesystems is utterly broken, and has been for years. Adding popups is not
addressing the root problem in the slightest, doubly so if they don't appear
until _after_ the cause is resolved.
--
You are receiving this mail because:
You are watching all bug changes.
