-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
airsaned report no scanners available, though scanimage -L reports one #97
Comments
I guess it's related to the avahi failure. If you set |
I guess, I have: [root@contr ~]# systemctl status avahi-daemon.service ● avahi-daemon.service - Avahi mDNS/DNS-SD Stack Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled; preset: disabled) Active: active (running) since Sat 2023-01-14 23:15:58 UTC; 2 days ago TriggeredBy: ● avahi-daemon.socket Main PID: 302 (avahi-daemon) Status: "avahi-daemon 0.8 starting up." Tasks: 2 (limit: 2243) Memory: 1.6M CPU: 22.921s CGroup: /system.slice/avahi-daemon.service ├─302 "avahi-daemon: running [contr.local]" └─314 "avahi-daemon: chroot helper" Jan 14 23:15:58 contr avahi-daemon[302]: New relevant interface lo.IPv6 for mDNS. Jan 14 23:15:58 contr avahi-daemon[302]: Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1. Jan 14 23:15:58 contr avahi-daemon[302]: New relevant interface lo.IPv4 for mDNS. Jan 14 23:15:58 contr avahi-daemon[302]: Network interface enumeration completed. Jan 14 23:15:58 contr avahi-daemon[302]: Registering new address record for fe80::921b:eff:fe38:ee39 on enp1s0.*. Jan 14 23:15:58 contr avahi-daemon[302]: Registering new address record for 192.168.9.48 on enp1s0.IPv4. Jan 14 23:15:58 contr avahi-daemon[302]: Registering new address record for 192.168.9.11 on enp1s0.IPv4. Jan 14 23:15:58 contr avahi-daemon[302]: Registering new address record for ::1 on lo.*. Jan 14 23:15:58 contr avahi-daemon[302]: Registering new address record for 127.0.0.1 on lo.IPv4. Jan 14 23:15:59 contr avahi-daemon[302]: Server startup complete. Host name is contr.local. Local service cookie is 2060985771. |
What about |
No much difference. Still "No scanners available" :(
airsaned is run: |
I am trying to make AirSane build (https://aur.archlinux.org/packages/airsane-git) in archlinux to work.
I am starting airsaned via airsaned.service with:
It runs, but www frontend reports "AirSane Server on / No scanners available" :/
Switching to same user/groups I am able to detect scanner though:
Logs during start:
Does it mean that scanner is not detectable to airsaned?
Due to message bus security policy can't be made available?
Or any other issue?
TIA for any hints.
The text was updated successfully, but these errors were encountered: