A candidate fix is to pass the vmlinuz-3.11.0-12-generic (or whatever) filename into the test_relative() function for the 'Test File' parameter, when it's called for the non-existent initrd.img-* file, since the vmlinuz is guaranteed to be present.
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1248053 Title: initrd.img symlink is absolute Status in “linux” package in Ubuntu: Incomplete Bug description: When the linux-image package is installed, it creates symlinks from the root directory: # ls -l / initrd.img -> /boot/initrd.img-3.11.0-13-generic vmlinuz -> boot/vmlinuz-3.11.0-13-generic This is needed for booting the currently installed kernel (managed from within the distro for security updates etc) in certain environments, such as virtual hosts or root-NFS booting. The bug is that the initrd.img symlink is absolute, since the test_relative() perl function checks for the presence of the initrd.img file, which is created after the postinst scripts runs, so it assumes a absolute symlink is needed. This isn't the case for the vmlinuz file, since it is shipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248053/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
