package linux-image-*-generic failed to install/upgrade with error "[: 25: ==: unexpected operator" when gfxboot-grub is installed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Processing triggers for man-db ...
Setting up linux-image-
Running depmod.
update-initramfs: Generating /boot/initrd.
Not updating initrd symbolic links since we are being updated/reinstalled
(2.6.26-5.14 was configured last, according to dpkg)
Not updating image symbolic links since we are being updated/reinstalled
(2.6.26-5.14 was configured last, according to dpkg)
Running postinst hook script /sbin/update-grub.
[: 25: ==: unexpected operator
exec: 25: -a: not found
User postinst hook script [/sbin/update-grub] exited with value 2
dpkg: error processing linux-image-
subprocess post-installation script returned error exit status 2
dpkg: dependency problems prevent configuration of linux-restricte
linux-
Package linux-image-
dpkg: error processing linux-restricte
dependency problems - leaving unconfigured
Setting up exim4-config (4.69-5ubuntu1) ...
No apport report written because the error message indicates its a followup error from a previous failure.
Setting up exim4-base (4.69-5ubuntu1) ...
Setting up exim4-daemon-light (4.69-5ubuntu1) ...
* Starting MTA [ OK ]
Setting up exim4 (4.69-5ubuntu1) ...
Setting up bsd-mailx (8.1.2-
Setting up mailx (1:20071201-3) ...
Setting up smartmontools (5.38-1ubuntu2) ...
Errors were encountered while processing:
linux-
linux-
E: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Package
Architecture: amd64
DistroRelease: Ubuntu 8.10
ErrorMessage: subprocess post-installation script returned error exit status 2
NonfreeKernelMo
Package: linux-image-
ProcCmdLine: User Name=UUID=
ProcVersionSign
SourcePackage: linux
Title: package linux-image-
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 258631, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.