Ah. In /lib/udev/rules.d/50-udev-default.rules: KERNEL=="fuse", ACTION=="add", MODE="0666", OPTIONS+="static_node=fuse"
So most udev rules apply MODE settings unconditionally, but the fuse rule for some reason applies permissions only for ACTION==add. That means that when we rescan with --action=change, this device gets the default device permissions applied instead of the ones intended for /dev/fuse. I think the correct fix here is to drop the 'ACTION=="add"', but this should be checked with upstream to be sure. As for rfkill, I don't see what's causing the permission change. It may be an adverse interaction with udev-acl, I'm not sure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1152718 Title: udevadm seems to set incorrect permissions for /dev/fuse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1152718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
