Red Hat Bugzilla – Bug 285101
USB printer port with wrong ownership/permissions
Last modified: 2008-06-16 10:28:13 EDT
Description of problem:
Booting Linux, I can't use the USB printer. The problem is that
/proc/bus/usb/???/??? belongs to root:root, and no group write.
It should be group lp, rw for group. After fixing this, cups has to be restarted.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Has happened for several kernels
Don't look at me, it has nothing to look with the kernel. Some time ago
(like, about a month) and update was pushed out which completely broke
this kind of ownership arrangement. Now there's not a single file owned
by a user other than root in the whole /dev. As a result, sound does not
work on my laptop. I'm pretty sure it's the same thing with you.
On second thought maybe I was wrong, because printer is not owned by the
console user. Please see bug 259141.
This used to work for a while, now (kernel-2.6.24-0.138.rc7.fc9,
cups-1.3.5-1.fc9, hplip-2.7.10-3.fc9) it is again broken.
Note that the affected files (/dev/bus/usb/???/???) are certainly auto-generated
by the kernel + udev.
I'm throwing this bug over to udev, or it will never get any attention.
Like I said, kernel does not know anything about permissions of device
files (it only sets default permissions for /sys but not device nodes).
should be fixed with udev-118
also note that you have to look at the ACLs for the device nodes. PolicyKit/HAL
sets ACLs for the console user.
# getfacl /dev/bus/usb/*/*
Yep, fixed by udev-118-1.fc9 here.
Note that "console user" is a non-issue here, the machine has no such user most
of the time. It shows no special ACLs in any case (just root logged in via tty).
Broken again with udev-118-11.fc9.x86_64. Same sympthoms as before, the relevant
daemons are running now.
the facls should be set by HAL
avahi-daemon, haldaemon, messagebus are all running.
Is there some logfile?
Currently hal-0.5.11-0.2.rc2.fc9.i386, installed 20080322
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
hal-0.5.11-1.fc10.x86_64, and it has been working fine for a while now.
Close this one?