ubuntu-bug doesn't know how to file bugs against snaps

Bug #1861082 reported by Seth Arnold on 2020-01-28
24
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Snap Store
Undecided
Unassigned
Snapcraft
Undecided
Unassigned
snapd
Medium
Unassigned
apport (Ubuntu)
Undecided
Unassigned

Bug Description

Hello, I had problems with subiquity in the focal live server install image. I tried to use 'ubuntu-bug subiquity' to report the bug, but ubuntu-bug apparently cannot file bug reports against snaps.

This is frustrating that users need to know which portions of Ubuntu are delivered via debs, which portions are delivered by snaps, and try to find a way to report bugs correctly.

ubuntu-bug should know how to report bugs for Canonical software.

Thanks

tags: added: champagne
Launchpad Janitor (janitor) wrote :

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

Changed in apport (Ubuntu):
status: New → Confirmed
Dimitri John Ledkov (xnox) wrote :

So, snaps in the snapstore can declare a contact url, where one can file bug reports.

I don't see these to be exposed on the system, but maybe I don't know the localhost APIs for that.

I do wonder if there can be some standartesation done, for example, if the contact url is +filebug on a launchpad project, maybe apport should be able to file bugs against the launchpad project for that snap.

Ie. ideally ubuntu-bug core20 subiquity git-ubuntu would all work.

@snapd @snapcraft @snapstore - is there a standard for where to file bug reports, and how can apport query and use it? Can we start enforcing branced snaps to provide that?

Changed in apport (Ubuntu):
status: Confirmed → Incomplete
Brian Murray (brian-murray) wrote :

I think it's worth mentioning that 'ubuntu-bug git-ubuntu' does present a dialog telling you that "it is about a snap published by canonical. Contact them via https://bugs.launchpad.net/usd-importer/+filebug for help". So apport does try to point you in the right direction.

You can see this code in apport/ui.py.

Dimitri John Ledkov (xnox) wrote :

aha, so:

$ snap info --verbose git-ubuntu | grep contact
contact: https://bugs.launchpad.net/usd-importer/+filebug

I wonder, if we can improve apport to actually upload / start filing a bug report on launchpad, if it points to a launchpad +filebug url?

Can we enforce for contact to be set to something sensible, for all Canonical published projects?

Also does apport know how to open bug reports against launchpad "upstream" (not ubuntu distro-package) projects? And i guess also github issues?

Changed in snapd:
status: New → Triaged
importance: Undecided → Medium
Dimitri John Ledkov (xnox) wrote :

So, in addition to the contact: field on all seeded snaps / canonical snaps.

Re: installers
We generally do have special cases in ubuntu-bug for "debian-installer", "ubiquity", and "subiquity", as anybody should be able file bug reports against "installation". Whether or not, they are installing or completed the install. That needs more special cases in apport.

For snaps that don't declare contact.... Maybe we should direct people at the snapstore URL to try to find who published the package there? Or like direct them at "snaps-on-ubuntu" project that has lots of bugs against any snap out there?

I wonder how other distributions handle the "where to file bugs against snaps on $DISTRO".

tags: added: id-5e73c372136ba285edff6d4d
Adam Novak (interfect) wrote :

I encountered this when trying to report a bug in the snap-store, which as far as I can tell is the new default package manager. It looks pretty silly to see Apport disclaiming responsibility for the package manager.

It knows the snap is published by "canonical". Maybe everything published by "canonical" should be special-cased.

Steve Langasek (vorlon) wrote :

Based on the latest comments, "incomplete" is wrong, we have enough information here for apport to start using the contact field.

Changed in apport (Ubuntu):
status: Incomplete → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers