Bug#660852: cups: Not possible to print and all status commands give empty output and web frontend do not work

2012-09-09 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Brian, Am So den 9. Sep 2012 um 12:37 schrieb Brian Potkin: > The good news first. Would you please take a look at > >http://www.cups.org/str.php?L4053 Seems to be the same. And I had think of such a bug from begin on. > The bad news is t

Bug#660852: cups: Not possible to print and all status commands give empty output and web frontend do not work

2012-09-09 Thread Brian Potkin
tags 660852 + upstream tags 660852 + moreinfo thanks On Sun 11 Mar 2012 at 14:09:53 +0100, Klaus Ethgen wrote: > Some minutes ago I did release the holds and updated again, now to > 1.5.2-6. Unfortunately with the same result. The following is the > complete output of the command line: > --- >

Bug#660852: cups: Not possible to print and all status commands give empty output and web frontend do not work

2012-03-11 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 NotDashEscaped: You need GnuPG to verify this message Hello, Am Di den 28. Feb 2012 um 20:47 schrieb Brian Potkin: > Today, using CUPS 1.5.2-5, I reviewed the bug you reported and was unable > to reproduce any of the problems you described. The web

Bug#660852: cups: Not possible to print and all status commands give empty output and web frontend do not work

2012-02-28 Thread Brian Potkin
severity 660852 important thanks Hello Klaus, Today, using CUPS 1.5.2-5, I reviewed the bug you reported and was unable to reproduce any of the problems you described. The web interface in particular behaved as it normally does. This was using your cupsd.conf as well as mine. Please would you