Unfortunately, the error that started the installation problems occurred
earlier than the start of your log files. If you happen to still have
the older log files you could do some archaeology in them to see when
the error first occurred, and what started it.
One of the typical ways to get into this service is when some unrelated
service is upgraded as part of your routine system update. Typically,
the service then needs to be restarted to pick up its fixes, but there
are situations where it fails to start up, such as if there is an issue
with the formerly working configuration. The service remains installed
in this case, but left in an unconfigured (aka 'broken') state. Now,
any further updates of any packages related to that service will have to
be restarted, but the faulty config will not resolve itself. Neither
rebooting nor reinstalling things will resolve it.
In other words, the errors may be mentioning php7.2, but that's possibly
just because some service (mysql? apache?) is in an incomplete state.
Depending on your particular case there are two solutions:
- either remove the offending package if you don't want to continue using it.
- Or if you do want to keep it please fix the configuration so that re-starting
the service will work.
Either way, please let us know how you're doing, and if you got it
resolved in the meantime it would likely help other bug reporters if you
explained what steps you took.
** Changed in: php7.2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853760
Title:
php 7.2 has dependency problems and they are not letting to update
apache2 and php7.2 * modules
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php7.2/+bug/1853760/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
