On Tue, 2008-03-25 at 11:48 +0000, Tim Waugh wrote:
> Take a look at the 'lshal' output -- you should see an entry that
> contains 'scanner' in the 'info.capabilities' list.
Couldn't find a scanner, but did a grep and found print.
[root@scrappy ~]# lshal | grep scanner
[root@scrappy ~]# lshal | grep scan
[root@scrappy ~]# lshal | grep print
udi =
'/org/freedesktop/Hal/devices/usb_device_3f0_3f11_CN491B619BO2_if1_printer_CN491B619BO2'
info.capabilities = {'printer'} (string list)
info.category = 'printer' (string)
info.udi =
'/org/freedesktop/Hal/devices/usb_device_3f0_3f11_CN491B619BO2_if1_printer_CN491B619BO2' (string)
printer.commandset = {'LDL', 'MLC', 'PML', 'DYN'} (string list)
printer.device = '/dev/usb/lp0' (string)
printer.originating_device =
'/org/freedesktop/Hal/devices/usb_device_3f0_3f11_CN491B619BO2_if1'
(string)
printer.product = 'psc 1310 series ' (string)
printer.serial = 'CN491B619BO2' (string)
printer.vendor = 'hp' (string)
>
> Is that entry there? If not, for some reason the rules are not matching
> that device in:
> /usr/share/hal/fdi/policy/10osvendor/10-hplip.fdi
>
> If the entry is there, on the other hand, then for some reason the
> access_control.grant_group property is not getting set to 'lp', or else
> the group is not actually getting granted on the /dev/bus/xxx/yyy device
> node.
Something to note and maybe a new status..
I read over that bug report you asked me to look at and have done the
following since then..
Edited /etc/udev/rules.d/50-udev-default.rules
And change the below line to 664 instead of 644. Don't know if that was
right or wrong, but may not ahve anything to do with what I did after...
#libusb device nodes
SUBSYSTEM=="usb", ACTION=="add", ENV{DEVTYPE}=="usb_device",
NAME="bus/usb/$env{BUSNUM}/$env{DEVNUM}", MODE="0664"
Never could get printer to print, so I removed it. I then added it from
scratch,as in instead of plug n play, I just added it manually (via gui
though), selecting the appropriate hp drivers that it gave me, and so
far it is working, even after a reboot. It worked this morning, then I
updated it this afternoon after work, reboot and still works so far.
So I don't know what to do next, cept see if it fails, or do something
that you may want? I can remove it, disconnect it all or something, let
it auto detect again and see what happens? Just let me know.
BTW, in case you do have me perform couple tests, would like to get it
back to a working order again when done in case other half wants to
print in the mean time.
--
Mike Chambers
Fedora Project - Ambassador, Bug Zapper, Tester, User, etc..
mikec302@xxxxxxxxxxxxxxxxx
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
