Ubuntu installer crashed

Bug #1820795 reported by Jacob Fox
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Custom partition installation settings.
Opted to download updates and install 3rd party drivers.
Installing alongside Windows 10 and over an existing installation.
Current boot partition set to be formatted as EXT4 and mounted to /boot
Current root partition not formatted, selected BTRFS and mounted to /

Installation crashed part way through.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubiquity 19.04.6.1
ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
Uname: Linux 4.19.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu21
Architecture: amd64
CasperVersion: 1.402
Date: Mon Mar 18 21:39:03 2019
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash ---
LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Jacob Fox (jacob-thefox) wrote :
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

There are some odd errors in UbiquitySyslog.txt I haven't seen before:

Mar 19 04:38:51 ubuntu user-setup: adduser: Only one or two names allowed.
Mar 19 04:38:51 ubuntu ubiquity: chpasswd: (user ) pam_chauthtok() failed, error:
Mar 19 04:38:51 ubuntu ubiquity: Authentication token manipulation error
Mar 19 04:38:51 ubuntu ubiquity: chpasswd: (line 1, user ) password not changed

Could you please tell us more about exactly how you filled in the User Setup screen? Did you use any special characters, or something with spaces under the username field?

Changed in ubiquity (Ubuntu):
status: New → Incomplete
Revision history for this message
Jacob Fox (jacob-thefox) wrote :

Name entered was "localadmin" without the quotes
Machine name was "vader-l"

Don't believe I made any typos. I did a minimal install following this, but with multiple changes. I first made sure to remove the btrfs '@' subvolume and I also did a minimal install with no updates downloaded. If I had to make an educated guess I'd say it was the existing install causing conflicts. "localadmin" was a user that existed in the previous install.

Revision history for this message
Jacob Fox (jacob-thefox) wrote :

Oh, forgot to mention, the second installation attempt with previous installation removed succeeded without error.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.