Bug#766334: BrowseAllow all gets into cups-browsed.conf by default resulting in no remote printers

2014-10-31 Thread Michal Hocko
On Thu, Oct 30, 2014 at 08:29:42AM +0100, Didier 'OdyX' Raboud wrote: > Hi Michal, and thanks for your bugreport, > > I think I understand the problem you're having, let's see. > > Le mercredi, 22 octobre 2014, 13.12:51 Michal Hocko a écrit : > > (..) > > Of course I had > > BrowseAllow all > >

Bug#766334: BrowseAllow all gets into cups-browsed.conf by default resulting in no remote printers

2014-10-31 Thread Michal Hocko
On Thu, Oct 30, 2014 at 06:40:00PM +0100, Didier 'OdyX' Raboud wrote: > Control: tags -1 +pending +patch > > Le jeudi, 30 octobre 2014, 12.13:09 Tim Waugh a écrit : > > On Thu, 2014-10-30 at 11:10 +0100, Till Kamppeter wrote: > > > The "Browse..." directive implementation was done by Tim Waugh as

Bug#760476: concerning 760476

2014-10-31 Thread Nikos Mavrogiannopoulos
Hi, I've thought of an alternative path that doesn't require changes into applications that close all descriptors but uses some heuristics to check whether the descriptor is still open (and the same type). If that looks reasonable I plan to include it in the next release of gnutls. https://www.gi

Bug#758626: cups-browsed: uses a lot of CPU on a busy network

2014-10-31 Thread Till Kamppeter
I by myself have never tested cups-browsed with that many printers or otherwise very noisy networks. It is also the first time that someone reports that cups-browsed takes a lot of CPU. cups-browsed is running an event loop and if an event (= broadcast signal from local avahi-daemon or from remote

Bug#712512: simple test case

2014-10-31 Thread ael
A small update. I have just written two extremely simple postscript files: simple1.ps:- 100 100 moveto 200 200 lineto stroke showpage and simple2.ps:- 350 050 moveto 050 350 lineto stroke showpage If I print them in sequence, the bug shows up:- lpr simple1.ps (prints correctly) l

Bug#712512: Ghostscript seems to be working

2014-10-31 Thread ael
Following from my previous message, # cat simple1.pcl >/dev/usb/lp0 # cat simple2.pcl >/dev/usb/lp0 works. The second file simple2.pcl is printed correctly. So presumably this suggests that it is a cups problem? A quick look at the foomatic ppd file didn't show anything obviously wrong to the

Bug#712512: Ghostscript seems to be working

2014-10-31 Thread Till Kamppeter
Your problem seems to be a bad interference between your printer and the USB CUPS backend. Please follow the instructions of the section USB printer does not print or prints garbage on https://wiki.ubuntu.com/DebuggingPrintingProblems Till -- To UNSUBSCRIBE, email to debian-printing-requ.