udev postinst script fails in chroot environment

Bug #381104 reported by stuart
28
This bug affects 4 people
Affects Status Importance Assigned to Milestone
udev (Ubuntu)
Triaged
Low
Unassigned

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.

Tags: jaunty udev
stuart (stuart-hayton)
tags: added: jaunty udev
Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

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
Revision history for this message
Damian (damianator) wrote :

Same problem here. Very annoying :(

Revision history for this message
Damian (damianator) wrote :

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

Changed in udev (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
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:
 udev
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.