I had to re-install due to a corrupted root partition. All of my partitions other than /boot (/, /home/, /data/, swap) are encrypted. I first unlocked them using `udiskctl unlock -b /dev/sdXY`. I then ran ubiquity, and used manual partition selection to assign them to the appropriate luks partitions. Installation seemed to go fine, but when I entered my user details, I got an error saying "ubi-usersetup failed with error 1". When I looked in /var/log/syslog, there were no clear messages related to ubi-usersetup (other than it crashed), but there was a message `cannot stat '/etc/crypttab': no such file or directory`. At this point, pressing 'ignore' caused ubiquity to freeze on the last screen, with no messages, 'retry' took me back to the user-data entry panel, and 'cancel' aborted and failed the install. When I looked, there was no /target/etc/crypttab, so I just copied the one from /etc/crypttab (which only contained a single commented header line, no actual info). That fixed the problem, and after pressing 'retry' in ubiquity, the ubi-usersetup did not fail again, and setup continued as normal. I will now follow the instructions at http://askubuntu.com/questions/853078/reinstall-to-existing-encrypted-partitions/868726 to fix crypttab on the new system. No sure if this is a neon bug, a ubiquity bug, or a feature, but I figured I'd post it, as I suspect other people will hit this sometimes, and the work-around is useful.
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!