Bug 873979 - Yast2 Scanner Configuration return error when configuring scanning through network
Summary: Yast2 Scanner Configuration return error when configuring scanning through ne...
Status: RESOLVED DUPLICATE of bug 859353
Alias: None
Product: openSUSE 13.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Final
Hardware: x86-64 openSUSE 13.1
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Johannes Meixner
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-16 14:52 UTC by Jean-Claude Dole
Modified: 2014-04-22 08:02 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jean-Claude Dole 2014-04-16 14:52:47 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:28.0) Gecko/20100101 Firefox/28.0

When I try to configure scanning thru network in yast2/hardware/scanner, I get this error : /usr/lib/YaST2/bin/setup_network_scanner_config: line 74: /etc/init.d/xinetd: No such file or directory
Failed to start xinetd
For all detailed information please see post #1 at : http://forums.opensuse.org/showthread.php/493624-OS-13-1-Yast2-Scanner-Configuration

Reproducible: Always

Steps to Reproduce:
1.Fresh install of 13.1 on notebook
2.Install driver for USB EPSON PERFECTION V500 PHOTO scanner following vendor recommendation
3.yast2/scanner
4.From a linux notebook try to configure an USB EPSON PERFECTION V500 PHOTO which is connected to another linux box.
Actual Results:  
popup message : /usr/lib/YaST2/bin/setup_network_scanner_config: line 74: /etc/init.d/xinetd: No such file or directory
Failed to start xinetd

Expected Results:  
Scanner should be accessible across the local network

In /usr/lib/YaST2/bin/setup_network_scanner_config ; near line 74 after replacing all stuff like "$XINETD_INIT_SCRIPT status" by "systemctl status xinet.service" and "reload" by restart, it "seems ? ? ? " to work.