Error using KeePassXC integration (couldn't execute "clip")

[apsinthium]

.

[aadcg]

@apsinthium please share you config file.

---

Could be related to 1871bd0.

[aadcg]

On seconds thoughts, this may be because the Flatpak can't locate keepassxc-cli.

@apsinthium what's the output of:

flatpak run engineer.atlas.Nyxt  --eval "(serapeum:resolve-executable \"keepassxc-cli\")" --quit

[aadcg]

@apsinthium you didn't enter the command as I've described. Did you escape the quotes? Please paste flatpak run engineer.atlas.Nyxt --eval "(serapeum:resolve-executable \"keepassxc-cli\")" --quit.

I think you should see something along the lines of

$ flatpak run engineer.atlas.Nyxt  --eval "(serapeum:resolve-executable \"keepassxc-cli\")" --quit

Note that the directories 

'/var/lib/flatpak/exports/share'
'/home/aadcg/.local/share/flatpak/exports/share'

are not in the search path set by the XDG_DATA_DIRS environment variable, so
applications installed by Flatpak may not appear on your desktop until the
session is restarted.

<INFO> [11:12:38] Loading Lisp file #P"/home/aadcg/.config/nyxt/config.lisp".
NIL

[aadcg]

@apsinthium Now you did it correctly. The output differs from the one above.

---

Two things here:

1. The password manager must error when the call (executable interface) returns nil in execute from password.lisp. @aartaka could you address it?
2. We need to understand how to manage system binaries when Nyxt is run as a Flatpak. We already pass --filesystem=host. I need to think.

[aadcg]

The solution to 2. is to invoke the password manager as flatpak-spawn --host keepassxc-cli. But first I need to tweak the Flatpak settings. Then we can test it.

Depends on flathub-infra/flatpak-builder-lint#194.

[aadcg]

@apsinthium are you still interested in testing the password facilities in the Flatpak distribution?

For reference, Flatpak users need to prepend the executable they need to invoke with flatpak-spawn --host. E.g. calling keepassxc-cli becomes flatpak-spawn --host keepassxc-cli. This piece of information should be added to the manual.

[aadcg]

@apsinthium If you're not using the Flatpak, then it makes little sense. Thanks for the collaboration offer nonetheless!

---

For Flatpak users, I expected that the piece of configuration below should work. It seems that I'm missing something about the architecture of password mode. @aartaka any idea?

(define-configuration nyxt/mode/password:password-mode
  ((nyxt/mode/password:password-interface (make-instance 'password:keepassxc-interface))))

(define-configuration password:keepassxc-interface
  ((password:executable (str:split " " "flatpak-spawn --host keepassxc-cli"))))

When attempting to read the slot's value (slot-value), the slot
NYXT::CUSTOMIZE-HOOK is missing from the object
#<STANDARD-CLASS PASSWORD:KEEPASSXC-INTERFACE>.
   [Condition of type SB-PCL::MISSING-SLOT]

Restarts:
 0: [RETRY] Retry EVAL of current toplevel form.
 1: [CONTINUE] Ignore error and continue loading file "/home/aadcg/.config/nyxt/config.lisp".
 2: [ABORT] Abort loading file "/home/aadcg/.config/nyxt/config.lisp".
 3: [LOAD-LISP-RETRY] Retry loading Lisp file.
 4: [QUIT] Run `nyxt:quit' and try again.
 5: [FORCE-QUIT] Run `nyxt:quit' and set `*browser*' to NIL in any case.
 --more--

Backtrace:
 0: ((:METHOD SLOT-MISSING (T T T T)) #<STANDARD-CLASS COMMON-LISP:STANDARD-CLASS> #<STANDARD-CLASS PASSWORD:KEEPASSXC-INTERFACE> NYXT::CUSTOMIZE-HOOK SLOT-VALUE NIL) [fast-method]
 1: ((LAMBDA (SB-PCL::OBJECT) :IN SB-PCL::SLOT-MISSING-INFO) #<STANDARD-CLASS PASSWORD:KEEPASSXC-INTERFACE>)
 2: ((LAMBDA NIL :IN "/home/aadcg/.config/nyxt/config.lisp"))

[aartaka]

Seems like make-password-interface-user-classes doesn't force keepassxc-interface to be a user-class.

[aadcg]

There are 3 topics in this issue:

• Being able to run host commands while running Nyxt as a flatpak;
• Adding the possibility to set the executable commands for a password interface;
• Catching errors when no executable is found for a password interface (Warn on missing password executable #3249).

I've fixed what is strictly related to the Flatpak and I'd suggest @aartaka taking over the remaining issues.