Crash due to user not figuring out where to set boot.

[Tim Dillenberger]

Trying to do a clean install of Ubuntu and it came up with an error.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: ubiquity 18.10.12
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CasperVersion: 1.399
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 17 13:58:33 2019
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

[Sebastien Bacher (seb128)]

Thank you for your bug report, the log has that error
'ubiquity: df: /target/: can't find mount point'

Could you explain what you mean exactly by 'user not figuring out where to set boot.'? Did you use custom partitionning, could you describe exactly what you configured there?

[Tim Dillenberger (tim-dillenberger)]

hey Bug,
The Installer had issues and required me to go into the partition manager
to set boot partition, and it just crashed. had to reinstall 18.04 lts
version and will wait for next LTS version.
Tim Dillenberger

An Overall Nice Fellow.

On Fri, Jan 18, 2019 at 3:35 AM Sebastien Bacher <email address hidden> wrote:

> Thank you for your bug report, the log has that error
> 'ubiquity: df: /target/: can't find mount point'
>
> Could you explain what you mean exactly by 'user not figuring out where
> to set boot.'? Did you use custom partitionning, could you describe
> exactly what you configured there?
>
> ** Changed in: ubiquity (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: ubiquity (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1812257
>
> Title:
> Crash due to user not figuring out where to set boot.
>
> Status in ubiquity package in Ubuntu:
> Incomplete
>
> Bug description:
> Trying to do a clean install of Ubuntu and it came up with an error.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.10
> Package: ubiquity 18.10.12
> ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
> Uname: Linux 4.18.0-10-generic x86_64
> NonfreeKernelModules: wl
> ApportVersion: 2.20.10-0ubuntu13
> Architecture: amd64
> CasperVersion: 1.399
> CurrentDesktop: ubuntu:GNOME
> Date: Thu Jan 17 13:58:33 2019
> InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz
> file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash ---
> LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
> (20181017.3)
> ProcEnviron:
> LANGUAGE=en_US.UTF-8
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_US.UTF-8
> LC_NUMERIC=C.UTF-8
> SourcePackage: ubiquity
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1812257/+subscriptions
>

[Launchpad Janitor (janitor)]

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