Hi Ludo, Daniel et alii, sáb 07 jun 2025 às 22:20:34 (1749345634), [email protected] enviou: > Hi Daniel, > > Daniel Hatton <[email protected]> writes: > > > A couple of weeks ago, the keepasxc-browser-icecat extension on my > > Guix system lost the ability to connect to keepassxc. I'm looking for > > advice on how to diagnose and fix what's wrong, please. > > FWIW, I have the exact same problem, starting two weeks ago or so. > > Cc’ing the ‘mozilla’ team in case they have ideas. >
There's some missing info that would be helpful if any or both of you could provide: Did it start after upgrading packages on the user profile? If so, which was the last working commit and the first broken one? Did it start after a system reconfigure? Same as above. Which of the mozilla browsers were affected/tested? In the last couple of weeks (or so), the browsers have been upgraded, but I also see that one input (quazip-0) was removed from keepassxc on commit abe2738982. Maybe keepassxc-proxy depended on that? Other than that, I've noticed that the browser extension is lagging behind by some releases already and that the communication protocol is said to be under develpment: <https://github.com/keepassxreboot/keepassxc-browser/blob/develop/keepassxc-protocol.md> So maybe those versions became silently incompatible (though the last keepassxc upgrade has been on master for some months already). I'd start by upgrading the extension, instead of trying to debug an old one. Anyhow, mozilla has a section on how to debug native messaging: <https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Native_messaging> and <https://extensionworkshop.com/documentation/develop/debugging/#viewing_log_output> Happy hacking!
