[SRU] ubuntu-bug doesn't know how to file bugs against snaps
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Snap Store Server |
New
|
Undecided
|
Unassigned | ||
Snapcraft |
New
|
Undecided
|
Unassigned | ||
snapd |
Triaged
|
Medium
|
Unassigned | ||
apport (Ubuntu) |
Fix Released
|
Undecided
|
Lukas Märdian | ||
Focal |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
Users of Ubuntu 20.04 are not able to easily report bugs against applications provided as a snap.
[Test Case]
Install subiquity snap:
# sudo snap install subiquity --classic
subiquity 20.06.1 aus Canonical✓ installiert
# snap list | grep subiquity
subiquity 20.06.1 1938 latest/stable canonical* classic
ubuntu-bug subiquity results in message:
# LANGUAGE="en_US" apport-cli subiquity
*** Collecting problem information
The collected information can be sent to the developers to improve the
application. This might take a few minutes.
...dpkg-query: no packages found matching subiquity
*** You are about to report a bug against the deb package, but you also a have snap published by canonical installed. You can contact them via https:/
What would you like to do? Your options are:
Y: Yes
N: No
C: Cancel
=== New/Expected Result ===
ubuntu-bug <package or snap name> should ask the user if he/she wants to report the bug against the snap or deb package, if both are installed. If the snap is chosen, the "Snap" and "SnapSource" fields should be part of the report:
# LANGUAGE="en_US" apport-cli subiquity
*** Collecting problem information
The collected information can be sent to the developers to improve the
application. This might take a few minutes.
...dpkg-query: no packages found matching subiquity
*** You have two versions of this application installed, which one do you want to report a bug against?
Choices:
1: subiquity 20.06.1 (stable) snap
2: subiquity (1938) deb package
C: Cancel
Please choose (1/2/C): 1
.
*** Send problem report to the developers?
After the problem report has been sent, please fill out the form in the
automatically opened web browser.
What would you like to do? Your options are:
S: Send report (46.1 KB)
V: View report
K: Keep report file for sending later or copying to somewhere else
I: Cancel and ignore future crashes of this program version
C: Cancel
Please choose (S/V/K/I/C): V
Make sure the following two fields are part of the generated report:
== Snap =======
subiquity 20.06.1 (stable)
== SnapSource =======
subiquity
[Regression Potential]
Small; the change adds a new add_snap_info() method to report.py and is triggered in the ui.py logic only in cases which would have otherwise lead to an error message. Furthermore, the change has been uploaded to Groovy some while ago where it is being used and tested.
[Original Bug Report]
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 |
Changed in snapd: | |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: | added: id-5e73c372136ba285edff6d4d |
Changed in apport (Ubuntu Focal): | |
milestone: | none → ubuntu-20.04.1 |
tags: | removed: champagne |
Changed in apport (Ubuntu): | |
assignee: | nobody → Lukas Märdian (slyon) |
Changed in apport (Ubuntu Focal): | |
assignee: | nobody → Lukas Märdian (slyon) |
description: | updated |
summary: |
- ubuntu-bug doesn't know how to file bugs against snaps + [SRU] ubuntu-bug doesn't know how to file bugs against snaps |
description: | updated |
tags: | added: id-5eeb87fddafe19544a50da51 |
Changed in apport (Ubuntu Focal): | |
status: | Triaged → In Progress |
Changed in apport (Ubuntu Focal): | |
assignee: | Lukas Märdian (slyon) → nobody |
Changed in apport (Ubuntu): | |
milestone: | ubuntu-20.04.1 → none |
Status changed to 'Confirmed' because the bug affects multiple users.