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 also during shutdown, it accesses localhost:631 (this is why it > hangs on shutdown), independent of configuration.
I had noticed some asymmetry between startup and shutdown. > Now I have fixed this in the upstream BZR repository. if you are familiar > with compiling stuff by yourself and with BZR, load a current BZR snapshot, > build it, and put its cups-browsed into /usr/sbin/, replacing the distro's > one. Then check whether it solves the problem. I'm as familiar with BZR as I am with Swiss train timetables. Designing and building nuclear power stations seems a lot easier to me. :) > Do the following commands (relevant source code file is utils/cups-browsed.c > FYI): > > sudo apt-get build-dep cups-filters > sudo apt-get install bzr > bzr branch http://bzr.linuxfoundation.org/openprinting/cups-filters ./autogen.sh was necessary here. The INSTALL file helped. > cd cups-filters > ./configure > make > sudo systemctl stop cups-browsed > sudo cp cups-browsed /usr/sbin/ > sudo systemctl start cups-browsed I end up with a cups-browsed file with size 370820 in the root of cups-filters. > Now it should run purely on the domain socket. If not (then it probably runs > purely on localhost:631) add the line > > DomainSocket /var/run/cups/cups.sock > > to /etc/cups/cups-browsed.conf and restart cups-browsed. > > Does the shutdown now work correctly? Yes, it does. That's with cups 2.2~rc1-5. Thank you for your timely response and the fix (and the detailed instructions). Cheers, Brian.
