Red Hat Bugzilla – Bug 429000
USB printer port with wrong ownership/permissions
Last modified: 2013-03-05 22:54:20 EST
Description of problem: Again, on boot I get: crw-r--r-- 1 root root ... /dev/bus/usb/001/004 # USB printer here I need to: chgrp lp /dev/bus/usb/001/004 chmod g+rw /dev/bus/usb/001/004 service cups restart to be able to print Version-Release number of selected component (if applicable): udev-118-1.fc9 How reproducible: Always (booted twice) Steps to Reproduce: 1. Boot 2. Check permissions on USB port with printer 3. Actual results: Expected results: Additional info:
Immediately after plugging in the printer, what does 'getfacl' say on the device node? The 'ls -l' output you gave looks correct (that's how a correctly configured device node will look for 'ls -l'), but does not include enough information to say whether or not the ACL permissions are correct.
The printer is plugged in all time. [vonbrand@quelen ~]$ getfacl /dev/bus/usb/001/004 getfacl: Removing leading '/' from absolute path names # file: dev/bus/usb/001/004 # owner: root # group: root user::rw- group::r-- other::r-- (yes, I had to fix permissions yet again after booting yesterday)
But I want to see what they are immediately after the node is created, before you fix anything.
That is what they are on reboot!
What does 'lsusb' say when the printer is plugged in and switched on?
# getfacl /dev/bus/usb/001/004 getfacl: Removing leading '/' from absolute path names # file: dev/bus/usb/001/004 # owner: root # group: root user::rw- group::r-- other::r-- # lsusb Bus 001 Device 004: ID 03f0:3817 Hewlett-Packard LaserJet P2015 Series Bus 001 Device 001: ID 0000:0000 Bus 002 Device 003: ID 1241:1177 Belkin F8E842-DL Mouse Bus 002 Device 002: ID 0a81:0101 Chesen Electronics Corp. Keyboard Bus 002 Device 001: ID 0000:0000
Hmm, this works as expected here. 1. What does 'rpm -q hal' say? 2. Can you please attach the output of 'lshal'? Thanks.
# rpm -q hal hal-0.5.10-4.fc9.x86_64 # lshal error: dbus_bus_get: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
# service haldaemon status hald is stopped # service haldaemon start Starting HAL daemon: [FAILED]
Hum... just noticed that service messagebus was not enabled. Starting that one I can start avahi-daemon and the haldaemon. Rebooting with messagebus enabled gives: # getfacl /dev/bus/usb/001/004 getfacl: Removing leading '/' from absolute path names # file: dev/bus/usb/001/004 # owner: root # group: root user::rw- group::r-- group:lp:rw- mask::rw- other::r-- and printing works! Sorry for the mess.
It is back today! I checked, messagebus, avahi-daemon and haldaemon are all running.
Created attachment 295810 [details] Output of lshal hal-0.5.10-5.fc9.x86_64
Just checked the output of lshal, there the printer shows up as 001/005, when it definitely is at 001/004. Changing ownership/permission of the last one and restarting cups allows me to print.
So I need to see three bits of information all at once: 1. lsusb, to see which xxx/yyy number is correct 2. lshal, to see that the correct attributes are set 3. getfacl /dev/bus/usb/xxx/yyy, to see the ACLs
Created attachment 295908 [details] lsusb output
Created attachment 295910 [details] lshal output
Created attachment 295911 [details] getfacl /dev/bus/usb/001/* output
Note that I changed ownership/permissions on 001/004 by hand.
Weird... tried again to make sure. Clean reboot, printer is now at 001/004. messagebus, avahi-daemon, haldaemon all active. Printing works. I swear it did not work before!
If it recurs, please attach the information requested *without* changing any permissions.