udev postinst script fails in chroot environment

Bug #381104 reported by stuart on 2009-05-27
This bug affects 4 people
Affects Status Importance Assigned to Milestone
udev (Ubuntu)

Bug Description

Binary package hint: udev

The udev.postinst script fails to restart udev (cannot bind to socket) when running in a chroot environment such as that used by the ubuntu customisation kit (uck), because of this the script fails to complete configuration.

I am attempting to build an updated live cd for jaunty 9.04 the recent udev update to version 141-1.1 causes the build to fail or if errors
ignored the image to fail to boot. I note that other packages such as acpid do detect and work round the chroot environment.

stuart (stuart-hayton) on 2009-05-27
tags: added: jaunty udev

A chroot environment should normally have start-stop-daemon masked out to prevent services from being started, so this is a corner case

Changed in udev (Ubuntu):
importance: Undecided → Low
status: New → Confirmed
Damian (damianator) wrote :

Same problem here. Very annoying :(

Damian (damianator) wrote :

But he problem here is with acpid, not with udev on my machine

Changed in udev (Ubuntu):
status: Confirmed → Triaged
Andy Ruddock (andy-ruddock) wrote :

This bug is still present in 12.04LTS, updates fail :

Setting up udev (175-0ubuntu9.1) ...
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
invoke-rc.d: initscript udev, action "restart" failed.
dpkg: error processing udev (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers