On Wed 19 Jul 2017 at 01:59:55 +, brian m. carlson wrote:
> At this point, I don't have access to the printer anymore, so I can't
> test any further. I think your change probably doesn't make things
> worse for people with that printer, so I'd suggest closing this bug
> report at this point.
On Mon, Jul 17, 2017 at 11:19:39PM -0300, Till Kamppeter wrote:
> This is all very strange.
>
> What do you get if you run the command
>
> driverless
>
> This should make the printer's IPP URI appear. Now run
>
> driverless [IPP URI] > out.ppd
>
> with [IPP URI] replaced by the printer's IPP U
This is all very strange.
What do you get if you run the command
driverless
This should make the printer's IPP URI appear. Now run
driverless [IPP URI] > out.ppd
with [IPP URI] replaced by the printer's IPP URI, the output of the
first command.
out.ppd then is a valid and working PPD for y
On Mon, Jul 17, 2017 at 09:09:09PM -0300, Till Kamppeter wrote:
> On 07/17/2017 08:34 PM, brian m. carlson wrote:
> >
> > It does not appear to fix the problem. The PPD that's generated is
> > identical and still contains the 600x2 resolution. I will lose access
> > to the printer tomorrow, unfo
On 07/17/2017 08:34 PM, brian m. carlson wrote:
It does not appear to fix the problem. The PPD that's generated is
identical and still contains the 600x2 resolution. I will lose access
to the printer tomorrow, unfortunately, so I'll be unable to test
further.
The actual change takes place i
On Mon, Jul 17, 2017 at 03:08:09PM -0300, Till Kamppeter wrote:
> I have now added a fallback mechanism to the PPD generator in cups-filters
> which does not accept resolutions < 75 dpi.
>
> It is committed (rev. 7652) to the upstream BZR repository. Please test.
It does not appear to fix the pro
I have now added a fallback mechanism to the PPD generator in
cups-filters which does not accept resolutions < 75 dpi.
It is committed (rev. 7652) to the upstream BZR repository. Please test.
Till
On Sun 16 Jul 2017 at 19:42:21 +, brian m. carlson wrote:
> retitle 868360 cups-filters-core-drivers: recommends non-functional
> driverless operation
> kthxbye
>
> On Sun, Jul 16, 2017 at 05:17:14PM +0100, Brian Potkin wrote:
> > On Sun 16 Jul 2017 at 14:38:44 +, brian m. carlson wrote:
retitle 868360 cups-filters-core-drivers: recommends non-functional driverless
operation
kthxbye
On Sun, Jul 16, 2017 at 05:17:14PM +0100, Brian Potkin wrote:
> On Sun 16 Jul 2017 at 14:38:44 +, brian m. carlson wrote:
> > The printer resolution is indeed returned in an IPP query, as you'll s
On Sun 16 Jul 2017 at 14:38:44 +, brian m. carlson wrote:
> On Sun, Jul 16, 2017 at 12:34:05AM +0100, Brian Potkin wrote:
> > On Sat 15 Jul 2017 at 19:40:04 +, brian m. carlson wrote:
> > > * Validate data. Nobody is going to print a two-pixel raster image, and
> > > cups should not acc
On Sun, Jul 16, 2017 at 12:34:05AM +0100, Brian Potkin wrote:
> On Sat 15 Jul 2017 at 19:40:04 +, brian m. carlson wrote:
> > * Validate data. Nobody is going to print a two-pixel raster image, and
> > cups should not accept it as a valid (and in this case, the only
> > valid) option.
>
>
On Sat 15 Jul 2017 at 19:40:04 +, brian m. carlson wrote:
> On Sat, Jul 15, 2017 at 08:16:19PM +0100, Brian Potkin wrote:
> > On Fri 14 Jul 2017 at 22:48:32 +, brian m. carlson wrote:
> >
> > > This does fix the problem. Since this printer supports PCL, I can also
> > > use the hpijs-pcl
On Sat, Jul 15, 2017 at 08:16:19PM +0100, Brian Potkin wrote:
> On Fri 14 Jul 2017 at 22:48:32 +, brian m. carlson wrote:
>
> > This does fix the problem. Since this printer supports PCL, I can also
> > use the hpijs-pcl5c driver in the mean time.
>
> Is this a bug in Brother's printer? It l
On Fri 14 Jul 2017 at 22:48:32 +, brian m. carlson wrote:
> On Fri, Jul 14, 2017 at 06:42:34PM -0300, Till Kamppeter wrote:
> >
> > Replace
> >
> > --
> > *DefaultResolution: 600x2dpi
> > *OpenUI *cupsPrintQuality/Print Quality: PickOne
> > *OrderDependency: 10 AnySetup *cupsPrintQua
On Fri, Jul 14, 2017 at 06:42:34PM -0300, Till Kamppeter wrote:
> It seems that the printer answers the wrong resolution (firmware bug). Under
> the printer's attributes I have found:
>
> > DEBUG2: Attr: pwg-raster-document-resolution-supported
> > DEBUG2: Value: 600x2dpi
I have just updated the
It seems that the printer answers the wrong resolution (firmware bug).
Under the printer's attributes I have found:
DEBUG2: Attr: pwg-raster-document-resolution-supported
DEBUG2: Value: 600x2dpi
Please run the following command:
ipptool -tv ipp://copper.local:631/ipp/print get-printer-attrib
Package: cups-filters-core-drivers
Version: 1.14.1-1
Severity: normal
I have a Brother MFC-9340CDW printer on the local LAN. When using the
driverless configuration, the resolution is set to 600x2 dpi, resulting
in the printer printing literally two lines on the page. The resolution
of the print
17 matches
Mail list logo
