@Stanz Your crash may be due to a bug that's already been reported, but it doesn't seem to be due to *this* bug. This bug appears to be related to time-zone issues, occurs much earlier in the installation, displays different messages than yours, and (at least in my case) does not necessarily result in the installation begin aborted. Reporting your crash here as a comment is unlikely to help get the underlying bug resolved. If you have not done so already, you should report it, following the instructions at https://help.ubuntu.com/community/ReportingBugs as well as any bug reporting instructions provided by the Apport bug-reporting utility or by Launchpad in your web browser. If you have not done so already, it's probably a good idea to search for the bug before reporting it, but if you accidentally file a duplicate bug in a popular package like ubiquity, it will probably be identified and flagged as a duplicate in short order.
As for the user-friendliness issue, Natty is alpha software and therefore should be expected to behave badly and require some technical skill to deal with. The problem of ubiquity failing in a user-unfriendly matter will be resolved when it is made not to fail; plus, most of the time when ubiquity crashes, the user is provided with a message that they can understand without technical skill. If you can identify a specific way in which ubiquity could be more user-friendly, you may want to file a bug report / feature request here on Launchpad. Apport bug reports with automatically collected and attached crash data are private by default because they could contain sensitive personal information like passwords or credit card numbers. Ubiquity wouldn't take your credit card information, but it could certainly take your password (you have to give it the username and password for the initial, administrative user). Many people reuse their passwords on multiple computers or even on Internet services (like Launchpad itself); it would be bad to automatically render that information accessible by everyone on the Internet. If you are confident that your bug report does not contain sensitive personal information, then you can always change it status to public. If you are not confident of this, then you should (1) examine the attached files yourself to ensure they don't contain such information, or (2) wait for the files that potentially contain such information to be automatically processed and removed (at which point the bot doing the processing and removing marks it public), or (3) for them to be examined by a member of the Bug Squad for data that looks like passwords or credit card numbers (at which point the Bug Squad member marks the bug public). On the other hand, if you are complaining that bots on Launchpad sometimes automatically mark a new bug report as a duplicate of a bug that is still private (sometimes even when the bug report marked as a duplicate is itself public and has multiple non-bot subscribers), that *is* arguably a problem. Since most private bugs become public, it is also arguably not a problem. See bug 396406, bug 157899, and bug 434733. You might also find more related bug reports / feature requests by searching for bugs in Launchpad itself (for example, https://launchpad.net/+search?field.text=private+duplicate). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/703476 Title: ubiquity crashed with TypeError in changed(): value is of wrong type for this column -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
