I was able to recreate this by running apport-collect on bug 1766787 and
it crashed whether I choose to view the report or keep it. The same
thing happens with a ubiquity bug report too. However, when running
apport-collect on an apport bug report a report is created without a
ProblemType it just is not checked for anything so the process doesn't
crash.
Anyway, this pretty seriously impacts the usability of apport-collect.
** Summary changed:
- apport-collect with debian-installer doesn't create a ProblemType in the
report
+ apport-collect doesn't create a ProblemType in the report
** Changed in: apport
Status: New => Triaged
** Changed in: apport (Ubuntu)
Status: New => Triaged
** Changed in: apport (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766794
Title:
apport-collect doesn't create a ProblemType in the report
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1766794/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
