https://bugs.kde.org/show_bug.cgi?id=476795

            Bug ID: 476795
           Summary: Cannot reliably mount KeeShare container from an SMB
                    mount pulled in via KIO
    Classification: Frameworks and Libraries
           Product: frameworks-kio
           Version: 5.110.0
          Platform: Fedora RPMs
                OS: Linux
            Status: REPORTED
          Severity: minor
          Priority: NOR
         Component: general
          Assignee: kio-bugs-n...@kde.org
          Reporter: h...@runiq.de
                CC: kdelibs-b...@kde.org
  Target Milestone: ---

SUMMARY

I'm using KeePassXC and would like to include a shared database [1] from an SMB
mount accessed via KIO. This works fine as long as I don't reboot. However,
with each reboot, the link to the mounted file changes. It looks like this: 

/run/user/1000/doc/56b810f0/my-share.kdbx.share

The problem is that the '56b810f0' bit in the middle is different on every
boot.

Is there a way to get a deterministic path here? I've looked at kioclient to
maybe automate this with a Systemd user unit, but it doesn't appear to have a
mount command available.

[1]
https://keepassxc.org/docs/KeePassXC_UserGuide#_database_sharing_with_keeshare

STEPS TO REPRODUCE
1. Set up a KeeShare container in KeePassXC
2. Save it to a Samba share (or any other KIO-managed remote, presumably)
3. Observe the mount address KeePassXC uses (the text in the green bar)

OBSERVED RESULT

The mount address looks like this:

/run/user/1000/doc/56b810f0/my-share.kdbx.share

With the '56b810f0' bit in the middle being different on every boot.

EXPECTED RESULT

The mount address is deterministic and works across reboots.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora Kinoite 38
(available in About System)
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.11

ADDITIONAL INFORMATION

I've looked into working around this myself via kioclient and a systemd unit,
but kioclient doesn't appear to have a 'mount' command or similar.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to