Ubuntu bug reporting for snaps (was: Should we remove chromium-browser from the archive?)

[Olivier Tilloy]

On Tue, Feb 8, 2022 at 8:57 PM Sebastien Bacher <seb128 at ubuntu.com> wrote:
>
> Hey Olivier, thanks for raising the topic!
>
> Le 08/02/2022 à 19:33, Olivier Tilloy a écrit :
> >   - a custom apport hook that collects additional information about the
> > snap and its dependencies
>
> I'm going to sidetrack slightly the discussion in a new topic to address
> that point. I think that's a problem we need to resolve for snaps. We
> added some hooks to apport directly for subiquity or
> ubuntu-desktop-installer but it would be better if ubuntu-bug was able
> to find hooks provided by the snaps (either by having snapd exporting
> them to a system location or by teaching ubuntu-bug to look into
> /snap/<...>/current/<somedir>.

A good first step, not going as far as enabling snaps to expose custom
hooks, would be for apport to attach standard additional information
when reporting a bug for a snap (in the add_snap_info function?):

  - snap changes --abs-time $SNAPNAME
  - snap connections $SNAPNAME
  - snap info --abs-time $SNAPNAME
  - for PROVIDER in $(grep default-provider
/snap/$SNAPNAME/current/meta/snap.yaml | uniq | cut -d: -f2); do snap
info --abs-time $PROVIDER; done
  - snap info --abs-time $(grep base:
/snap/$SNAPNAME/current/meta/snap.yaml | cut -d: -f2)

Of course, custom hooks would be a nice addition.