| 2020-01-22 14:24:13 |
Jean-Baptiste Lallement |
bug |
|
|
added bug |
| 2020-01-22 14:25:24 |
Jean-Baptiste Lallement |
summary |
System fail to reboot after installation |
[18.04.4] System fails to reboot after installation |
|
| 2020-01-22 14:25:28 |
Jean-Baptiste Lallement |
ubiquity (Ubuntu): importance |
Undecided |
Critical |
|
| 2020-01-22 14:25:43 |
Jean-Baptiste Lallement |
tags |
amd64 apport-bug bionic ubiquity-18.04.14.13 |
amd64 apport-bug bionic rls-bb-incoming ubiquity-18.04.14.13 |
|
| 2020-01-22 14:33:59 |
Jean-Baptiste Lallement |
affects |
ubiquity (Ubuntu) |
linux (Ubuntu) |
|
| 2020-01-22 14:34:11 |
Jean-Baptiste Lallement |
nominated for series |
|
Ubuntu Bionic |
|
| 2020-01-22 14:34:11 |
Jean-Baptiste Lallement |
bug task added |
|
linux (Ubuntu Bionic) |
|
| 2020-01-22 14:34:18 |
Jean-Baptiste Lallement |
linux (Ubuntu Bionic): importance |
Undecided |
Critical |
|
| 2020-01-22 14:34:25 |
Jean-Baptiste Lallement |
linux (Ubuntu): status |
New |
Fix Released |
|
| 2020-01-22 14:34:31 |
Jean-Baptiste Lallement |
linux (Ubuntu Bionic): milestone |
|
ubuntu-18.04.4 |
|
| 2020-01-22 15:08:47 |
Jean-Baptiste Lallement |
attachment added |
|
bionic-desktop-amd64.manifest.20191210-12.diff https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860559/+attachment/5322192/+files/bionic-desktop-amd64.manifest.20191210-12.diff |
|
| 2020-01-23 05:42:07 |
Jean-Baptiste Lallement |
bug task added |
|
casper (Ubuntu) |
|
| 2020-01-23 05:43:42 |
Jean-Baptiste Lallement |
description |
bionic desktop 20190122
Since bionic 20191211 the system doesn't reboot after installation.
After pressing enter to reboot, the system hangs. There is this message printed in a loop on the console:
[sdb] tag#0 access beyond end of device
20191211 includes a new kernel and a new gcc
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
Uname: Linux 5.3.0-28-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 22 15:17:58 2020
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity
InstallationDate: Installed on 2020-01-22 (0 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install) |
bionic desktop 20190122
Since bionic 20191211 the system doesn't reboot after installation.
After pressing enter to reboot, the system hangs. There is this message printed in a loop on the console:
[sdb] tag#0 access beyond end of device
20191211 includes a new kernel and a new gcc
This is similar to bug 1840122 in 19.10 which started with the upgrade from kernel 5.0 to kernel 5.2. Although the error message displayed on the console was different.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
Uname: Linux 5.3.0-28-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 22 15:17:58 2020
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity
InstallationDate: Installed on 2020-01-22 (0 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2020-01-23 06:06:43 |
Jean-Baptiste Lallement |
description |
bionic desktop 20190122
Since bionic 20191211 the system doesn't reboot after installation.
After pressing enter to reboot, the system hangs. There is this message printed in a loop on the console:
[sdb] tag#0 access beyond end of device
20191211 includes a new kernel and a new gcc
This is similar to bug 1840122 in 19.10 which started with the upgrade from kernel 5.0 to kernel 5.2. Although the error message displayed on the console was different.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
Uname: Linux 5.3.0-28-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 22 15:17:58 2020
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity
InstallationDate: Installed on 2020-01-22 (0 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install) |
bionic desktop 20190122
Since bionic 20191211 the system doesn't reboot after installation.
After pressing enter to reboot, the system hangs. There is this message printed in a loop on the console:
[sdb] tag#0 access beyond end of device
20191211 includes a new kernel and a new gcc
This is similar to bug 1840122 in 19.10 which started with the upgrade from kernel 5.0 to kernel 5.2. Although the error message displayed on the console was different.
Installing finalrd helps to work around the issue. However in Bionic, finalrd is in universe.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
Uname: Linux 5.3.0-28-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 22 15:17:58 2020
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity
InstallationDate: Installed on 2020-01-22 (0 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2020-01-23 06:07:00 |
Jean-Baptiste Lallement |
casper (Ubuntu): importance |
Undecided |
Critical |
|
| 2020-01-23 06:07:02 |
Jean-Baptiste Lallement |
casper (Ubuntu Bionic): importance |
Undecided |
Critical |
|
| 2020-01-23 06:07:07 |
Jean-Baptiste Lallement |
casper (Ubuntu): status |
New |
Fix Released |
|
| 2020-01-23 06:07:11 |
Jean-Baptiste Lallement |
casper (Ubuntu Bionic): status |
New |
Confirmed |
|
| 2020-01-23 06:07:14 |
Jean-Baptiste Lallement |
linux (Ubuntu Bionic): status |
New |
Confirmed |
|
| 2020-01-23 06:22:43 |
Jean-Baptiste Lallement |
description |
bionic desktop 20190122
Since bionic 20191211 the system doesn't reboot after installation.
After pressing enter to reboot, the system hangs. There is this message printed in a loop on the console:
[sdb] tag#0 access beyond end of device
20191211 includes a new kernel and a new gcc
This is similar to bug 1840122 in 19.10 which started with the upgrade from kernel 5.0 to kernel 5.2. Although the error message displayed on the console was different.
Installing finalrd helps to work around the issue. However in Bionic, finalrd is in universe.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
Uname: Linux 5.3.0-28-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 22 15:17:58 2020
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity
InstallationDate: Installed on 2020-01-22 (0 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install) |
bionic desktop 20190122
Since bionic 20191211 the system doesn't reboot after installation.
After pressing enter to reboot, the system hangs. There is this message printed in a loop on the console:
[sdb] tag#0 access beyond end of device
20191211 includes a new kernel and a new gcc
This is similar to bug 1840122 in 19.10 which started with the upgrade from kernel 5.0 to kernel 5.2. Although the error message displayed on the console was different on baremetal, it is identical in a VM.
Installing finalrd helps to work around the issue. However in Bionic, finalrd is in universe.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
Uname: Linux 5.3.0-28-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 22 15:17:58 2020
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity
InstallationDate: Installed on 2020-01-22 (0 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2020-01-23 11:39:43 |
Jean-Baptiste Lallement |
description |
bionic desktop 20190122
Since bionic 20191211 the system doesn't reboot after installation.
After pressing enter to reboot, the system hangs. There is this message printed in a loop on the console:
[sdb] tag#0 access beyond end of device
20191211 includes a new kernel and a new gcc
This is similar to bug 1840122 in 19.10 which started with the upgrade from kernel 5.0 to kernel 5.2. Although the error message displayed on the console was different on baremetal, it is identical in a VM.
Installing finalrd helps to work around the issue. However in Bionic, finalrd is in universe.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
Uname: Linux 5.3.0-28-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 22 15:17:58 2020
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity
InstallationDate: Installed on 2020-01-22 (0 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install) |
bionic desktop 20190122
Since bionic 20191211 the system doesn't reboot after installation.
After pressing enter to reboot, the system hangs. There is this message printed in a loop on the console:
[sdb] tag#0 access beyond end of device
(in this context sdb is the USB stick)
20191211 includes a new kernel and a new gcc
This is similar to bug 1840122 in 19.10 which started with the upgrade from kernel 5.0 to kernel 5.2. Although the error message displayed on the console was different on baremetal, it is identical in a VM.
Installing finalrd helps to work around the issue. However in Bionic, finalrd is in universe.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
Uname: Linux 5.3.0-28-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 22 15:17:58 2020
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity
InstallationDate: Installed on 2020-01-22 (0 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20200122)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2020-01-23 16:19:43 |
Steve Langasek |
tags |
amd64 apport-bug bionic rls-bb-incoming ubiquity-18.04.14.13 |
amd64 apport-bug bionic ubiquity-18.04.14.13 |
|
| 2020-01-27 13:04:35 |
Jean-Baptiste Lallement |
casper (Ubuntu Bionic): assignee |
|
Dimitri John Ledkov (xnox) |
|
| 2020-01-28 17:38:34 |
Brian Murray |
summary |
[18.04.4] System fails to reboot after installation |
[18.04.4] Live system fails to reboot after installation |
|
| 2020-01-30 09:08:50 |
Jean-Baptiste Lallement |
marked as duplicate |
|
1840122 |
|
