package mysql-server-5.7 5.7.24-0ubuntu0.18.04.1 failed to install/upgrade: new mysql-server-5.7 package pre-removal script subprocess returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mysql-5.7 (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
$ service apparmor reload
helped me
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: mysql-server-5.7 5.7.24-
ProcVersionSign
Uname: Linux 4.15.0-43-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
AptOrdering:
mysql-
mysql-
NULL: ConfigurePending
Architecture: amd64
Date: Thu Jan 24 13:40:25 2019
ErrorMessage: new mysql-server-5.7 package pre-removal script subprocess returned error exit status 1
InstallationDate: Installed on 2018-11-22 (63 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Logs.var.
MySQLConf.
[mysqld]
sql_mode=
MySQLConf.
MySQLConf.
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
MySQLConf.
[mysqld_safe]
syslog
MySQLVarLibDirL
ProcCmdline: BOOT_IMAGE=
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
RelatedPackageV
dpkg 1.19.0.5ubuntu2.1
apt 1.6.6ubuntu0.1
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.24-
UpgradeStatus: No upgrade log present (probably fresh install)
Thank you for taking the time to report this bug and helping to make Ubuntu better.
Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http:// www.ubuntu. com/support/ community
Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http:// www.chiark. greenend. org.uk/ ~sgtatham/ bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.