Failing auto-connect to gnome-42-2204

[James-Carroll]

I think you might be running into the same issue as Opera’s recently had:

@jslarraz

Although you are generally right, assertions defined for plugs have precedence. That means (if I’m right) that if opera assertion contains any information about content interfaces in its plugs, the assertion of the slot (the content snap) would not be taken into consideration. As opera is plugging chromium-ffmpeg I think we also need to explicitly allow other content snaps (even if they have global auto-connection at the slot side) in the opera declaration.

Your snap currently has:

plugs:
  browser-support:
    allow-auto-connection: true
  content:
    allow-auto-connection:
      -
        plug-attributes:
          content: $SLOT(content)
        slot-attributes:
          content: chromium-ffmpeg-115016
        slot-snap-id:
          - XXzVIXswXKHqlUATPqGCj2w2l7BxosS8

So I think in this case, the Store team need to do as was done for Opera and grant an override to make the Gnome snaps autoconnect properly, since they’re effectively at conflict with the ffmpeg overrides.

Whilst unrelated to your issue, I’d really encourage you to swap compression: xz to compression: lzo, whilst it uses a fair bit more disk usage, the launch speeds of your browser will be significantly impacted on lower resource machines with xz. Almost all new desktop orientated snaps will be using LZO leaving XZ primarily for IOT where disk space is at a premium.

Otherwise, once you have the gnome extension autoconnecting, I’d personally also recommend re-assessing your stage packages list, e.g, - libgtk-3-0 wouldn’t be needed because the Snap already has it via the extension. This would let you trim down the filesize but more importantly avoids duplicating potentially incompatible libraries (not so much a problem with GTK3 these days, but in GTK4 for example, the repo versions will likely be older than the extension versions, and this is implicitly asking to mix both).