Bug#899259: closed by Brian Potkin (Re: Bug#899259: cups-daemon: with IdleExitTimeout 60, fails to exit after 60 s of inactivity)

On Thu, 21 Jun 2018 22:07:50 +0100 Brian Potkin wrote: [...] > Thank you for the confirmation that "PreserveJobHistory No" works for > you. This is a win in my book, irrespective of the inticacies involved > in socket activation. You seem happy with the outcome, so let us close > this this report

Bug#899259: cups-daemon: with IdleExitTimeout 60, fails to exit after 60 s of inactivity

On Wed, 20 Jun 2018 15:33:20 +0100 Brian Potkin wrote: [...] > Looking at the debug2 error log lead me to putting > > PreserveJobHistory No > > in cupsd.conf. This gives reliable and consistent socket activation > and timing out. How about for you? Thanks for the suggestion. Now I am trying

Bug#899259: cups-daemon: with IdleExitTimeout 60, fails to exit after 60 s of inactivity

On Wed 20 Jun 2018 at 00:31:19 +0200, Francesco Poli wrote: > On Tue, 19 Jun 2018 14:25:07 +0100 Brian Potkin wrote: > > [...] > > A temporary workaround is to run: > > > > cupsctl Browsing=No > > > > to restore the CUPS default setting. > > > > How do you go on with that, Francesco?

Bug#899259: cups-daemon: with IdleExitTimeout 60, fails to exit after 60 s of inactivity

On Wed 20 Jun 2018 at 00:31:19 +0200, Francesco Poli wrote: > On Tue, 19 Jun 2018 14:25:07 +0100 Brian Potkin wrote: > > [...] > > A temporary workaround is to run: > > > > cupsctl Browsing=No > > > > to restore the CUPS default setting. > > > > How do you go on with that, Francesco?

Bug#899259: cups-daemon: with IdleExitTimeout 60, fails to exit after 60 s of inactivity

On Tue, 19 Jun 2018 14:25:07 +0100 Brian Potkin wrote: [...] > A temporary workaround is to run: > > cupsctl Browsing=No > > to restore the CUPS default setting. > > How do you go on with that, Francesco? I can try, but I already have: $ grep Browsing /etc/cups/cupsd.conf

Bug#899259: cups-daemon: with IdleExitTimeout 60, fails to exit after 60 s of inactivity

Quouting from https://github.com/apple/cups/issues/5319: OK, near as I can guess the issue is that Browsing (sharing) is enable by default in Debian (sigh...) which means that the idle exit timeout will not kick in as soon as there is a print queue (== hey we are doing printer sharing),

Bug#899259: cups-daemon: with IdleExitTimeout 60, fails to exit after 60 s of inactivity

On Fri, 25 May 2018 23:42:09 +0100 Brian Potkin wrote: [...] > I have reported this bug upstream. Thanks a lot! -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01

Bug#899259: cups-daemon: with IdleExitTimeout 60, fails to exit after 60 s of inactivity

tags 899259 upstream forwarded 899259 https://github.com/apple/cups/issues/5319 thanks On Fri 25 May 2018 at 23:38:44 +0200, Francesco Poli wrote: > On Fri, 25 May 2018 20:56:18 +0100 Brian Potkin wrote: > > [...] > > Did using socket activation on stretch ever work for you when printing? >

Bug#899259: cups-daemon: with IdleExitTimeout 60, fails to exit after 60 s of inactivity

On Fri, 25 May 2018 20:56:18 +0100 Brian Potkin wrote: [...] > Did using socket activation on stretch ever work for you when printing? Well, as I said in , socket activation used to work in versions up to cups-daemon/2.2.6-5, if I recall correctly... --

Bug#899259: cups-daemon: with IdleExitTimeout 60, fails to exit after 60 s of inactivity

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, 2018-05-25 at 19:23 +0100, Brian Potkin wrote: > Yves-Alexis Perez (cc'ed) has an interest in socket activation working. I > wonder whether he observes the behaviour described in b) when printing? > Yves-Alexis? Hi, it's been a while since

Bug#899259: cups-daemon: with IdleExitTimeout 60, fails to exit after 60 s of inactivity

On Fri 25 May 2018 at 21:23:13 +0200, Francesco Poli wrote: > On Fri, 25 May 2018 19:23:20 +0100 Brian Potkin wrote: > > > 3. No IdleExitTimeout in cupsd.conf. The default is 60 seconds. > > I have instead: > > $ grep IdleExit /etc/cups/cupsd.conf > IdleExitTimeout 60 > > I can try

Bug#899259: cups-daemon: with IdleExitTimeout 60, fails to exit after 60 s of inactivity

On Fri, 25 May 2018 19:23:20 +0100 Brian Potkin wrote: > On Mon 21 May 2018 at 21:53:38 +0200, Francesco Poli (wintermute) wrote: > > > Dear Debian Printing Team, > > this bug report is a sort of "sequel" of #894762... [...] > > Why does cupsd fail to exit? > > What's wrong? > > > > Please help

Bug#899259: cups-daemon: with IdleExitTimeout 60, fails to exit after 60 s of inactivity

On Mon 21 May 2018 at 21:53:38 +0200, Francesco Poli (wintermute) wrote: > Dear Debian Printing Team, > this bug report is a sort of "sequel" of #894762... > > After some preliminary tests, I concluded that socket activation > was working again. > > Well, I was wrong! :-( > > After some

Bug#899259: cups-daemon: with IdleExitTimeout 60, fails to exit after 60 s of inactivity

Package: cups-daemon Version: 2.2.7-5 Severity: normal Dear Debian Printing Team, this bug report is a sort of "sequel" of #894762... After some preliminary tests, I concluded that socket activation was working again. Well, I was wrong! :-( After some further testing, I found out the