Possible bug in Grub in latest Install Updates

[Valtam]

Looks to me like there could be a bug in the latest version of Grub.

IMPORTANT: If you are planning to do updates, DON'T. Not until there is more word on this.

Those that have, may see a message similar to the following in their log:

Code:

Setting up grub-common (2.02~beta2-36ubuntu3.10) ...
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Setting up grub2-common (2.02~beta2-36ubuntu3.10) ...
Setting up grub-pc-bin (2.02~beta2-36ubuntu3.10) ...
Setting up grub-pc (2.02~beta2-36ubuntu3.10) ...
/var/lib/dpkg/info/grub-pc.postinst: line 703: syntax error near unexpected token `fi'
dpkg: error processing package grub-pc (--configure):
subprocess installed post-installation script returned error exit status 2

Ubuntu is bound to catch this so please wait for further instructions and don't not update yet if you haven't already.

Stay tuned

[BritBloke]

Got the same error message : --

Code:

=====================
E: grub-pc: subprocess installed post-installation script returned error exit status 2

Selecting previously unselected package libsignon-glib1:i386.
(Reading database ... 216243 files and directories currently installed.)
Preparing to unpack .../libsignon-glib1_1.13+16.04.20151209.1-0ubuntu1_i386.deb ...
Unpacking libsignon-glib1:i386 (1.13+16.04.20151209.1-0ubuntu1) ...
Selecting previously unselected package libaccounts-glib0:i386.
Preparing to unpack .../libaccounts-glib0_1.21+16.04.20160222-0ubuntu1_i386.deb ...
Unpacking libaccounts-glib0:i386 (1.21+16.04.20160222-0ubuntu1) ...
Selecting previously unselected package libexiv2-14:i386.
Preparing to unpack .../libexiv2-14_0.25-2.1ubuntu16.04.1_i386.deb ...
Unpacking libexiv2-14:i386 (0.25-2.1ubuntu16.04.1) ...
Selecting previously unselected package libgexiv2-2:i386.
Preparing to unpack .../libgexiv2-2_0.10.3-2_i386.deb ...
Unpacking libgexiv2-2:i386 (0.10.3-2) ...
Selecting previously unselected package shotwell-common.
Preparing to unpack .../shotwell-common_0.22.0+git20160108.r1.f2fb1f7-0ubuntu1_all.deb ...
Unpacking shotwell-common (0.22.0+git20160108.r1.f2fb1f7-0ubuntu1) ...
Selecting previously unselected package shotwell.
Preparing to unpack .../shotwell_0.22.0+git20160108.r1.f2fb1f7-0ubuntu1_i386.deb ...
Unpacking shotwell (0.22.0+git20160108.r1.f2fb1f7-0ubuntu1) ...
Processing triggers for libc-bin (2.23-0ubuntu7) ...
Processing triggers for gconf2 (3.2.6-3ubuntu6) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ...
Processing triggers for gnome-menus (3.13.3-6ubuntu3.1) ...
Processing triggers for mime-support (3.59ubuntu1) ...
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
Processing triggers for libglib2.0-0:i386 (2.48.2-0ubuntu1) ...
Processing triggers for menu (2.1.47ubuntu1) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up grub-pc (2.02~beta2-36ubuntu3.10) ...
/var/lib/dpkg/info/grub-pc.postinst: line 703: syntax error near unexpected token `fi'
dpkg: error processing package grub-pc (--configure):
subprocess installed post-installation script returned error exit status 2
Setting up libsignon-glib1:i386 (1.13+16.04.20151209.1-0ubuntu1) ...
Setting up libaccounts-glib0:i386 (1.21+16.04.20160222-0ubuntu1) ...
Setting up libexiv2-14:i386 (0.25-2.1ubuntu16.04.1) ...
Setting up libgexiv2-2:i386 (0.10.3-2) ...
Setting up shotwell-common (0.22.0+git20160108.r1.f2fb1f7-0ubuntu1) ...
Setting up shotwell (0.22.0+git20160108.r1.f2fb1f7-0ubuntu1) ...
Processing triggers for libc-bin (2.23-0ubuntu7) ...
Processing triggers for menu (2.1.47ubuntu1) ...
Errors were encountered while processing:
grub-pc
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up grub-pc (2.02~beta2-36ubuntu3.10) ...
/var/lib/dpkg/info/grub-pc.postinst: line 703: syntax error near unexpected token `fi'
dpkg: error processing package grub-pc (--configure):
subprocess installed post-installation script returned error exit status 2
Errors were encountered while processing:
grub-pc

[Valtam]

Follow the thread here if you're interested - https://bugs.launchpad.net/ubuntu/+sourc...ug/1692215

[Valtam]

Those brave enough to fix this themselves can do the following to fix:

Code:

sudo leafpad /var/lib/dpkg/info/grub-pc.postinst

change line 699 from:

Code:

        if dpkg --compare-versions "$2" lt-nl 2.02~beta2-36ubuntu3.10 then

to:

Code:

        if dpkg --compare-versions "$2" lt-nl 2.02~beta2-36ubuntu3.10; then

notice the added semicolon after ubuntu3.10

Then run:

Code:

sudo dpkg --configure grub-pc

Please confirm this fix works.

[Ottawagrant]

Hi Jerry: When you try to run the command in terminal you get an error that it can't open it because it's a directory. But if you go to the file itself & right-click 'open as administrator', it'll open. I changed the line (#699), saved & then ran the sudo grub update in terminal. BUT! You then get a choice of:
-install the package maintainers version
-keep the local version installed
-show the differences between the versions
-show a side-by-side difference between the versions
-show a 3-way difference between available versions
-do a 3-way merge between available versions (experimental)
-start a new shell to examine the situation

Which do I select? I'm just going to keep the terminal window open until you, or someone else posts a reply & then I'll let you know what happened.

[Valtam]

So you've encountered the exact same updates error as above have you?

Sent from my Mobile phone using Tapatalk

[Ottawagrant]

When I booted up my computer first thing this morning I updated the computer. Error. So I came here to see if anyone else had it. they did. After I modified grub-pc.postinst I was trapped into making a choice between 6 choices in terminal. I also found that while terminal was open I couldn't come to the forum & post a reply. I remember having a similar situation to this back in Linux Lite series 1. The choice I made at the time was "install the package maintainers version". Also doing a side-by-side comparison of the first 2 choices the first choice (package maintainer) was a newer version than the second choice. 50 - 50 choice I figured, so I went with choice number 1 - "install the package maintainers version". Entered it, it installed it, no error. Rebooted the computer & all seems well. Running update it tells me that my system is up to date. But as I mentioned you do have to actually go to /var/lib/dpkg/info & right-click grub-pc.postinst to change it. It won't open via terminal.

[elelme]

I thought, being a novice, that I broke the distro, finally...
THANKS for the alert. Had just about decided that LL was just
another disappointment..Whew! So glad to know it was not Linux Lite and not me, either. 

[jonno O]

updated before i saw your message :-[ came out with error as you mentioned.

[bluzeo]

So if I updated the source to install something this be an bad idea?? For now!?


God not dead! He roaring like an Lion.