Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • K KIOFuse
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 14
    • Issues 14
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 9
    • Merge requests 9
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • SystemSystem
  • KIOFuse
  • Issues
  • #18
Closed
Open
Issue created Feb 26, 2021 by Alexander Saoutkin@asaoutkinDeveloper

Use Fixed Location for KIO FUSE

The path of the KIO FUSE mount changes between launches (and in particular, between sessions) meaning that programs that have an "Open Recently" feature, don't work as expected. Bug Report: 432856.

  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). The following two ML threads (here and here) lead me to believe that this is possible if mounting with -o auto_unmount but my local testing seemed to imply it didn't work. This will need investigating.
  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... although it's definitely possible one way or another.
Assignee
Assign to
Time tracking