Public bug reported:
First I do not know if this is a CUPS issue or an Avahi issue.
I do not know whether Avahi or CUPS generates the files nor where they
are. They are not in /etc/avahi/services, where I expected to find them,
so they must lie somewhere in CUPS.
I have a printer installed in CU
Public bug reported:
First I do not know if this is a CUPS issue or an Avahi issue.
I do not know whether Avahi or CUPS generates the files nor where they
are. They are not in /etc/avahi/services, where I expected to find them,
so they must lie somewhere in CUPS.
I have a printer installed in CU
** Description changed:
First I do not know if this is a CUPS issue or an Avahi issue.
I do not know whether Avahi or CUPS generates the files nor where they
are. They are not in /etc/avahi/services, where I expected to find them,
so they must lie somewhere in CUPS.
I have a printe
** Description changed:
First I do not know if this is a CUPS issue or an Avahi issue.
I do not know whether Avahi or CUPS generates the files nor where they
are. They are not in /etc/avahi/services, where I expected to find them,
so they must lie somewhere in CUPS.
I have a printe
Public bug reported:
I have set up a /etc/avahi/services/scanner.service that looks like this
%h
_uscan._tcp
80
I expected that avahi would then advertise this service (I am shooting
to emulate eSCL, AKA Apple AirScan)
Trent, Thanks that does work. Now on to seeing how to addd the txt
attributes for scanner features and such, hopefully this too is
attainable.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launc
6 matches
Mail list logo