Jose Yamut, Jr

Fond of +rw but seldom has time 4 both. 😎😋🤖

How To linux Ubuntu

Bug #1592669

First encountered this bug in 2017. It is almost 2 years now and they still have not gotten to fix it. Well, somebody actually said they already have a fix for it but have not committed it yet since according to them, and I quote:

“We’ve had a fix for this in review for a while, but haven’t been able to push it to completion (it’s a fairly big change to how the packaging works).”

You can find all the information about this bug at this page – https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1592669

Anyway, this bug is related to how the MySQL Server is packaged on Ubuntu 16.04 Xenial Xerus. It is not actually a bug on the database application itself. Rather the bug is on how the app is packaged and fails during the process of updating the MySQL Server post install.

Once this happens, it renders your software update after with an error message. You will get something like parts of the installation process failed and that you should re-run the update/upgrade process. From what I have noticed, all other upgrades are succesful except for MySQL. Since the MySQL update did not complete properly, you won’t be able to use it anymore. It will fail to start.

A simple workaround was provided though. Again you can see the full exchange at the link above. For the impatient just follow these steps:

  • Edit /var/lib/dpkg/info/mysql-server-5.7.postinst and put a simple “exit 0” at the top after #!/bin/bash
  • Run apt-get -f install
  • (Although not mentioned explicitly) Revert on your modification in step #1


I guess thanks and no thanks?

First, thanks for providing an easy-to-do DIY fix.

And, second, no thanks because I am pretty sure bug #1592669 will NOT get fixed. They are going to wait until Ubuntu 16.04 gets the ax in April 2021. That won’t be too soon, but it is getting close enough. To think that Xenial Xerus is a LTS release. Ubuntu, I am disappointed at you.

Similar Posts:

First encountered this bug in 2017. It is almost 2 years now and they still have not gotten to fix it. Well, somebody actually said they already have a fix for it but have not committed it yet since according to them, and I quote: “We’ve had a fix for this in review for a…

Tags: