I don't think we could/should warn because we don't know for sure which content slot should be used, just because the default-provider is disabled doesn't mean that the user isn't trying to use some other provider of the content interface.
We could maybe expose some additional property on interface slots which forces a warning to be exposed, but that would be a fair amount of work. What would be easier and more preferable I think (that would also benefit more snaps) is to update the extension hook that is being used here to use `snapctl is-connected ...` on all the content interface plugs that should be coming from the platform snaps, that code if put into upstream snapcraft would benefit all snaps built with the extension that presumably all require using a platform snap. -- 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/1915712 Title: [snap] configure hook fails because the gnome-3-28-1804 platform snap isn't connected Status in chromium-browser package in Ubuntu: Incomplete Status in snapd package in Ubuntu: Incomplete Bug description: happened on do-release-upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 87.0.4280.66-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18 Uname: Linux 4.15.0-135-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-VGA-1: enabled: enabled dpms: On status: connected edid-base64: AP///////wAEcmOt9h4RchURAQMIJh546JrlplhJmSMRUFS/7wABAQEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAeC0RAAAeAAAA/QA4Sx5TDgAKICAgICAgAAAA/wBMNzgwQzA1NDQwNDQKAAAA/ABBTDE5MTYKICAgICAgAGE= modes: 1280x1024 1280x1024 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400 Date: Mon Feb 15 13:26:20 2021 Desktop-Session: 'None' 'None' '/usr/local/share:/usr/share:/var/lib/snapd/desktop' Env: 'None' 'None' ErrorMessage: »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück InstallationDate: Installed on 2017-06-27 (1328 days ago) InstallationMedia: Kubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) InstalledPlugins: Load-Avg-1min: 0.61 Load-Processes-Running-Percent: 0.2% MachineType: Hewlett-Packard HP Pro3500 Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-135-generic root=UUID=093e88ea-7b5e-4e39-b56c-03b28ad06dd2 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 87.0.4280.66-0ubuntu0.18.04.1 failed to install/upgrade: »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to focal on 2021-02-15 (0 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: AMI dmi.bios.version: 8.17 dmi.board.name: 2ABF dmi.board.vendor: Foxconn dmi.board.version: 3.20 dmi.chassis.asset.tag: CZC34935PY dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.17:bd10/25/2013:svnHewlett-Packard:pnHPPro3500Series:pvr:rvnFoxconn:rn2ABF:rvr3.20:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Pro3500 Series dmi.sys.vendor: Hewlett-Packard modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1915712/+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
