https://bugs.kde.org/show_bug.cgi?id=432856
--- Comment #4 from a.saout...@gmail.com --- (In reply to Rafael Linux User from comment #3) > I'm sorry, my fault. I forgot to write 2 steps: > > - Switch off o.s. > - Switch on o.s. > > as I usually do every day. I didn't try if same issue between sessions. Ok that's unfortunately expected. However if the following two are done then this bug can be fixed: 1. mount KIO FUSE at /run/1000/kio-fuse/ instead of /run/1000/kio-fuse-<6-char-random-str>/. The reason why there's a random string is so that if KIO FUSE crashes for whatever reason, it can be DBus activated again. Otherwise, if KIO FUSe crashes and it is DBus activated again, it will be unable to mount as the previous process crashed and didn't unmount itself. I don't know if there's a way to call fusermount3 -u $dir upon crashing (which would allow us to remove the random string). 2. For the subsequent stat to succeed, the origin (i.e. protocol + authority) must already be mounted somehow. I'm not sure on the best way to proceed on that though... -- You are receiving this mail because: You are watching all bug changes.
