Bugzilla – Bug 332750
HP scanner only works as root
Last modified: 2007-11-22 19:18:42 UTC
I have tried to get the scanner in a HP Photosmart C3180 USB multi-function printer to work with the hpaio driver. I actually succeeded, but the scanner only works, when I'm logged in as root user. Both Kooka and xsane doesn't seem to access the scanner in "normal" user mode. Where is the bug, and could you release please release a patch? I obviously seems to be an access permission issue.
Please attach y2logs. If you are in doubt follow: http://en.opensuse.org/Bugs/YaST Thanks!
Created attachment 177868 [details] y2logs If more info is needed, please contact me.
Created attachment 178315 [details] y2logs I confirm this issue with HP PSC 2350. I attach YaST logs too, if they can be of help. Regards, Alberto
Considering these scanners are probably among the most used in Linux, I increase severity a bit :-)
Please post your /etc/hal/fdi/policy/10osvendor/70-scanner.fdi , output of 'hwinfo --scanner' and 'lshal'.
Unfortunately I am not home in at a least 2 weeks from now! I will post the requested info at that time. I'm truly sorry!
Created attachment 178617 [details] 70-scanner.fdi
Created attachment 178621 [details] lshal.txt The hwinfo --scanner command doesn't output anything. I attached the information you requested before installing the today provided security patch for hplip. After installing the patch, I can start xsane as a user and scan documents, so it seems the patch fixed this issue too. I'll do some more check, but it seems to work ok now for me. Regards, Alberto
Mads, could you please confirm the hplip patch fixes this issue also for you?
As soon as I get home. Next monday. I'm sorry. Can you mark it as resolved for the time being?
#10: ok
To me, the security patch does not fix the problem.
I suspect bug#309933 and bug#309933 are related if not duplicates.
(In reply to comment #13 from Jarl Friis) > I suspect bug#309933 and bug#309933 are related if not duplicates. > I ment bug#309933 and bug#332750 may be related.
Can both of you activate the "set -x" line in /usr/lib/YaST2/bin/test_and_set_scanner_access_permissions and then run it as root as /usr/lib/YaST2/bin/test_and_set_scanner_access_permissions 2>/tmp/out and attach /tmp/out text/plain attachments to this bug.
Created attachment 181472 [details] Providing information requested in comment #15
/usr/lib/YaST2/bin/test_and_set_scanner_access_permissions detects the HP USB device but then hp-makeuri -s 001:002 seems to result no useful output so that in the end no entry for your device is written to /etc/hal/fdi/policy/10osvendor/80-scanner.fdi To find out what goes wrong, run lsusb -d 03f0: which should result something like Bus 123 Device 456: ID 03f0:7004 HP Photosmart C3180 Note the actual bus and device numbers and run hp-makeuri -s 123:456 with your actual bus and device numbers. For example on my machine: ------------------------------------------------------------------ # lsusb -d 03f0: Bus 003 Device 017: ID 03f0:0417 HP LaserJet 1220 # hp-makeuri -s 003:017 hpaio:/usb/HP_LaserJet_1220?serial=00XXXXXXXXXX ------------------------------------------------------------------ By the way: The easiest workaround to get scanner access for normal users is to use the saned and the net meta-backend on your local host to access the scanner, for example via "YaST scanner setup" -> "Other" -> "Scanning via Network" -> "Local Host Configuration". A little drawback is that now scanning-frontends for root will "see" the scanner twice. Once directly as "hpaio:..." and a duplicate via the net meta-backend as "net:localhost:hpaio:...".
Created attachment 181632 [details] 70-scanner.fdi This is from another PC (my laptop) - but same problem.
Created attachment 181641 [details] lshal Again. This is the output from my other computer - again, the same problem. The hwinfo --scanner command doesn't output anything.
(In reply to comment #9 from Matej Horvath) > Mads, could you please confirm the hplip patch fixes this issue also for you? > It doesn't fix the issue. On none of my pc's. Unfortunately.
(In reply to comment #15 from Johannes Meixner) > Can both of you activate the "set -x" line in > /usr/lib/YaST2/bin/test_and_set_scanner_access_permissions > and then run it as root as > /usr/lib/YaST2/bin/test_and_set_scanner_access_permissions 2>/tmp/out > and attach /tmp/out text/plain attachments to this bug. I did this as well... However after doing so, the scanner (OfficeJet G85) is now available to non-root. So I cannot reproduce this bug anymore. To be honest, I don't know exactly what fixed my problem, but it seems like running /usr/lib/YaST2/bin/test_and_set_scanner_access_permissions fixed the problem. It could also be that that the security patch + reboot (i.e. restart hplip) solved the problem. Even though I claimed in comment #12 that the security patch (alone) did not fix the problem. I may be wrong here. If you are still interested in the output of the command let me know, but I don't think it is that interesting anymore since my system works now...
Created attachment 181792 [details] out I did what I was asked to do in #15, but it makes no difference. The user access for the scanner still doesn't work. I've also double checked that the patch is in fact installed... and it is. I have attached the /tmp/out file.
Regarding comment #21: /usr/lib/YaST2/bin/test_and_set_scanner_access_permissions is run by YaST for each scanner setup. I have no idea why it didn't work on the first run. For some background information see comment #17. Regarding comment #22: In attachment #181792 [details] there is the error "lsusb: command not found". Without "lsusb" it cannot work. It looks like a messed up system installation (e.g. "usbutils" RPM not installed or removed). When you manually remove packages which are installed in the default system, arbitrary problems can happen.
(In reply to comment #23 from Johannes Meixner) > When you manually remove packages which are installed > in the default system, arbitrary problems can happen. Instead of when, try if... I don't recall changing or deleting the usbutils package. I did a fresh install from the KDE cd. But who knows... Anyway... I'm on the road (again), so I can't test the scanner. Happy to see the RESOLVED tag, though... :) :)
As per comment #21 and comment #24 the fix is verified.