Hi Nathan, Can you confirm to me that my attachment file is enough to reproduce the bug?
I'm not sure if I have attached the file correctly, sorry for that. ** Description changed: + How the reproduce the bug: + https://bugs.launchpad.net/ubuntu/+source/chromium- + browser/+bug/2121676/+attachment/5903558/+files/how-to-reproduce.zip + Hi, I'm am on Ubuntu 24.04. I'm using Chromium via snap with this version: ```sh $ snap list chromium Name Version Rev Tracking Publisher Notes chromium 139.0.7258.138 3235 latest/stable canonical✓ - ``` I have installed the extension KeePassXC-Browser version 1.9.9.3 to connect Chromium to my KeePassXC instance 2.7.10 (and to fill HTTP forms automatically with my logins/passwords in KeepPassXC). But it doesn't work. The extension prints this message: ```txt KeePassXC-Browser has encountered an error: Cannot connect to KeePassXC. Check that browser integration is enabled in KeePassXC settings. ``` But my KeePassXC settings are perfectly OK. For instance, if I run Chromium without snap like this: - ```sh # To run an unboxed Chromium instance. /snap/chromium/current/usr/lib/chromium-browser/chrome --user-data-dir=/home/flaf/snap/chromium/common/chromium ``` the extension KeePassXC-Browser works perfectly without any change (HTTP forms are well automatically filled with my logins/passwords). So the problem probably comes from the snap encapsulation. It's a well-known problem which is appeared with the snap encapsulation. For instance, there was exactly the same problem with Firefox when it was switched to snap, and it was eventually resolved. - - Note: there is a similar bug here https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2095385 which has been set to "status=Invalid" because the term of "regression" in the summary field is inappropriate. Indeed, the extension has never worked since Chromium switched to snap. But I think it's just a misunderstanding. The person who created this ticket probably meant that the extension no longer works since Chromium switched to snap. + Note: there is a similar bug here + https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2095385 + which has been set to "status=Invalid" because the term of "regression" + in the summary field is inappropriate. Indeed, the extension has never + worked since Chromium switched to snap. But I think it's just a + misunderstanding. The person who created this ticket probably meant that + the extension no longer works since Chromium switched to snap. Regards. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2121676 Title: Chromium (via snap) on Ubuntu 24.04: extension keepassxc-browser doesn't work Status in chromium-browser package in Ubuntu: Triaged Bug description: How the reproduce the bug: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2121676/+attachment/5903558/+files/how-to-reproduce.zip Hi, I'm am on Ubuntu 24.04. I'm using Chromium via snap with this version: ```sh $ snap list chromium Name Version Rev Tracking Publisher Notes chromium 139.0.7258.138 3235 latest/stable canonical✓ - ``` I have installed the extension KeePassXC-Browser version 1.9.9.3 to connect Chromium to my KeePassXC instance 2.7.10 (and to fill HTTP forms automatically with my logins/passwords in KeepPassXC). But it doesn't work. The extension prints this message: ```txt KeePassXC-Browser has encountered an error: Cannot connect to KeePassXC. Check that browser integration is enabled in KeePassXC settings. ``` But my KeePassXC settings are perfectly OK. For instance, if I run Chromium without snap like this: ```sh # To run an unboxed Chromium instance. /snap/chromium/current/usr/lib/chromium-browser/chrome --user-data-dir=/home/flaf/snap/chromium/common/chromium ``` the extension KeePassXC-Browser works perfectly without any change (HTTP forms are well automatically filled with my logins/passwords). So the problem probably comes from the snap encapsulation. It's a well-known problem which is appeared with the snap encapsulation. For instance, there was exactly the same problem with Firefox when it was switched to snap, and it was eventually resolved. Note: there is a similar bug here https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2095385 which has been set to "status=Invalid" because the term of "regression" in the summary field is inappropriate. Indeed, the extension has never worked since Chromium switched to snap. But I think it's just a misunderstanding. The person who created this ticket probably meant that the extension no longer works since Chromium switched to snap. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2121676/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
