network scanning

justwantin · 08-20-2008, 04:50 PM

I have been using hpoj to set up for network scanning with an hp psc printer/scanner up until slack 12.0 but I have now upgraded my printserver to 12.1.

It seems hpoj won't compile on 12.1 which is not surprising as the source is getting a bit old.

Is there anyone here sharing scanners. Scanning with HP-toolbox doesn't help much when one is on another computer.

TIA

justwantin · 09-11-2008, 04:29 AM

I thought I'd better finish this of in case anyone googles into it.

I had set everything up as I allways do for network scanning when upgrading the server to 12.1 but I could not get the clients to see the scanner on the server.

As it turns out there is now a /etc/udev/rules.d/55-hpmud.rules that creates the usb device for my hp-psc-2355 and gives in lpr.lpr ownership and 0660 permissions. Never was before AFAIK.

While I could scan as a user on the server in an ssh session the same user on a workstation would not have permission for network scanning on the server. Being in the group scanner was useless with the permission to lpr.

Solution late at night was change the rule for 0666 permission. Probably could just make users members of lpr too

Maybe I'm the only one networking a scanner to not know about this as I found no reference to it when googling and just stumbled into it in the hplip technical doc.

T3slider · 09-11-2008, 10:25 PM

From CHANGES_AND_HINTS.TXT available from your Slackware 12.1 install CD/DVD or from your favourite mirror (which is considered essential reading material):

Quote:

Originally Posted by CHANGES_AND_HINTS.TXT

There is a minor problem with the HPLIP and CUPS versions in Slackware 12.1;
hp-toolbox will not work unless LC_ALL is set to a UTF8 locale.
An easy workaround is to start it with "LC_ALL=$LANG.UTF8 hp-toolbox" if
you're not using a UTF8 locale. Also, your user account must be a member
of the "lp" group for hp-toolbox to work properly, and to use the scanner
portion of some (all?) HP print/scan/copy units, you'll need to be a member
of the "lp" group. This is due to the fact that hplip's udev rules set
the device with group "lp" ownership.

So, yes, adding your user to the 'lp' (not lpr...) group should have fixed the problem. Thanks for reporting a solution though -- it will probably help others in the future.

justwantin · 09-12-2008, 03:48 AM

Yes thanks I did mean lp., not lpr. My tyop.

I read the changes and hits but never paid much attention to the hplip part since with all the boxes using network printing and scanning hp-toolbox was not required. I didn't get around to upgrading the server until a couple weeks ago and just figured saned setup on the server would be same as before, just a little newer and shinier. Silly me.