Comment 13 for bug 1736080

Hi,
thanks for the explanation.
Actually, I has some troubles with the initial dual boot setup of the
machine (which is now single boot into Ubuntu), so this is probably my
fault!
As for th Nov. 28 timestamp, I added some lines to the /etc/fstab to mount
network disks, which I omitted from the prev report since they were
unrelated.
Thanks for your help and your thorough explanations.
Best,
Michele

2017-12-14 22:39 GMT+01:00 Steve Langasek <email address hidden>:

> On Thu, Dec 14, 2017 at 07:26:35AM -0000, Michele Polese wrote:
> > This fixed it. Thank you very much!
> > How's the /etc/fstab generated? Just to know if it's my fault for the
> wrong
> > configuration or something was messed up during the setup.
>
> The /etc/fstab is generated at boot time. The line that you had
> uncommented
> for /boot/efi was definitely not produced by the Ubuntu installer - even if
> there were a bug that produced such a line, the installation would have
> failed with that line present and the system would not have been bootable
> afterwards.
>
> Also, your bug report shows an installation date of 2016-11-21, and 'ls -l
> /etc/fstab' showed a timestamp on the file of November 28.
>
> So this must have been modified after the installation. There is no
> software in the standard Ubuntu install which would have made this change.
> It's possible there is some package present in the Ubuntu universe archive
> which would make such a change - if so, we would be interested to know what
> package that was, so that we could fix it. Or you might have installed
> third-party software which made this change, or followed some guide on the
> Internet telling you to make such changes to the file.
>
> If you do have any ideas how this happened, we would appreciate any
> information you could provide, since it's a fairly common report that
> /boot/efi is not correctly configured in /etc/fstab but we don't know why
> users are ending up in this situation.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1736080
>
> Title:
> package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
> failed to install/upgrade: subprocess installed post-installation
> script returned error exit status 1
>
> Status in shim-signed package in Ubuntu:
> Incomplete
>
> Bug description:
> See https://askubuntu.com/questions/948315/error-processing-package-
> shim-signed
>
> ProblemType: Package
> DistroRelease: Ubuntu 16.04
> Package: shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
> ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
> Uname: Linux 4.4.0-101-generic x86_64
> NonfreeKernelModules: vtsspp sep4_1 socperf2_0 pax
> .proc.sys.kernel.moksbstate_disabled: 0
> ApportVersion: 2.20.1-0ubuntu2.13
> Architecture: amd64
> BootEFIContents:
> fw
> fwupx64.efi
> Date: Sat Dec 2 06:52:44 2017
> DpkgHistoryLog:
> Start-Date: 2017-12-02 06:52:36
> Commandline: /usr/bin/unattended-upgrade
> Upgrade: thunderbird-gnome-support:amd64 (1:52.4.0+build1-0ubuntu0.16.04.2,
> 1:52.5.0+build1-0ubuntu0.16.04.1), thunderbird-locale-en-gb:amd64
> (1:52.4.0+build1-0ubuntu0.16.04.2, 1:52.5.0+build1-0ubuntu0.16.04.1),
> thunderbird-locale-en-us:amd64 (1:52.4.0+build1-0ubuntu0.16.04.2,
> 1:52.5.0+build1-0ubuntu0.16.04.1), firefox-locale-en:amd64
> (57.0+build4-0ubuntu0.16.04.6, 57.0.1+build2-0ubuntu0.16.04.1),
> firefox-locale-it:amd64 (57.0+build4-0ubuntu0.16.04.6,
> 57.0.1+build2-0ubuntu0.16.04.1), thunderbird:amd64
> (1:52.4.0+build1-0ubuntu0.16.04.2, 1:52.5.0+build1-0ubuntu0.16.04.1),
> firefox:amd64 (57.0+build4-0ubuntu0.16.04.6, 57.0.1+build2-0ubuntu0.16.04.1),
> thunderbird-locale-en:amd64 (1:52.4.0+build1-0ubuntu0.16.04.2,
> 1:52.5.0+build1-0ubuntu0.16.04.1), thunderbird-locale-it:amd64
> (1:52.4.0+build1-0ubuntu0.16.04.2, 1:52.5.0+build1-0ubuntu0.16.04.1)
> EFITables:
> nov 27 10:15:11 pcsensori34 kernel: efi: EFI v2.40 by American
> Megatrends
> nov 27 10:15:11 pcsensori34 kernel: efi: ACPI=0x87417000 ACPI
> 2.0=0x87417000 SMBIOS=0xf05e0 ESRT=0x87dfe598 MPS=0xfcba0
> nov 27 10:15:11 pcsensori34 kernel: esrt: Reserving ESRT space from
> 0x0000000087dfe598 to 0x0000000087dfe5d0.
> ErrorMessage: subprocess installed post-installation script returned
> error exit status 1
> InstallationDate: Installed on 2016-11-21 (377 days ago)
> InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
> (20160719)
> RelatedPackageVersions:
> dpkg 1.18.4ubuntu1.2
> apt 1.2.24
> SecureBoot: 6 0 0 0 0
> SourcePackage: shim-signed
> Title: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
> failed to install/upgrade: subprocess installed post-installation script
> returned error exit status 1
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/shim-signed/+
> bug/1736080/+subscriptions
>

--
Michele Polese

Ph.D. Student
Dept. of Information Engineering (DEI) - SIGNET Research Group
University of Padova
Via Gradenigo 6/B, 35131 Padova (Italy)

email: <email address hidden>
web: polese.io - mmwave.dei.unipd.it