dpkg error libflac8_1.3.2-1ubuntu0.1_i386.deb

[Hector Poirot]

Hi the Recent security patch for libflac8 is not installing :

Preparing to unpack .../libflac8_1.3.2-1ubuntu0.1_i386.deb ...
dpkg: error processing archive /var/cache/apt/archives/libflac8_1.3.2-1ubuntu0.1_i386.deb (--unpack):
 triggers ci file contains unknown directive 'libcrypto'
Errors were encountered while processing:
 /var/cache/apt/archives/libflac8_1.3.2-1ubuntu0.1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

I am running :

Distributor ID: Ubuntu
Description: Ubuntu 18.04.6 LTS
Release: 18.04
Codename: bionic

4.15.0-191-generic

libflac8:
  Installed: 1.3.2-1
  Candidate: 1.3.2-1ubuntu0.1
  Version table:
     1.3.2-1ubuntu0.1 500
        500 http://ca.archive.ubuntu.com/ubuntu bionic-security/main i386 Packages
        500 http://ca.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages
 *** 1.3.2-1 500
        500 http://ca.archive.ubuntu.com/ubuntu bionic/main i386 Packages
        100 /var/lib/dpkg/status

Thank you

[Camila Camargo de Matos (ccdm94)]

Hello Hector,

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug, as I was unable to reproduce the issue.

We will proceed with investigations, but meanwhile, since there have been reports of similar bugs in the past (such as LP#1784065) , maybe one of the following could be attempted in order to fix your issue:

- Run "dpkg --configure -a" and "apt-get -f install" in your system and then try the upgrade once again.

- Execute the steps in this Wiki page https://wiki.ubuntu.com/DebuggingInstallationIssues#triggers_ci_file_contains_unknown_directive_syntax and then run the upgrade command once again.

Please let us know if any of the above solutions help in any way, and please feel free to report any other bugs you may find.

[Hector Poirot (hectorpoirot29)]

Hi, thanks for the feedback.

The Workaround in Bug 500042 described in the Wiki (clearing the Package.triggers & reinstall) solved the issue. The install went through.

Note: the command to purge the ureadahead package was not necessary in the workaround as it is not installed on my system (not sure why).

[Camila Camargo de Matos (ccdm94)]

Thank you for your feedback!

Since the issue is resolved, and it was not a security related bug, I will close this and mark it as Invalid.

Please feel free to report any other bugs you may find!

[Seth Arnold (seth-arnold)]

Hector, ureadahead was more useful in the era of slow hard drives. It loads files that are needed during system boot, with the intention of having the files in memory before they are needed. It's significantly less useful with SSDs, and even with spinning hard drives it's not always a win. (It assumes there's no memory pressure during boot that would cause files to be discarded; on most systems that's probably a fine assumption, but it isn't always true.)

There's no cause for concern for it to be missing.

Thanks