Gather additional info when creating a bug about a snap

Bug #1960964 reported by Brian Murray
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
Fix Released
Medium
Brian Murray

Bug Description

On the ubuntu-devel mailing list[1] it was suggested that apport should collect the following additional information when reporting a bug about a snap:

  - 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)

This should be fairly straightforward we just need to decide on names for the keys in the report.

[1] https://lists.ubuntu.com/archives/ubuntu-devel/2022-February/041836.html

Tags: fr-2057
tags: added: fr-2057
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in apport (Ubuntu):
status: New → Confirmed
Revision history for this message
Olivier Tilloy (osomon) wrote :

For reference, the chromium-browser package in focal and upwards is a simple wrapper that installs the chromium snap, and it has a custom apport hook that attaches some of this information. The names of the keys there are:

 - Snap.Changes
 - Snap.Connections
 - Snap.Info.chromium
 - Snap.Info.core
 - Snap.Info.core18 (this needs to be updated because it is currently hardcoded in the hook, but the snap has since been rebased on core20)
 - Snap.Info.gtk-common-themes

See bug #1958810 for an example.

There isn't any tooling that expects these specific names though, so as far as I'm concerned they can be changed.

Changed in apport (Ubuntu):
status: Confirmed → In Progress
importance: Undecided → Medium
assignee: nobody → Brian Murray (brian-murray)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package apport - 2.20.11-0ubuntu78

---------------
apport (2.20.11-0ubuntu78) jammy; urgency=medium

  [ Olivier Gayot ]
  * Expect whoopsie to be started using path-based activation.
  * Pass timeout option to apport-autoreport so that whoopsie has time to
    upload all reports.
  * Use timer-based activation for apport-autoreport in addition to path-based
    activation (on modification of /var/crash).
  * Some code cleanup in data/whoopsie-upload-all.
  * Use unbuffered logging in data/whoopsie-upload-all.
  * Touch the /var/crash directory in data/whoopsie-upload-all so that
    whoopsie activates when needed.
  * Stop removing .crash files after they are successfully uploaded by
    whoopsie.

  [ Brian Murray ]
  * When collecting information about a snap gather some additional details,
    thanks to Olivier Tilloy for the idea. (LP: #1960964)
  * Update the recommended version of whoopsie for apport-noui.

 -- Brian Murray <email address hidden> Tue, 22 Feb 2022 17:13:48 -0800

Changed in apport (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.