Description of problem: udevd failed to execute /usr/bin/setfacl' " -m user:lp: rw /dev/parport0" :no suchfile or directory Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. clean install. Pick Custom during package selection phase, select all package groups except LSB and LXDE groups. After boot, install task-printing-hp, cups-common, cups packages if not already installed. 2. apply all updates and reboot 2. at the grub prompt hit e 3. e again 4. enter a space 3 at end of line 5. remove verbose=whatever 6. enter return 6 enter b return Watch screen for the above message. Solution was to install acl-2.2.51-2.mga2.src.rpm
do we need somewhere a require or something ?
CC: (none) => bruno, doktor5000, thierry.vignaudAssignee: bugsquad => dmorganecSummary: 2_alpha1: udevd failed to execute /usr/bin/setfacl => udevd failed to execute /usr/bin/setfaclSource RPM: (none) => udev ?
Looks like some bad path in some udev rule. What does report the following command? fgrep sbin/setfacl /lib/udev/rules.d /etc/udev/ -r
Keywords: (none) => NEEDINFO
(In reply to comment #2) > Looks like some bad path in some udev rule. Hmm, and yet urpmi acl made the problem go away. > What does report the following command? > fgrep sbin/setfacl /lib/udev/rules.d /etc/udev/ -r Nothing, see. # fgrep sbin/setfacl /lib/udev/rules.d /etc/udev/ -r # But, I have made that mistake a few times myself, maybe this will help :) # fgrep bin/setfacl /lib/udev/rules.d /etc/udev/ -r /lib/udev/rules.d/85-usbmuxd.rules:ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="05ac", ATTR{idProduct}=="12[9a][0-9a-f]", ENV{USBMUX_SUPPORTED}="1", ATTR{bConfigurationValue}!="$attr{bNumConfigurations}", ATTR{bConfigurationValue}="$attr{bNumConfigurations}", RUN+="/usr/bin/setfacl -m user:usbmux:rw %N", RUN+="/usr/sbin/usbmuxd -u -U usbmux" /lib/udev/rules.d/69-cd-sensors.rules:ENV{COLORD_SENSOR}=="*?", RUN+="/bin/setfacl -m u:root:rw $env{DEVNAME}" ------------ That is weird, the error seems to be from 69-cd-sensors.rules and yet it went away after urpmi acl. What is odd about that is, I would still have expected the error because: # type -a setfacl setfacl is /usr/bin/setfacl # ll /usr/bin/setfacl -rwxr-xr-x 1 root root 36136 Sep 12 22:12 /usr/bin/setfacl # locate bin/setfacl /usr/bin/setfacl While we are on this bug, Should I clear the NEEDINFO keyword?
Keywords: NEEDINFO => (none)
Do you have a separated /usr partition?
(In reply to comment #4) > Do you have a separated /usr partition? I hope one is not needed. :) No, everything from dvd in in /
Maybe Colin will have an idea?
CC: (none) => mageia
This generally shouldn't be an issue. I just think udev is missing a require on acl. On my system here: [colin@jimmy dracut (mga)]$ rpm -q --whatrequires acl hal-0.5.14-6.mga1 Which is a blast from the past! :) The separate /usr partition is supported, but you'll need to use dracut as initrd generator (and work out what the problem is with it for you was reported in bug #3588) such that it is mounted in the initrd before we start init.
Keywords: NEEDINFO => (none)Status: NEW => ASSIGNEDSummary: udevd failed to execute /usr/bin/setfacl => udev lacks a require one acl (udevd failed to execute /usr/bin/setfacl)Source RPM: udev ? => udev
*** Bug 3646 has been marked as a duplicate of this bug. ***
CC: (none) => gdugan
i added the requires on acl today. I faced this issue yesterday when installing a printer, it didn't worked because i was lacking this requires.
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED
Can you actually push udev please :-) ?
Just for reference (as I have this bug open in a tab) a new udev package was pushed.