Thanks for the nifty test case! I've added it to <https://wiki.ubuntu.com/ErrorTracker#non-app-crash>.
As you can see there, if in this situation we used buttons for specifying whether to send the error report, it would be inconsistent with every other case, where we use a checkbox for specifying whether to send the error report. As in the other cases, "Continue" refers to continuing to use Ubuntu in general, not the command line program in particular. Normally in an error alert the button text would be "OK", but I thought that might be a little too grating in the case where something has just crashed on you. Now, it might be that most people experiencing a command-line crash think that "Continue" refers to the terminal command, but I'd want more than anecdotal evidence of that. Changing the button text based on whether the checkbox is checked is an interesting proposal, but it makes the assumption that people will have the state of the checkbox in mind when they click the button. That's unlikely on systems where the checkbox is unchecked by default -- and even less likely, when it is configured not to be present at all! In those cases, "Cancel" would seem like a non-sequitur: cancel what? Maybe there's a better label than "Continue", but I don't know what it would be. If we could get away with a little cheekiness, "Oh Well" or "Bother" might be possibilities. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/938706 Title: Confusing "Continue" button for command line program crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/938706/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
