F26: Print from gnome is not respect cups directive 'ErrorPolicy retry-job'

classic Classic list List threaded Threaded
14 messages Options
Reply | Threaded
Open this post in threaded view
|

F26: Print from gnome is not respect cups directive 'ErrorPolicy retry-job'

Dario Lesca
Into cups printer configuration file, I have set "ErrorPolicy retry-
job". When I print to a printer power off, I do not want stop printer,
I want cups still try to print until printer is power on.

And this work great if I print on a Fedora server (without GUI).

If I print a document from gnome on a printer unplugged or power off,
this printer is stopped, and when I power on it, I must go to into
control panel to start it.

How to disable this Gnome "unconfigurable" behavior (into Gnome contro
panel there are no options to do this)?

Many Thanks

--
Dario Lesca
(inviato dal mio Linux Fedora 26 Workstation)
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: F26: Print from gnome is not respect cups directive 'ErrorPolicy retry-job'

Tim-163
Allegedly, on or about 2 October 2017, Dario Lesca sent:

> Into cups printer configuration file, I have set "ErrorPolicy retry-
> job". When I print to a printer power off, I do not want stop
> printer, I want cups still try to print until printer is power on.
>
> And this work great if I print on a Fedora server (without GUI).
>
> If I print a document from gnome on a printer unplugged or power off,
> this printer is stopped, and when I power on it, I must go to into
> control panel to start it.
>
> How to disable this Gnome "unconfigurable" behavior (into Gnome
> contro panel there are no options to do this)?

Do I gather that you get two different behaviours:

Auto-restarting if you print directly from the printer server?
Not auto-restarting if you print from a client PC?

If so, how are your clients set up?

Have you let them auto-discover the server and not hand-configured the
clients?  (The server's configuration should handle all of this.)

Have you manually set up printer queues on each client PC?  (You need
to tweak everything on every PC, when done that way.)

Or are you just using one machine, and talking about Gnome desktop
behaviour differences?

--
[tim@localhost ~]$ uname -rsvp
Linux 4.12.13-300.fc26.x86_64 #1 SMP Thu Sep 14 16:00:38 UTC 2017 x86_64

Boilerplate:  All mail to my mailbox is automatically deleted.
There is no point trying to privately email me, I only get to see
the messages posted to the mailing list.

George Orwell's '1984' was supposed to be a warning against tyranny,
not a set of instructions for supposedly democratic governments.


.
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: F26: Print from gnome is not respect cups directive 'ErrorPolicy retry-job'

Dario Lesca
Il giorno lun, 02/10/2017 alle 23.26 +1030, Tim ha scritto:
> Do I gather that you get two different behaviours:
>
> Auto-restarting if you print directly from the printer server?

The printer it's connect to my workstation/server via USB cable

> Not auto-restarting if you print from a client PC?

The client is a workstation with Gnome Desktop, on which work cups
server and the user who prints the document.

Print from client on the printers shared from this workstation, is
another issue.... But here I try to resolve the subject issue.

>
> If so, how are your clients set up?

> Have you let them auto-discover the server and not hand-configured
> the clients?  (The server's configuration should handle all of this.)
>
> Have you manually set up printer queues on each client PC?  (You need
> to tweak everything on every PC, when done that way.)

This is another issue, which has been happening since I updated the
server workstation from Fedora 19 to Fedora 26.

For now all my two Fedora 26 client cannot print in any way on the
workstation/server Fedora 26, I have try many solution to resolve this
problem ... but for now I still have not resolved.

On server I have share in many way all printers, but all client cannot
see these printer. Before fedora 26, on this workstation there was
Fedora 19, all printers configured on it, were accessible by all
clients automatically.

And If I configure manually on client some printers (which are
accessible via https://ip:631/printers/printer1), the printer from
client not work.
For now I bypass this annoying problem to produce a pdf on client, copy
it on workstation/server and print it from it.
But thi is another problem, if someone have some suggest let me know
(thanks!)

> Or are you just using one machine, and talking about Gnome desktop
> behaviour differences?

Yes, in this tread I talk about this scenario.

On one machine (workstation/server) if I print a document from Gnome
Desktop and the usb printer is off, when I power on it, I must go to
control panel and restart the printer, even if into cups printers.conf
I have set for this printer 'ErrorPolicy retry-job'

Thanks

--
Dario Lesca
(inviato dal mio Linux Fedora 26 Workstation)
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: F26: Print from gnome is not respect cups directive 'ErrorPolicy retry-job'

Tim-163
Tim:
>> Or are you just using one machine, and talking about Gnome desktop
>> behaviour differences?

Dario Lesca:
> Yes, in this tread I talk about this scenario.
>
> On one machine (workstation/server) if I print a document from Gnome
> Desktop and the usb printer is off, when I power on it, I must go to
> control panel and restart the printer, even if into cups
> printers.conf I have set for this printer 'ErrorPolicy retry-job'

I'm in unfamiliar problem resolving territory, here, but I'll have a
bash at it, though I'm running Mate instead of Gnome.  It's a bit
surprising why command-line printing should be different that GUI
printing, in this regards.

I occasionally have the same problem, and had to do the same thing (go
into a config control and restart the printer), but not always.
Perhaps there's a time period involved where it auto-restarts?  My
situation is made a bit easier by my printer being permanently on, and
it's stand-by mode (that it goes into when left idle) doesn't make the
printed appear to be powered off.  It's things like power failure
recovery, or pulling out network leads, that provokes a problem that
needs manual intervention.

What's an example command line to start printing that successfully
wakes up a sleeping printer?  How are you printing in command line?

I wonder if you should be looking for another error policy, related to
resume or restart printer, rather than the job?

How have you made this ErrorPolicy change to the config file?
Exactly where did you put it?
Exactly what command did you put?
There can be a time delay parameter, and it may need to be different.
There may be a global option, it may be doable with each printer.

You may want to mention whether it makes any difference to having to
restart the printer queue if the printer was on, then went to sleep
because it was left idle, and it self-switched-off, versus you switched
it off yourself.

Also, does manually switching on the printer before you attempt to
print make any difference?  Perhaps switching it on a good minute
before.

--
[tim@localhost ~]$ uname -rsvp
Linux 4.12.14-300.fc26.x86_64 #1 SMP Wed Sep 20 16:28:07 UTC 2017 x86_64

Boilerplate:  All mail to my mailbox is automatically deleted.
There is no point trying to privately email me, I only get to see
the messages posted to the mailing list.

Error: unable to decode remainder of message.


.
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: F26: Print from gnome is not respect cups directive 'ErrorPolicy retry-job'

Tim-163
In reply to this post by Dario Lesca
Since this is an offshoot of your thread, I'm responding separately.

Tim:
>> If so, how are your clients set up?
>> Have you let them auto-discover the server and not hand-configured
>> the clients?  (The server's configuration should handle all of
>> this.)
>>
>> Have you manually set up printer queues on each client PC?  (You
>> need to tweak everything on every PC, when done that way.)

Dario Lesca:

> This is another issue, which has been happening since I updated the
> server workstation from Fedora 19 to Fedora 26.
>
> For now all my two Fedora 26 client cannot print in any way on the
> workstation/server Fedora 26, I have try many solution to resolve
> this problem ... but for now I still have not resolved.
>
> On server I have share in many way all printers, but all client
> cannot see these printer. Before fedora 26, on this workstation there
> was Fedora 19, all printers configured on it, were accessible by all
> clients automatically.
>
> And If I configure manually on client some printers (which are
> accessible via https://ip:631/printers/printer1), the printer from
> client not work.
> For now I bypass this annoying problem to produce a pdf on client,
> copy it on workstation/server and print it from it.
> But thi is another problem, if someone have some suggest let me know

Firstly, things can be easier, or more consistent, if you only use one
method of configuring printing, such as the CUPs webserver interface,
rather than a desktop tool.

Running a central printer server for several clients requires a few
things:

The print server's configuration needs to be set up to share its
printers.  From the CUPs configuration at <http://localhost:631/>, you
need to go into the "administration" section and select the "share
printers connected to this system" option, then click on the "change
settings" form button to save that change.  If you have a non-english
installation, CUPs will probably use your own language, and you'll need
to find the same features with similar descriptions.

This makes the server publish its printers to clients, and should make
the server listen for connections on all LAN interfaces.

On the server, the firewall must be opened for ports 631 for TCP and
UDP traffic.  

If you're using the firewall configuration GUI this will mean allowing
the IPP service (older configurators listed them as some form of "print
server" and "print client").  There's also a zone configuration, where
you can preset some different configurations for the firewall (home use
with relaxed firewalls, public use with tight firewals, etc.).  Meaning
you can set up some rules beforehand for those situations, and change
the whole lot of rules just by changing zones.  Be aware that the
configurator has two ways of working, runtime and permanent.  The
runtime mode will change settings now, as you try them, but not save
them as permanent settings.  The permanent mode will do both, together
(set rules and save them).

You should enable and start the cups service, and I can't recall
whether you also need to do the same with the cups-browsed service, the
following commands will do it (as root or using sudo):

systemctl enable cups
systemctl start cups
systemctl enable cups-browsed
systemctl start cups-browsed

                 -----------------------------------

On the clients, the firewall must be opened for ports 631 using UDP
traffic.

If you're using the firewall configurator GUI, this will mean allowing
the IPP-client service.

You should not have to set up any printers on the clients, they should
simply find the printers offered by the server, and you can select
which one to print to when you want to print something.  You can,
optionally, preset one as the default printer.  And your programs would
print to it, by default, if you don't choose another printer.

NB:  If you start setting up printers on the clients (e.g. selecting
drivers, etc.), then you lose the convenience of having a central
server, and have to individually set up each printer on the client,
including all the special options that you want.

But for the automatic printer discovery, you should enable and start
the cups service, *and* the cups-browsed service, the following
commands will do it (as root or using sudo):

systemctl enable cups
systemctl start cups
systemctl enable cups-browsed
systemctl start cups-browsed

As best as I can recall, that's all I've had to do.  Forgetting the
cups-browsed service is what always catches me.  There's no reminder
about that when you're reading the CUPs options in the web browser.

--
[tim@localhost ~]$ uname -rsvp
Linux 4.12.14-300.fc26.x86_64 #1 SMP Wed Sep 20 16:28:07 UTC 2017 x86_64

Boilerplate:  All mail to my mailbox is automatically deleted.
There is no point trying to privately email me, I only get to see
the messages posted to the mailing list.

Ha ha ha ha...
(I couldn't think of a good joke, so I supplied a laugh track, instead.)


.
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: F26: Print from gnome is not respect cups directive 'ErrorPolicy retry-job'

Dario Lesca
Il giorno mar, 03/10/2017 alle 19.34 +1030, Tim ha scritto:
>
> Firstly, things can be easier, or more consistent, if you only use
> one method of configuring printing, such as the CUPs webserver
> interface, rather than a desktop tool.

I have configure my two USB home printers via https://localhost:631

> Running a central printer server for several clients requires a few
> things:
>
> The print server's configuration needs to be set up to share its
> printers.  From the CUPs configuration at <http://localhost:631/>,
> you need to go into the "administration" section and select the"share
> printers connected to this system" option, then click on the "change
> settings" form button to save that change.
>

Yes, my cups server (igloo) is configured like you suggest.

    [    lesca@igloo     ~]$ sudo cupsctl
    [sudo] password di lesca:
    _debug_logging=0
    _remote_admin=0
    _remote_any=1
    _share_printers=1
    _user_cancel_any=1
    BrowseLocalProtocols=dnssd
    DefaultAuthType=Basic
    JobPrivateAccess=default
    JobPrivateValues=default
    MaxLogSize=0
    PageLogFormat=
    SubscriptionPrivateAccess=default
    SubscriptionPrivateValues=default
    WebInterface=Yes

Note the flag _remote_admin=0 and _remote_any=1

Remote admin is disable but if I try to connect to http://igloo:631/
from my notebook (dodo) I can connect to it and configure any token and
printers.

I also try to enable remote any but nothing is change.

> This makes the server publish its printers to clients, and should
> make the server listen for connections on all LAN interfaces.

Yes, my server is accessible on 631/tcp port and is bind on all
interface.

    [    lesca@igloo     ~]$ sudo netstat -natup |grep 631
    [sudo] password di lesca:
    tcp        0      0 0.0.0.0:631             0.0.0.0:*               LISTEN      6871/cupsd          
    tcp6       0      0 :::631                  :::*                    LISTEN      6871/cupsd          

> On the server, the firewall must be opened for ports 631 for TCP and
> UDP traffic.  

The firewall is open on port 631/TCP, but the port 631/UDP ? ... what
is it for?

Only if I start cups-browsed there is a 631/udp port listening on all
server IP, but this service is only useful on the client, on the server
is not necessary, from man page:

    "cups-browsed - A daemon for browsing the Bonjour broadcasts of
    shared, remote CUPS printers"

On my printers server do not want "broadcasts of shared, remote CUPS
printers". This is what I try to do on Client.
 
On printers server I want share two printers and this printer are
shared:

    [    root@igloo     ~]# grep -E '(Printer|Shared)' /etc/cups/printers.conf
    # Printer configuration file for CUPS v2.2.2
    <DefaultPrinter Cups-PDF>
    MakeModel Generic CUPS-PDF Printer
    Shared No
    </DefaultPrinter>
    <Printer HP_Deskjet_5900>
    Location Local Printer
    Shared Yes
    </Printer>
    <Printer Samsung_ML-1710>
    Location Local Printer
    Shared Yes
    </Printer>

> If you're using the firewall configuration GUI

Thanks for your explanation but my firewalld is off, I use shorewall
and the all port/proto are open for all PC into my lan to cups server.

> You should enable and start the cups service,

Yes, all the necessary cups services are enabled and start:

    [    root@igloo     ~]# systemctl list-unit-files |grep ^cups
    cups.path                                   enabled        
    cups-browsed.service                        disabled      
    cups.service                                enabled        
    cups.socket                                 enabled        

>  and I can't recall whether you also need to do the same with the
> cups-browsed service, the following commands will do it (as root or
> using sudo):
>
> systemctl enable cups
> systemctl start cups
> systemctl enable cups-browsed
> systemctl start cups-browsed

Only cups-browsed is not start on server, it's not necessary, and also
if I try start this service, none printer is pushed to my client.

>                  -----------------------------------
>
> On the clients, the firewall must be opened for ports 631 using UDP
> traffic.

On the client firewalld and SElinux are disabled, then all ports is
open.

> You should not have to set up any printers on the clients, they
> should simply find the printers offered by the server, and you can
> select which one to print to when you want to print something.  You
> can, optionally, preset one as the default printer.  And your
> programs would print to it, by default, if you don't choose another
> printer.
>
> NB:  If you start setting up printers on the clients (e.g. selecting
> drivers, etc.), then you lose the convenience of having a central
> server, and have to individually set up each printer on the client,
> including all the special options that you want.
>
> But for the automatic printer discovery, you should enable and start
> the cups service, *and* the cups-browsed service, the following
> commands will do it (as root or using sudo):
>
> systemctl enable cups
> systemctl start cups
> systemctl enable cups-browsed
> systemctl start cups-browsed
>
> As best as I can recall, that's all I've had to do.  Forgetting the
> cups-browsed service is what always catches me.  There's no reminder
> about that when you're reading the CUPs options in the web browser.

On my client all this service is enabled and start and I have do
anythings you suggest.

    [    root@dodo    :~]# systemctl list-unit-files |grep ^cups
    cups.path                                                        enabled        
    cups-browsed.service                                             enabled        
    cups.service                                                     enabled        
    cups.socket                                                      enabled        

This is the point: all what you suggest are done, but none printers are
pushed from server to my client.

If I power on the old server with Fedora 19, and connect it to my lan,
all printers on this old server are pushed to my client, without change
nothing on client.

This is all. I no longer know what to try to do to solve my problem

Many thanks for you help.

--
Dario Lesca
(inviato dal mio Linux Fedora 26 Workstation)
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: F26: Print from gnome is not respect cups directive 'ErrorPolicy retry-job'

Dario Lesca
In reply to this post by Tim-163
Il giorno mar, 03/10/2017 alle 19.30 +1030, Tim ha scritto:
> What's an example command line to start printing that successfully
> wakes up a sleeping printer?

sudo cupsenable printer1

>   How are you printing in command line?

lp -d printer1 /tmp/file.pdf

>
> I wonder if you should be looking for another error policy, related
> to resume or restart printer, rather than the job?

Other error policy (abort-job, retry-current-job, stop-printer) are not
useful for me, I want retry-job

> How have you made this ErrorPolicy change to the config file?

Via browser: https://igloo:631/admin/#CUPS_POLICIES then drop down menu
and choice "Error Policy:"

> Exactly where did you put it?

I have put it via web interface

> Exactly what command did you put?

?

> There can be a time delay parameter, and it may need to be different.

Can be, but I do not know.

> There may be a global option, it may be doable with each printer.

May be, but I do not know

> You may want to mention whether it makes any difference to having to
> restart the printer queue if the printer was on, then went to sleep
> because it was left idle, and it self-switched-off, versus you
> switched it off yourself.
>
> Also, does manually switching on the printer before you attempt to
> print make any difference?  Perhaps switching it on a good minute
> before.

yes, turn on printer before print the document is the better solution,
but some time the user do not remember to do that and print.

I have try this case, but the printer has not been put off.
Only a few times this happens

Thanks for reply, now I try to do some test how to reproduce this
problem and let you known

Many thanks

--
Dario Lesca
(inviato dal mio Linux Fedora 26 Workstation)
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: F26: Print from gnome is not respect cups directive 'ErrorPolicy retry-job'

Samuel Sieb
In reply to this post by Dario Lesca
On 10/04/2017 03:07 PM, Dario Lesca wrote:
> This is the point: all what you suggest are done, but none printers are
> pushed from server to my client.
>
> If I power on the old server with Fedora 19, and connect it to my lan,
> all printers on this old server are pushed to my client, without change
> nothing on client.
>
> This is all. I no longer know what to try to do to solve my problem

Cups now uses mdns to broadcast printers.  So you might need to open the
mdns ports to allow those packets to go out.  Also you might require
avahi-daemon to be running.
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: F26: Print from gnome is not respect cups directive 'ErrorPolicy retry-job'

Tim-163
Allegedly, on or about 4 October 2017, Samuel Sieb sent:
> Cups now uses mdns to broadcast printers.

Oh, yuck.  Yet another thing in the mix.  Three daemons just to use a
printer!  Really?!

> So you might need to open the mdns ports to allow those packets to go
> out.  Also you might require avahi-daemon to be running.

You might, but I don't.  Currently on FC26, that uname thing in my
signature is a script that runs whenever I post, it's not static.

--
[tim@localhost ~]$ uname -rsvp
Linux 4.12.14-300.fc26.x86_64 #1 SMP Wed Sep 20 16:28:07 UTC 2017 x86_64

Boilerplate:  All mail to my mailbox is automatically deleted.
There is no point trying to privately email me, I only get to see
the messages posted to the mailing list.

It seems the modern trend with Linux programmers is to change existing software
so that it's more annoying to use (e.g. making reboots required, when they
never used to be), then denying that *that* is a nuisance, then saying it's
necessary (ignoring that several years of prior versions didn't have that
stupid requirement), then complaining about being criticised for making things
worse.  Don't try giving me an Emperor's New Clothes routine, it won't wash.
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: F26: Print from gnome is not respect cups directive 'ErrorPolicy retry-job'

Dario Lesca
In reply to this post by Samuel Sieb
Il giorno mer, 04/10/2017 alle 19.42 -0700, Samuel Sieb ha scritto:
> Cups now uses mdns to broadcast printers.

Thank Samuel.

There is some documentation for learn this news?

>  So you might need to open the mdns ports to allow those packets to
> go out.

On lan interface of printers server I have open all port from/to it
to/from all PC, I must do something other?

>  Also you might require avahi-daemon to be running.

This service is available for default, I do not power off it.

Thanks

--
Dario Lesca
(inviato dal mio Linux Fedora 26 Workstation)
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: F26: Print from gnome is not respect cups directive 'ErrorPolicy retry-job'

Samuel Sieb
In reply to this post by Tim-163
On 10/05/2017 02:31 AM, Tim wrote:
> Allegedly, on or about 4 October 2017, Samuel Sieb sent:
>> Cups now uses mdns to broadcast printers.
>
> Oh, yuck.  Yet another thing in the mix.  Three daemons just to use a
> printer!  Really?!

Three daemons?  You mean cupsd + avahi-daemon on the server and cupsd +
cups-browsed on the client?  How about it's nice that there's a useful
standard for things and everything except Windows can find printers on
the network?

Also, you don't need this to use a printer.  You can just run cupsd to
print to a local printer or you can manually add the remote cups printer
on the client.  What's the problem?
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: F26: Print from gnome is not respect cups directive 'ErrorPolicy retry-job'

Samuel Sieb
In reply to this post by Dario Lesca
On 10/05/2017 02:42 AM, Dario Lesca wrote:
> Il giorno mer, 04/10/2017 alle 19.42 -0700, Samuel Sieb ha scritto:
>> Cups now uses mdns to broadcast printers.

> There is some documentation for learn this news?

I don't know, https://en.wikipedia.org/wiki/CUPS has a lot of info.  I
noticed it in the cups-browsed config file.

>>   So you might need to open the mdns ports to allow those packets to
>> go out.
>
> On lan interface of printers server I have open all port from/to it
> to/from all PC, I must do something other?

That's fine then.

>>   Also you might require avahi-daemon to be running.
>
> This service is available for default, I do not power off it.

Make sure you also have "nss-mdns" installed on the client.  Try running
"avahi-browse -a" to see if the printers are actually getting broadcast.
  That program is in the "avahi-tools" package.
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: F26: Print from gnome is not respect cups directive 'ErrorPolicy retry-job'

Tim-163
In reply to this post by Samuel Sieb
Tim:
>> Oh, yuck.  Yet another thing in the mix.  Three daemons just to use
>> a printer!  Really?!

Samuel Sieb:
> Three daemons?  You mean cupsd + avahi-daemon on the server and cupsd
> + cups-browsed on the client?

Yes, considering that I never needed to run avahi before, and don't
want to run it either.  I don't care for adhoc disorganised networking
that's not controlled by me - I already have DHCP and DNS servers
handling that.  Trying to get a third thing involved, and all of that
running in harmony is a nightmare I don't want to have.

And *I* don't run avahi, yet printing and printer browsing work for me.
CUPS always managed to advertise it's printers to the network, and the
clients always managed to find those printers.  Let printing be handled
by the printing software, not some middling networking server.

DHCP and DNS is quite tightly controlled as to what gets assigned what
addresses on this LAN.  Avahi is a randomised free-for-all.

--
[tim@localhost ~]$ uname -rsvp
Linux 4.12.14-300.fc26.x86_64 #1 SMP Wed Sep 20 16:28:07 UTC 2017 x86_64

Boilerplate:  All mail to my mailbox is automatically deleted.
There is no point trying to privately email me, I only get to see
the messages posted to the mailing list.

_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: F26: Print from gnome is not respect cups directive 'ErrorPolicy retry-job'

Dario Lesca
In reply to this post by Samuel Sieb
Il giorno gio, 05/10/2017 alle 13.15 -0700, Samuel Sieb ha scritto:
> Make sure you also have "nss-mdns" installed on the client.  Try
> running
> "avahi-browse -a" to see if the printers are actually getting
> broadcast.
>   That program is in the "avahi-tools" package.

I have verify on printers server and the avahi-daemon.service and
avahi-daemon.socket are masked!

I have unmask, enable and start it and now my client see the printers
shared and run "avahi-browse -a" list my shared printers.

Then avahi-daemon is necessary for CUPS. This is a news for me.

Many thanks!

--
Dario Lesca
(inviato dal mio Linux Fedora 26 Workstation)
_______________________________________________
users mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]