@ustcweizhou - very interesting approach to fix this. The type is usually "notify". There is a drawback that you change implies follow up units might start as soon as the daemonizing of libvirt is complete which might be too early. The notification would usually signal that it is completely ready and follow on units can be started. But lets ignore that for now and consider how it could affect the application of the netlink apparmor rule.
Related to comment #10 and comment #11 ff. If there is an old manual config that will set -d in /etc/default/libvirt-bin /etc/default/libvirt-bin then your change of the service file would make it match the behavior. There should be a non-default connection as the service file /lib/systemd/system/libvirt-bin.service starts libvirt "directly" and not via /etc/default/libvirt-bin - so the -d in that old files (if you are on SystemV/Upstart) should not matter. For all still affected by this could you check: 1. if your libvirt is run with "-d" option (which it should not be anymore) 2. if #1 was yes, then where this config comes from 3. once you debugged #2, decide if you either want to become closer to the supported content by changing back OR try a fix like suggested in comment #38 (which is not generally applicable) For everyone passing step #2 I'd be interested how in your personal system setup the "-d" gets applied, as with the systemd setup it should not be used anymore. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1594902 Title: Failed to upgrade to libvirt-bin 1.3.1-1ubuntu10.1 on Ubuntu 16.04 64-bit Status in apparmor package in Ubuntu: Confirmed Status in libvirt package in Ubuntu: Confirmed Bug description: Output from 'apt-get upgrade': Setting up libvirt-bin (1.3.1-1ubuntu10.1) ... initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'screen-cleanup' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `screen-cleanup' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `screen-cleanup' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'binfmt-support' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `binfmt-support' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `binfmt-support' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'screen-cleanup' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `screen-cleanup' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `screen-cleanup' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'binfmt-support' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `binfmt-support' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `binfmt-support' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'screen-cleanup' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `screen-cleanup' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `screen-cleanup' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'binfmt-support' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `binfmt-support' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `binfmt-support' Job for libvirt-bin.service failed because the control process exited with error code. See "systemctl status libvirt-bin.service" and "journalctl -xe" for details. invoke-rc.d: initscript libvirt-bin, action "restart" failed. dpkg: error processing package libvirt-bin (--configure): subprocess installed post-installation script returned error exit status 1 E: Sub-process /usr/bin/dpkg returned an error code (1) Output from 'systemctl status libvirt-bin.service': ● libvirt-bin.service - Virtualization daemon Loaded: loaded (/lib/systemd/system/libvirt-bin.service; enabled; vendor preset: enabled) Active: inactive (dead) (Result: exit-code) since Tue 2016-06-21 17:55:16 BST; 4min 52s ago Docs: man:libvirtd(8) http://libvirt.org Process: 2984 ExecStart=/usr/sbin/libvirtd $libvirtd_opts (code=exited, status=6) Main PID: 2984 (code=exited, status=6) Jun 21 17:55:15 lydia systemd[1]: Failed to start Virtualization daemon. Jun 21 17:55:15 lydia systemd[1]: libvirt-bin.service: Unit entered failed state. Jun 21 17:55:15 lydia systemd[1]: libvirt-bin.service: Failed with result 'exit-code'. Jun 21 17:55:16 lydia systemd[1]: libvirt-bin.service: Service hold-off time over, scheduling restart. Jun 21 17:55:16 lydia systemd[1]: Stopped Virtualization daemon. Jun 21 17:55:16 lydia systemd[1]: libvirt-bin.service: Start request repeated too quickly. Jun 21 17:55:16 lydia systemd[1]: Failed to start Virtualization daemon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1594902/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
