Bug#867818: No printer listed in some applications when no default printer is set

2017-07-10 Thread Didier 'OdyX' Raboud
Control: tags -1 +patch +pending

Le lundi, 10 juillet 2017, 09.28:00 h CEST Viktor Jägersküpper a écrit :
> Brian Potkin:
> > On Sun 09 Jul 2017 at 17:41:00 +, Viktor Jägersküpper wrote:
> >> The bug is already fixed upstream.
> > 
> > Reference, please.
> 
> https://github.com/apple/cups/commit/
b2f85109da901eb652babdc4f2a846c1c28228ff

Ah, great, thank you for the reference! Will include in the next upload!

Cheers,
OdyX



Bug#867818: No printer listed in some applications when no default printer is set

2017-07-10 Thread Viktor Jägersküpper
Brian Potkin:
> On Sun 09 Jul 2017 at 17:41:00 +, Viktor Jägersküpper wrote:
> 
>> The bug is already fixed upstream.
> 
> Reference, please.
https://github.com/apple/cups/commit/b2f85109da901eb652babdc4f2a846c1c28228ff



Bug#867818: No printer listed in some applications when no default printer is set

2017-07-09 Thread Brian Potkin
On Sun 09 Jul 2017 at 17:41:00 +, Viktor Jägersküpper wrote:

> CUPS 2.2.4-1 introduces a regression when no printer is set as default.
> In this case some applications will not list any printer at all, e.g.
> any Libreoffice application or the GNOME control center. A workaround is
> to set a printer as the default one, e.g. via the CUPS web interface.
> 
> The bug is already fixed upstream.

Reference, please.

Regards,

Brian.



Bug#867818: No printer listed in some applications when no default printer is set

2017-07-09 Thread Viktor Jägersküpper
Package: cups
Version: 2.2.4-1
Severity: normal
Forwarded: https://github.com/apple/cups/issues/5046
Tags: upstream
Tags: fixed-upstream
Control: affects -1 src:libreoffice
Control: affects -1 gnome-control-center

Dear Maintainer,

CUPS 2.2.4-1 introduces a regression when no printer is set as default.
In this case some applications will not list any printer at all, e.g.
any Libreoffice application or the GNOME control center. A workaround is
to set a printer as the default one, e.g. via the CUPS web interface.

The bug is already fixed upstream.

Regards,
Viktor