I was indeed running this upgrade from a chroot.
Ok. Installing upstart-using packages in a chroot requires additional
configuration, such as creating a /usr/sbin/policy-rc.d script that
returns a 101 status code or using dpkg-divert on invoke-rc.d or initctl
to replace it with true.
If you
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: upstart (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/771834
Title:
** Changed in: upstart (Ubuntu)
Importance: Undecided = Medium
** Changed in: upstart (Ubuntu)
Importance: Medium = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/771834
Title:
package
James, we've seen several of these connection refused problems with
upstart (seems to be reported against cups more than against any other
package). Can you think of any reason this would be happening, aside
from running in a chroot?
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) =
I was indeed running this upgrade from a chroot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/771834
Title:
package cups 1.4.6-5ubuntu1 failed to install/upgrade: le sous-
processus script
The log says:
Paramétrage de cups (1.4.6-5) ...
Installation de la nouvelle version du fichier de configuration
/etc/apparmor.d/usr.sbin.cupsd ...
start: Connexion à Upstart impossible: Failed to connect to socket
/com/ubuntu/upstart: Connexion refusée
invoke-rc.d: initscript cups, action start
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/771834
Title:
package cups 1.4.6-5ubuntu1 failed to install/upgrade: le sous-
processus script post-installation installé a retourné une erreur de
