| Summary: | udev lacks a require one acl (udevd failed to execute /usr/bin/setfacl) | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Bit Twister <bittwister2> |
| Component: | RPM Packages | Assignee: | D Morgan <dmorganec> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | bruno, doktor5000, gdugan, mageia, thierry.vignaud |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | udev | CVE: | |
| Status comment: | |||
|
Description
Bit Twister
2011-12-02 19:44:32 CET
do we need somewhere a require or something ? CC:
(none) =>
bruno, doktor5000, thierry.vignaud 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?
Manuel Hiebel
2011-12-08 16:19:58 CET
Keywords:
NEEDINFO =>
(none) Do you have a separated /usr partition? Keywords:
(none) =>
NEEDINFO (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.
Thierry Vignaud
2011-12-09 11:28:46 CET
Keywords:
NEEDINFO =>
(none) 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 =>
RESOLVED Can you actually push udev please :-) ? Just for reference (as I have this bug open in a tab) a new udev package was pushed. |