| 2015-11-30 12:14:51 |
David Henningsson |
description |
Steps to reproduce:
1) Install daily build of Ubuntu 16.04.
2) Install another kernel, in my case this one: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-rc3-wily/linux-image-4.4.0-040400rc3-generic_4.4.0-040400rc3.201511300321_amd64.deb
3) Immediately remove the new kernel after adding it.
You will now receive the following scary message:
The link /vmlinuz is a damaged link
Removing symbolic link vmlinuz
you may need to re-run your boot loader[grub]
The link /initrd.img is a damaged link
Removing symbolic link initrd.img
you may need to re-run your boot loader[grub]
...although it seems relatively harmless. I think the key to reproducing it is that you have to go from 2 to 1 kernels (it won't reproduce if you have 3 kernels installed and remove 1).
Somewhat related to bug 924742, but I have not installed any home compiled kernels, only one from the kernel mainline ppa.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: grub2-common 2.02~beta2-32
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
ApportVersion: 2.19.2-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Nov 30 13:07:15 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-11-28 (2 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
SourcePackage: grub2
UpgradeStatus: No upgrade log present (probably fresh install) |
Steps to reproduce:
1) Install daily build of Ubuntu 16.04.
2) Install another kernel, in my case this one: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-rc3-wily/linux-image-4.4.0-040400rc3-generic_4.4.0-040400rc3.201511300321_amd64.deb
3) Immediately remove the new kernel after adding it.
You will now receive the following scary message:
The link /vmlinuz is a damaged link
Removing symbolic link vmlinuz
you may need to re-run your boot loader[grub]
The link /initrd.img is a damaged link
Removing symbolic link initrd.img
you may need to re-run your boot loader[grub]
...although it seems relatively harmless. I think the key to reproducing it is that you have to go from 2 to 1 kernels (it won't reproduce if you have 3 kernels installed and remove one of them).
Somewhat related to bug 924742, but I have not installed any home compiled kernels, only one from the kernel mainline ppa.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: grub2-common 2.02~beta2-32
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
ApportVersion: 2.19.2-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Nov 30 13:07:15 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-11-28 (2 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
SourcePackage: grub2
UpgradeStatus: No upgrade log present (probably fresh install) |
|
