Bug#832637: More info

2016-09-03 Thread Till Kamppeter
On 09/03/2016 07:42 PM, Brian Potkin wrote: # DomainSocket /var/run/cups/cups.sock Thank you. As this line is commented out cups-browsed connects by the socket out-of-the-box on your machine. Till

Bug#832637: More info

2016-09-03 Thread Brian Potkin
On Sat 03 Sep 2016 at 19:17:48 -0300, Till Kamppeter wrote: > Brian, thank you very much for the testing. I will do the next (bug fix) > release containing also other fixes (version 1.11.3) most probably on > Monday. > > One question: Did cups-browsed use the socket out-of-the-box or did you

Bug#832637: More info

2016-09-03 Thread Till Kamppeter
Brian, thank you very much for the testing. I will do the next (bug fix) release containing also other fixes (version 1.11.3) most probably on Monday. One question: Did cups-browsed use the socket out-of-the-box or did you need to set it in cups-browsed.conf? Till

Bug#832637: More info

2016-09-03 Thread Brian Potkin
On Sat 03 Sep 2016 at 14:12:52 -0300, Till Kamppeter wrote: > The problem is most probably caused by inconsistency in how cups-browsed > accesses the local CUPS daemon, for some accesses it uses the domain socket > (which made it mostly well working in your case) and at other places, > especially

Bug#832637: More info

2016-09-03 Thread Till Kamppeter
The problem is most probably caused by inconsistency in how cups-browsed accesses the local CUPS daemon, for some accesses it uses the domain socket (which made it mostly well working in your case) and at other places, especially also during shutdown, it accesses localhost:631 (this is why it

Bug#832637: More info

2016-09-03 Thread Brian Potkin
On Tue 30 Aug 2016 at 23:31:55 +0200, Roderich Schupp wrote: > On Tue, Aug 23, 2016 at 6:55 PM, Brian Potkin > wrote: > > > I have no special skills in interpreting strace outputs but this would > > appear to be confirmation that cups-browsed cannot contact cups when it

Bug#832637: More info

2016-09-01 Thread Brian Potkin
On Tue 30 Aug 2016 at 23:31:55 +0200, Roderich Schupp wrote: > On Tue, Aug 23, 2016 at 6:55 PM, Brian Potkin > wrote: > > > I have no special skills in interpreting strace outputs but this would > > appear to be confirmation that cups-browsed cannot contact cups when it

Bug#832637: More info

2016-08-30 Thread Roderich Schupp
On Tue, Aug 23, 2016 at 6:55 PM, Brian Potkin wrote: > I have no special skills in interpreting strace outputs but this would > appear to be confirmation that cups-browsed cannot contact cups when it > closes down. > cupsd _is_ running. The strace fragment simply shows

Bug#832637: More info

2016-08-23 Thread Brian Potkin
On Sun 21 Aug 2016 at 17:30:10 +0200, Roderich Schupp wrote: > On Sun, Aug 21, 2016 at 4:27 PM, Brian Potkin > wrote: > > > Are you positive cups.service is still running while cups-browsed is > > stopping? 'systemctl status cups' in another terminal would tell you. > >

Bug#832637: More info

2016-08-21 Thread Roderich Schupp
On Sun, Aug 21, 2016 at 4:27 PM, Brian Potkin wrote: > Are you positive cups.service is still running while cups-browsed is > stopping? 'systemctl status cups' in another terminal would tell you. > Yes > If I use the sequence > > systemctl start cups

Bug#832637: More info

2016-08-21 Thread Roderich Schupp
I have the same problem as Heinrich Schuchardt (same version of cups-browsed, but cups-daemon 2.2~rc1-4 from experimental). $ sudo systemctl stop cups-browsed.service takes 90 seconds (while avahi-daemon.service and cups.service are still running). journalctl shows Aug 21 14:38:52 macarthur