** Description changed:
+ [Impact]
+ ubuntu-bug responds with a misleading statement asked to report a bug about
an executable path which starts with /snap/bin
+
+ [Test Case]
+ 1) Run ubuntu-bug /snap/bin/juju
+ 2) Read "/snap/bin/juju does not belong to a package"
+
+ With the version of apport in -proposed you'll receive a more
+ informative message about where you might get help regarding the issue
+ you are experiencing.
+
+ [Regression Potential]
+ The new code only affects executables that start with '/snap/bin' so the only
danger is if the newly added code contains an error which would cause a
traceback.
+
+ Original Report
+ ---------------
apport's ui.py file contains the following code:
- 809 # executable?
- 810 elif '/' in self.args[0]:
- 811 pkg = apport.packaging.get_file_package(self.args[0])
- 812 if not pkg:
- 813 optparser.error('%s does not belong to a package.' %
self.args[0])
- 814 sys.exit(1)
- 815 self.args = []
- 816 self.options.filebug = True
- 817 self.options.package = pkg
+ 809 # executable?
+ 810 elif '/' in self.args[0]:
+ 811 pkg = apport.packaging.get_file_package(self.args[0])
+ 812 if not pkg:
+ 813 optparser.error('%s does not belong to a package.' %
self.args[0])
+ 814 sys.exit(1)
+ 815 self.args = []
+ 816 self.options.filebug = True
+ 817 self.options.package = pkg
This will not provide any useful information about what to do if the
'executable' is provided by a snap. Information similar to
https://code.launchpad.net/~juliank/ubuntu/bionic/apport/snap/+merge/342207
should be provided if the path is from a snap.
** Description changed:
[Impact]
- ubuntu-bug responds with a misleading statement asked to report a bug about
an executable path which starts with /snap/bin
+ ubuntu-bug responds with a misleading statement asked to report a bug about
an executable path which starts with /snap/bin and the response is different
than if you were to use the snap name e.g. ubuntu-bug juju
[Test Case]
1) Run ubuntu-bug /snap/bin/juju
2) Read "/snap/bin/juju does not belong to a package"
With the version of apport in -proposed you'll receive a more
informative message about where you might get help regarding the issue
you are experiencing.
[Regression Potential]
The new code only affects executables that start with '/snap/bin' so the only
danger is if the newly added code contains an error which would cause a
traceback.
Original Report
---------------
apport's ui.py file contains the following code:
809 # executable?
810 elif '/' in self.args[0]:
811 pkg = apport.packaging.get_file_package(self.args[0])
812 if not pkg:
813 optparser.error('%s does not belong to a package.' %
self.args[0])
814 sys.exit(1)
815 self.args = []
816 self.options.filebug = True
817 self.options.package = pkg
This will not provide any useful information about what to do if the
'executable' is provided by a snap. Information similar to
https://code.launchpad.net/~juliank/ubuntu/bionic/apport/snap/+merge/342207
should be provided if the path is from a snap.
** Changed in: apport (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: apport (Ubuntu Bionic)
Assignee: (unassigned) => Brian Murray (brian-murray)
** Changed in: apport (Ubuntu Cosmic)
Status: Triaged => In Progress
** Changed in: apport (Ubuntu Cosmic)
Assignee: (unassigned) => Brian Murray (brian-murray)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1760220
Title:
ubuntu-bug with program path says as a snap does not belong to a
package
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Bionic:
In Progress
Status in apport source package in Cosmic:
In Progress
Bug description:
[Impact]
ubuntu-bug responds with a misleading statement asked to report a bug about
an executable path which starts with /snap/bin and the response is different
than if you were to use the snap name e.g. ubuntu-bug juju
[Test Case]
1) Run ubuntu-bug /snap/bin/juju
2) Read "/snap/bin/juju does not belong to a package"
With the version of apport in -proposed you'll receive a more
informative message about where you might get help regarding the issue
you are experiencing.
[Regression Potential]
The new code only affects executables that start with '/snap/bin' so the only
danger is if the newly added code contains an error which would cause a
traceback.
Original Report
---------------
apport's ui.py file contains the following code:
809 # executable?
810 elif '/' in self.args[0]:
811 pkg = apport.packaging.get_file_package(self.args[0])
812 if not pkg:
813 optparser.error('%s does not belong to a package.' %
self.args[0])
814 sys.exit(1)
815 self.args = []
816 self.options.filebug = True
817 self.options.package = pkg
This will not provide any useful information about what to do if the
'executable' is provided by a snap. Information similar to
https://code.launchpad.net/~juliank/ubuntu/bionic/apport/snap/+merge/342207
should be provided if the path is from a snap.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1760220/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
