qua 11 jun 2025 às 15:08:33 (1749665313), [email protected] enviou: > Hi André, > > André Batista <[email protected]> writes: > > > 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? > > Integration in IceCat is broken for me (integration in LibreWolf only > work reliably for a very short period of time for me, after some > semi-random bit twiddling). > > It broke between cfa2de2a77df3876061c8d26c104d2ebbae2631b and > 2ed0bd5875dd046ef4a3186bc58e022a05b0e751, if I’m not mistaken. >
That would exclude the last changes to keepassxc, but include those browsers being upgraded to their latest versions. So maybe their upgrade messed up something on the users profiles. Searching the issue track, I've found an old issue that at first appeared to be related to browser's upgrade, but turned out to be AppArmor related: <https://github.com/keepassxreboot/keepassxc-browser/issues/1863> Do you use AppArmor? > Specifically, when clicking on the “Reload” button of the KeepassXC > dialog in IceCat, I see this error on IceCat’s stderr: > > JavaScript error: undefined, line 0: Error: The operation failed for an > operation-specific reason > > Admittedly not a very insightful message. :-) > Meme worthy indeed. They provide a trobleshooting guide for the extension at: <https://github.com/keepassxreboot/keepassxc-browser/wiki/Troubleshooting-guide> I'll try to upgrade the extension and check things locally, but I'm a bit short on time right now. So, if anyone can, please take the lead. Cheers!
