Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can not open Attachments #14

Closed
mlthlschr opened this issue May 2, 2018 · 1 comment
Closed

Can not open Attachments #14

mlthlschr opened this issue May 2, 2018 · 1 comment

Comments

@mlthlschr
Copy link

C&P from official keepassXC github issue 1891. Looks like it is some kind of flatpak problem?!

I can not open any attachment in my KeepassXC. Within KeepassX it is possible.

Expected Behavior

Double-click an attachment of an entry should open it.

Current Behavior

Double-clicking the attachment of an entry leads to nothing happening.
Within Entry edit mode - Advanced - Open attachment leads to "Unable to open attachments: ... Cant open file ..."

Steps to Reproduce (for bugs)

Way A:

  1. Choose entry with attached file
  2. Check attachments tab
  3. Double click attachment

Way B:

  1. Double click entry with attached file (Edit entry mode)
  2. Go to advanced
  3. Choose attachment
  4. Click "Open"

Context

Opening attachment.

Debug Info

KeePassXC - Version 2.3.1
Revision: 2fcaeea
Distribution: Flatpak

Libraries:

  • Qt 5.10.1
  • libgcrypt 1.7.3

Operating system: Linux 4.9.0-6-amd64
CPU architecture: x86_64
Kernel: linux 4.9.0-6-amd64

Enabled extensions:

  • Auto-Type
  • Browser Integration
  • Legacy Browser Integration (KeePassHTTP)
  • SSH Agent
  • YubiKey
@AsavarTzeth
Copy link
Collaborator

This is probably an issue with the KeePassXC not being designed to work with portal API's. For example, we have similar issues like #13.

In other words it is something upstream is going to have to learn about and consider during development. Since KeePassXC is officially distributed as a snap, and snaps also are adopting the xdg-desktop-portal API's, there should be no lack of motivation.

Thanks to this issue, I got reminded about this and took the opportunity to inform the upstream developer team and offering my assistance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants