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

KeePassXC-Browser does not connect with KeePassXC #39

Open
jedenastka opened this issue Dec 12, 2020 · 5 comments
Open

KeePassXC-Browser does not connect with KeePassXC #39

jedenastka opened this issue Dec 12, 2020 · 5 comments

Comments

@jedenastka
Copy link

KeePassXC-Browser extension can't connect to native KeePassXC instance.

image

(It says: Key exchange did not succeed.).

I don't know if I should report it here or on KeePassXC-Browser repo, but it works with native Chromium browser provided by Debian so I guess it's not it's fault.

Here is an extenstion activity log: exported_activity_log_oboonakemofpalcgghocfoadofidjkkk.txt

Also the Chromium output:

~ $ flatpak run org.chromium.Chromium --enable-extension-activity-logging
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[39:39:1212/171004.980863:ERROR:vaapi_wrapper.cc(547)] vaInitialize failed (ignore if using Wayland desktop environment): unknown libva error
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[39:39:1212/171004.980971:ERROR:vaapi_wrapper.cc(557)] vaInitialize failed using DRM: unknown libva error
Failed to load cookie file from cookie: Operacja niedozwolona
[41:55:1212/171404.402303:ERROR:object_proxy.cc(621)] Failed to call method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd5: org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown
[41:55:1212/171404.402323:ERROR:kwallet_dbus.cc(100)] Error contacting kwalletd5 (isEnabled)
[41:55:1212/171404.402523:ERROR:object_proxy.cc(621)] Failed to call method: org.kde.KLauncher.start_service_by_desktop_name: object_path= /KLauncher: org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown
[41:55:1212/171404.402535:ERROR:kwallet_dbus.cc(72)] Error contacting klauncher to start kwalletd5
[41:55:1212/171404.402767:ERROR:object_proxy.cc(621)] Failed to call method: org.kde.KWallet.close: object_path= /modules/kwalletd5: org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown
[41:55:1212/171404.402777:ERROR:kwallet_dbus.cc(418)] Error contacting kwalletd5 (close)

My OS:

~ $ inxi -S 
System:
  Host: pecet Kernel: 5.9.0-12.1-liquorix-amd64 x86_64 bits: 64 
  Desktop: KDE Plasma 5.20.4 Distro: Debian GNU/Linux bullseye/sid
@xalt7x
Copy link

xalt7x commented Dec 13, 2020

This issue is probably similar to #34

@gasinvein
Copy link
Member

I think here is also another (probably unrelated) bug: Chromium can't connect to KWallet.

@Erick555
Copy link
Contributor

Try using --talk-name=org.kde.KWallet (you may confirm with --log-session-bus if this is correct dbus address.

@refi64
Copy link
Collaborator

refi64 commented Dec 15, 2020

This is definitely due to native extension hosts. Kwallet would be a different issue however.

@AsavarTzeth
Copy link

AsavarTzeth commented Jan 27, 2021

For reference: flathub/org.keepassxc.KeePassXC#29

When I last worked on something similar for Firefox and KeePassXC (both as flatpaks) all browsers on Flathub lacked the necessary native host extension points. I am happy to see that is no longer the case.

One question though: Would it be possible to standardize the native host extension prefix similar to: org.freedesktop.LinuxAudio.BaseExtension. I would love to work on this, but I dislike the idea of having to maintain a duplicated flatpak extension for each browser.

Edit: How could I miss #49

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

6 participants