Hi Nathan, The testing was done on 24.04 since at the time I was running Linux on my main desktop to see how the ecosystems being getting on (and since I've swapped from NVidia to Intel's Battlemage, for reasons I'm sure you can guess!).
The snap store now allows users to download older revisions, would it be possible for you to be able to identify the stable release revision around the 16th of June, since that's when the Github PR was made and would have been tested on the same day. If you can let me know the revision I'd be happy to try an older release and confirm if this is or isn't a regression, but my memory and what I've written down suggests this is a regression and on the Github PR where e.g., Brave snap is shown as a failure was specifically to highlight that it was Chromium's snap and not Chromium generally that was compatible with this feature. Hopefully testing it with an older version of Chromium would give some reassurances on whether this is infact a regression or I've gone mad and it's new functionality entirely. -- 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/2095385 Title: Chromium Snap (Ubuntu 24.10) regression in WebExtensions Portal leading to loss of functionality entirely Status in chromium-browser package in Ubuntu: New Bug description: Context: https://github.com/keepassxreboot/keepassxc/pull/10906 In Q2 2024, the Chromium snap was tested with KeepassXC's browser extension which relies upon the currently Ubuntu specific XDG Portals patches. Both the Portal package itself and the Browsers must make use of this interface to facilitate a sandbox mediation where the browser can connect to the local installed package, in this case I'm showing KeepassXC but my expectation is this is broken for every usecase of Webextensions. Due to a recent user report in the link above; I've checked this again more recently using Ubuntu 24.10 in a LiveCD environment with no changes to any packages apart from installing Chromium's snap and KeepassXC's snap. Chromium appears to have lost functionality entirely, whereas on e.g., Firefox, this functionality still works and the browser can connect. Reproduction Steps: 1) sudo snap install chromium keepassxc 2) Open KeepassXC, set up a database file (it can be a dummy empty database with a weak password for testing this) 3) Enable the Web Browser functionality in the KeepassXC settings, select Chromium (and Firefox). 4) In Chromium and Firefox, install the KeepassXC extensions from their relevant extension websites. 5) Attempt to connect the browser to the snap via the web extension icon. Expected results: The portals interface should pop up once asking for permission, followed by KeepassXC itself reacting and presenting its own interface to setup an encryption key for the connection; this second stage of KeepassXC responding to the connection request sufficiently shows the connection is working as expected. Actual results: This works for Firefox still, but no longer works for Chromium, despite working in the past. Electing to ignore the suggested terminal outputs below because I'm hoping the above is already clear enough to suggest that there's likely a portals patch Chromium's snap has been carrying that has either been removed or regressed to be functionless, this is covered by the basic `desktop` snap interface and that's connected by default; this wouldn't be a sandboxing issue and I'm not expecting anything useful in the outputs for this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2095385/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
