Comment 2 for bug 2064784

Revision history for this message
Thomas Aglassinger (roskakori) wrote (last edit ):

It seems the issue is related to the pcp package, which fails to install even when attempted after the upgrade.

```
$ sudo apt install -y cockpit
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
cockpit is already the newest version (314-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up pcp (6.2.0-1.1build4) ...
Job for pmlogger.service failed because the service did not take the steps required by its unit configuration.
See "systemctl status pmlogger.service" and "journalctl -xeu pmlogger.service" for details.
dpkg: error processing package pcp (--configure):
 installed pcp package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of cockpit-pcp:
 cockpit-pcp depends on pcp; however:
  Package pcp is not configured yet.

dpkg: error processing package cockpit-pcp (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
                                                                                                          Errors were encountered while processing:
 pcp
 cockpit-pcp
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
```