Add support for KeePassXC flatpak app #7
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Please see #8 This can now be further simplified, since Flatpak is no longer special-cased. |
WhyNotHugo
pushed a commit
to WhyNotHugo/keepassxc-proxy-rust
that referenced
this pull request
Jun 2, 2022
Rather than try a single path, try all supported paths, in the preferred order. This avoids breaking compatibility with previous KeePassXC versions. See: keepassxreboot/keepassxc#8018 Fixes: varjolintu#8 Supercedes: varjolintu#7
|
Let's close this if #10 already solves it. |
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds support for KeePassXC packaged as Flatpak.
The flatpak app places the socket at a path different from non-flatpak KeePassXC installation,
$XDG_RUNTIME_DIR/app/org.keepassxc.KeePassXC/(instead of directly under$XDG_RUNTIME_DIR/), so check the flatpak-specific path first, and if it exists - try to connect to the socket within it.