On 9/29/20 2:29 PM, Doug McGarrett wrote:
Addendum to message below. After I sent it, I found a popup comment box added to "Set Up Scanning via Network" It reads:
YaST2 - scanner @ linux1 <3> (linux1 is name of computer) ______________________________________________________________________________________ Cannot stop and disable saned.socket (no /usr/lib/systemd/system/saned.socket). Falling back to disable saned for xinetd and reload xinetd.service. sed: can't read /etc/xinetd.d/sane-port: No such file or directory Failed to disable saned in /etc/xinetd.d/sane-port _______________________________________________________________________________________ This should fall at the end of the setup I wrote below. --doug
/snip/ Also, yast can't find a scanner, even tho it is a part of the Epson WP-4530 all-in-one (which I finally got working!) The scanner is for all purposes a different machine than the printer. Yes, I understand that. Here is the result of the yast query:
Using yast, (YaST2) :
Driver v Scanner epson2 No scanner recognized by this driver net No scanner recognized by this driver
Following up on that: Page called "Set Up Scanning via Network"
Server Settings Permitted Clients for saned 127.0.0.0/8, changed to 192.168.1.0/24, per note in box
Client Settings Servers Used for the net Metadriver localhost, that's what this was set at; I didn't change it
Predefined Configurations Local Host Configuration Disable Scanning via Network <<<<<<<<<What's this??? I cannot change this!
When checking box "OK" get Error Failed to set up scanning via network
Hope this all meakes sense to the reader--I'm kinda snowed! --doug
To unsubscribe, e-mail: email@example.com To contact the owner, e-mail: firstname.lastname@example.org