https://bugs.kde.org/show_bug.cgi?id=319998
Stefan Brüns <stefan.bru...@rwth-aachen.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |stefan.bruens@rwth-aachen.d
| |e
--- Comment #31 from Stefan Brüns <stefan.bru...@rwth-aachen.de> ---
(In reply to Marco Leise from comment #30)
> I wish what the desktop environments do now didn't look so ad hoc. :)
> The issue of filesystems staying in the places list (and AFAICT, plasmashell
> slowing down) is not fixed by this, there are just fewer real life cases
> that could trigger the problem. I.e. if I moved my systemd auto-mount from
> /usr/repos to $HOME/repos I would have to reopen this report.
>
> My expectation was that KDE is properly informed by udisks about the
> disappearance of the loop device even if that means opening a bug report
> with the kernel. I don't have a deep understanding of the issue though.
There are two different aspects here:
1. Loop devices without backing file
2. User mounted loop devices (having a backing file)
The first should never be shown. If these are, it is a bug.
The second can only be handled in a heuristic way. The heuristic says when the
user has mounted e.g. a iso image, it is sensible to make it accessible and
findable by default.
Now, it is perfectly valid to have something permanent mounted in your home
directory. But if you add this *manually*, you should go the full way and tell
the infrastructure it should ignore it. This is easy to do, just add an
x-gvfs-ignore=true hint to your filesystem options.
--
You are receiving this mail because:
You are watching all bug changes.
