Crash reporter makes reporting crashes unnecessarily difficult
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Apport |
New
|
Undecided
|
Unassigned | ||
subiquity |
New
|
Undecided
|
Unassigned | ||
ubuntu-desktop-provision |
New
|
Low
|
Unassigned |
Bug Description
I experienced four installer failures while trying to install the latest Ubuntu. After every failure, I was offered the chance to report the bug. Which I did. Or, I thought I did. There is no interface indicating that your bug has not been submitted unless you then log in with an ubuntu one account (which you may not have or may not remember having). In fact, the first three times that I hit the bug, I closed the installer (and apparently, bug reporter) because nothing appeared to be happening. There was no indication that Firefox would be launched to log me into Ubuntu One, or *why* I needed to log into Ubuntu One. I eventually logged into it, after multiple login and password reset attempts. 10-15 minutes after my fourth install failure, I was finally able to submit a bug.
As the bug causes the 23.10 installer to fail consistently, it's probably pretty important that it be reported. But if we don't know if the report has been made, or if it is unnecessarily difficult to submit a bug report, the bug report won't get made.
For comparison, on macOS, a window pops up with the bug report info, which you can view easily. You click on *one button* to send the report to Apple. You can submit anonymously, or provide more info if you wish.
affects: | ubuntu-desktop-installer → ubuntu-desktop-provision |
Changed in ubuntu-desktop-provision: | |
importance: | Undecided → Low |