https://bugs.kde.org/show_bug.cgi?id=494224
Steve Vialle <stev...@runbox.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |stev...@runbox.com
--- Comment #12 from Steve Vialle <stev...@runbox.com> ---
(In reply to Nate Graham from comment #8)
> The problem is that there is an infinite amount of code in KDE software that
> assumes things that show up as local files won't randomly become transient.
The problem is that KDE (or more to the point, solid) constantly mucks about in
"local" filesystems the user isn't actively accessing, and has no graceful
handling for those background i/o operations failing.
A program freezing or crashing when a filesystem the user is currently
interacting with (using said program) goes down is expected and largely
unavoidable. The whole desktop (or every open file manager window, i.e. the
many, many bug reports regarding dolphin and network mounts) doing the same
when a filesystem that _isn't_ currently displayed in any window or being
accessed by the user is not expected, and furthermore, it's a behaviour that
appears to be unique to KDE.
> For third-party apps that can't or won't use KIO, a better solution is to
> encourage people to make use of kio-fuse for this by accessing their shares
> in Dolphin, and then we change kio-fuse to do the FUSE mount in a
> persistent, unchanging location. Then we also allow it to be automounted on
> login, optionally. This would give us the best of both worlds.
It'll also mean that network mounts are reliant on KIO, unreasonably slow
(FUSE), only available after login, and (without further manual configuration)
only available to a specific user. That's the best of _one_ world - namely a
single-user GUI desktop, where that GUI is always KDE.
There are many reasons to mount network shares early in the boot process and at
a level below KDE/KIO, and such has been normal practice on every unix for
decades. This was never a problem until KDE with its "everything integrated
with everything else" design and incessant polling of every available
filesystem became involved.
--
You are receiving this mail because:
You are watching all bug changes.
