From ArchWiki

Parallel port scanners

Hi folks.

Scanning over my parallel port scanner does not work unless my user is in the "lp" group. This article says that users need not be in any special group for the scanner to work since systemd.

Basically, my experience contradicts the article and I would like to either fix my setup or the article so both are in agreement.

Davidmcinnis (talk) 21:42, 18 June 2017 (UTC)

I wasn't aware that parallel port scanners were a thing!
SANE#Permission problem is really only relevant for usb scanners - parallel ports are assumed to have printers attached, and CUPS uses the lp group for other purposes. See FS#50009, and the note in CUPS#Connection Interfaces. The short version is that the wiki should be fixed to mention this and that you adding your user to the lp group is perfectly fine unless you are concerned about your user being able to view some of the CUPS files, which may contain sensitive information such as network printer passwords.
-- Pypi (talk) 00:46, 19 June 2017 (UTC)
I've made an edit to the page - does that fix the article for you? -- Pypi (talk) 01:25, 19 June 2017 (UTC)

Works for me. Thank you very much! —This unsigned comment is by Davidmcinnis (talk) 08:54, 1 April 2019 (UTC). Please sign your posts with ~~~~!

Multi-function printers/scanners

Hi Everyone,

I think the fix discussed above with “lp” udev group can also help with USB multi-function printers/scanners. My understanding of the problem is: a single device can not be owned by multiple groups in udev. So as soon as you add the rule with GROUP=“scanner”, printing may stop working. It’s kind of random, sometimes it works, so I spent a lot of time debugging it.

The solution for me was to use GROUP=“cups” in the scanner rule mentioned in SANE#Permission problem. I tried to edit the page, but my edit was reverted. Maybe someone could phrase it better than me.

Maxtomin (talk) 07:30, 13 June 2019 (UTC)

Unclear / Vague Section: Network attached scanners

I am not sure what the original author meant when he wrote: "Some scanners may be network attached and already provide their own server." What does he refer to? Scanners that have a web-interface from which one can create scans? So the reader could spare the trouble of installing sane and use that? Or is he referring to printers that can be used in a PnP fashion if sane-airscan is installed? Am I missing something? It might also be a good idea to mention that many modern scanners will immediately work over the network as long as you have sane-airscan installed. (Perhaps in the Installation Section?) LoNaAleim (talk) 12:56, 30 January 2021 (UTC)

Adding troubleshooting information for hpaio attached scanners


I would like to add some minor troubleshooting information for HP scanners that are accessed via hpaio. Some of these scanners need a plugin to operate and often stop working after an hplip upgrade because the plugin remains misaligned wrt the hplip version. The problem is that users do not get a prompt to install a new plugin, but just a very misleading indication of an I/O error.

Adding a quick note about the fact that some HP scanners need a plugin, that the latter can be installed via the AUR hplip-plugin package or using the hp-plugin command, that many issues can be caused by a version misalignment between the plugin and hplip could probably be useful (at least unless the hplip package can gain a post install script checking the plugin version and warning if needed).

Any opinion, suggestion?

—This unsigned comment is by Callegar (talk) 21:37, 15 March 2022‎ (UTC). Please sign your posts with ~~~~!