no bug reporting method

Bug #1651597 reported by Hadmut Danisch
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Snappy
Fix Released
Undecided
Unassigned

Bug Description

Hi,

I am just trying to get ubuntu core/snappy running on a raspberry.

Unfortunately, the LXC snap has a problem, and I wanted to report the bug.

But: No obvious way to report a bug or to find the developers of the snap.

snap info lxd just says

# snap info lxd
name: lxd
summary: "LXD - the container lighervisor"
publisher: canonical
tracking: stable
installed: 2.6.2 (537) -
channels:
  stable: 2.6.2 (537) -
  candidate: 2.6.2 (537) -
  beta: 2.6.2 (537) -
  edge: git-0ecd86b (758) -

which is just useless.

If all one can do about bugs is to wait, to pray, and to be patient, then you can just forget about snappy. Then it is not robust.

Revision history for this message
Kyle Fazzari (kyrofa) wrote :

It would indeed be nice to show the support URL information that the publisher provides to the store.

Changed in ubuntu-snappy (Ubuntu):
status: New → Confirmed
Revision history for this message
Ads20000 (ads20000) wrote :

Considering the publisher is Canonical, in this case I would file a bug against the LXC package in Ubuntu, but clearly state it's the Snappy package that you're filing against. Otherwise try and figure out who the maintainer is and contact them direct, or, if it's upstream that's packaged it, file a bug on their bug tracker.

But yes, ideally we need an ubuntu-bug command that works for Snaps and, even better, automatically redirects to upstream when necessary.

affects: ubuntu-snappy (Ubuntu) → snapd (Ubuntu)
Oliver Grawert (ogra)
affects: snapd (Ubuntu) → snappy
Revision history for this message
John Lenton (chipaca) wrote :

FWIW, currently snap info does list a "contact" field:

$ snap info lxd
name: lxd
summary: "System container manager and API"
publisher: canonical
contact: https://github.com/lxc/lxd/issues

marking this as fix-released as this landed in February.

Changed in snappy:
status: Confirmed → 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.