On Tue, Feb 25, 2014 at 03:28:37PM +0100, Didier Raboud wrote:
>
> Le vendredi, 26 avril 2013, 13.08:22 Alberto Gonzalez Iniesta a écrit :
> > I'm also experiencing this problem when my print clients were upgraded
> > from Ubuntu 10.04 to 12.04 [1]. The CUPS server [2] runs Debian
> > Squeeze.
>
* Brian Potkin [2014-02-27 16:22:57 +]:
> It was remiss of me not to have pushed the initial report of the bug
> upstream, but the str database was offline and I also had got it into my
> head that upstream was not considering any further changes to 1.5.3. If
> it is thought appropriate I could
On Tue 25 Feb 2014 at 15:28:37 +0100, Didier Raboud wrote:
> Le vendredi, 26 avril 2013, 13.08:22 Alberto Gonzalez Iniesta a écrit :
> > I'm also experiencing this problem when my print clients were upgraded
> > from Ubuntu 10.04 to 12.04 [1]. The CUPS server [2] runs Debian
> > Squeeze.
>
> Albe
* Didier Raboud [2014-02-25 15:28:37 +0100]:
> Control: tags -1 +moreinfo
>
> Le vendredi, 26 avril 2013, 13.08:22 Alberto Gonzalez Iniesta a écrit :
> > I'm also experiencing this problem when my print clients were upgraded
> > from Ubuntu 10.04 to 12.04 [1]. The CUPS server [2] runs Debian
> > S
On Tue, Feb 25, 2014 at 03:28:37PM +0100, Didier Raboud wrote:
> Control: tags -1 +moreinfo
>
> Le vendredi, 26 avril 2013, 13.08:22 Alberto Gonzalez Iniesta a écrit :
> > I'm also experiencing this problem when my print clients were upgraded
> > from Ubuntu 10.04 to 12.04 [1]. The CUPS server [2]
Control: tags -1 +moreinfo
Le vendredi, 26 avril 2013, 13.08:22 Alberto Gonzalez Iniesta a écrit :
> I'm also experiencing this problem when my print clients were upgraded
> from Ubuntu 10.04 to 12.04 [1]. The CUPS server [2] runs Debian
> Squeeze.
Alberto, Sergio: is this problem still present w
On Thu 21 Mar 2013 at 08:33:13 +0100, Sergio Gelato wrote:
> * Brian Potkin [2013-03-20 22:23:10 +]:
> > So, Sergio, which one one of us is going to report this upstream? You or
> > I?
>
> Not me, since I don't think I've established that it is an upstream bug.
> It seems proper to let the De
* Brian Potkin [2013-03-20 22:23:10 +]:
> So, Sergio, which one one of us is going to report this upstream? You or
> I?
Not me, since I don't think I've established that it is an upstream bug.
It seems proper to let the Debian package maintainers push reports upstream
as they see fit.
--
To
On Mon 08 Oct 2012 at 21:47:46 +0200, Sergio Gelato wrote:
> I've created a print queue with an
> AllowUser user1
> option. When submitting a print job as user1 all goes as expected, but
> if I submit it as some other user I see a flood of error messages appear
> (observed rates: 375-500 H
Thank you for your report, Sergio.
> Package: cups
> Version: 1.5.3-1
> Severity: important
> Tags: security
>
> I've created a print queue with an
> AllowUser user1
> option. When submitting a print job as user1 all goes as expected, but
> if I submit it as some other user I see a flood of
Package: cups
Version: 1.5.3-1
Severity: important
Tags: security
I've created a print queue with an
AllowUser user1
option. When submitting a print job as user1 all goes as expected, but
if I submit it as some other user I see a flood of error messages appear
(observed rates: 375-500 Hz,
11 matches
Mail list logo
