Bug 576370

Summary: several driver margins don't specify units
Product: [Fedora] Fedora Reporter: Tom Horsley <horsley1953>
Component: foomatic-dbAssignee: Tim Waugh <twaugh>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 13CC: jpopelka, twaugh
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: foomatic-db-4.0-13.20100204.fc13 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-04-09 04:06:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
poorly aligned test output
none
much better alignment with the hl1250 driver none

Description Tom Horsley 2010-03-23 21:58:45 UTC
Description of problem:

Complicated printer story I'll try to get right by consulting yum.log:

I did updates on my fedora 13 partition (installed from DVD), and I got this:

Mar 21 19:16:04 Updated: system-config-printer-1.2.0-1.fc13.x86_64

I decided to check and see if it could print, so I opened s-c-p and
there was no printer defined. I went through the manual add printer
process, and it picked one of the cups gutenprint hl-2060 drivers (the
simplified one I think). That driver didn't work (same story as is
documented in bug 531370). I then installed foomatic:

Mar 21 19:31:57 Installed: foomatic-db-4.0-10.20100204.fc13.noarch
Mar 21 19:31:59 Installed: foomatic-4.0.4-1.fc13.x86_64

Manually picking foomatic/hl1250 worked at that point.

Today I got a new update:

Mar 23 17:30:04 Updated: system-config-printer-1.2.0-4.fc13.x86_64

I deleted the previously installed system, rebooted, and opened
s-c-p again. This time it had automatically installed the printer
(because of new s-c-p or becaue I had foomatic installed this time?)

It picked the foomatic/hpijs-pcl5e driver. This driver can indeed print,
but it appears to expand the printout to be about an inch larger than
8.5x11 so that "Printer Test Page" gets cut off at the top and bottom.

Once again, I manually changed the driver to the hl1250 one, and that
works fine. I'll attach scans of the two test prints.


Version-Release number of selected component (if applicable):
system-config-printer-1.2.0-4.fc13.x86_64
cups-1.4.2-34.fc13.x86_64
cups-libs-1.4.2-34.fc13.i686

How reproducible:
100%

Steps to Reproduce:
1.see above
2.
3.
  
Actual results:
rotten alignment with default driver

Expected results:
good alignment with default driver

Additional info:

Comment 1 Tom Horsley 2010-03-23 22:11:33 UTC
Created attachment 402156 [details]
poorly aligned test output

Comment 2 Tom Horsley 2010-03-23 22:12:34 UTC
Created attachment 402157 [details]
much better alignment with the hl1250 driver

Comment 3 Tim Waugh 2010-03-24 18:15:29 UTC
(In reply to comment #0)
> I decided to check and see if it could print, so I opened s-c-p and
> there was no printer defined.

This is the first problem -- it should have added a queue automatically.  I can't really think why it wouldn't have done this, but /var/log/messages might give some indication.  Later on you say that this did work another time, so perhaps it's some sort of intermittent problem.

> I went through the manual add printer
> process, and it picked one of the cups gutenprint hl-2060 drivers (the
> simplified one I think). That driver didn't work (same story as is
> documented in bug 531370). I then installed foomatic:

This is the second problem -- it should have prompted you to install foomatic automatically.

Are you running KDE by any chance?

> It picked the foomatic/hpijs-pcl5e driver. This driver can indeed print,
> but it appears to expand the printout to be about an inch larger than
> 8.5x11 so that "Printer Test Page" gets cut off at the top and bottom.

So this is the third problem, that the pcl5e driver is giving you bad output.  We need to try to determine whether that's a generic problem with the driver, or whether it only happens with your printer model.

A possible fourth problem is that the pcl5e driver is recommended instead of hl1250.  I'll have to check the foomatic-db commit logs to see when/why this changed.

Comment 4 Tom Horsley 2010-03-24 18:37:52 UTC
>This is the first problem -- it should have added a queue automatically.  I
>can't really think why it wouldn't have done this, but /var/log/messages might
>give some indication.  Later on you say that this did work another time, so
>perhaps it's some sort of intermittent problem.

The printer was attached when I initially installed f13 from the dvd, so
maybe someone decided it couldn't work at that time and saved that info
somewhere? Or maybe it is one of the few customizations I have done on
f13 so far - turned off the avahi-daemon service (I actually hate things
that happen automatically, so this issue doesn't bother me much :-). I do
see a slew of avahi errors in the cups/error_log. The only thing I see
in /var/log/messages is the normal registering of the usb printer every
time I boot. 

When it did install automatically, it was after I had manually installed
foomatic then deleted the existing printer def.

>This is the second problem -- it should have prompted you to install foomatic
>automatically.
>
>Are you running KDE by any chance?

Nope, standard gnome session with new user on new /home created when I
installed.

Comment 5 Tom Horsley 2010-03-24 18:41:57 UTC
>So this is the third problem, that the pcl5e driver is giving you bad output. 
>We need to try to determine whether that's a generic problem with the driver,
>or whether it only happens with your printer model.

I just noticed in the test outputs I attached, that the "media limits"
for the pcl5e driver seem to imply that the entire page is printable
from edge to edge, and that is certainly not true. The hl1250 test page
shows much more reasonable media limits for this printer.

Comment 6 Tim Waugh 2010-03-25 08:52:37 UTC
Oh, well spotted, that's exactly the problem.

It is because the foomatic driver/hpijs-pcl5e.xml file has this:

    <margins>
      <general>
        <relative />
        <top>0.2</top>
        <left>0.25</left>
        <right>0.25</right>
        <bottom>0.2</bottom>
      </general>
    </margins>

but it should look like this:

    <margins>
      <general>
        <unit>in</unit>
        <relative />
        <top>0.2</top>
        <left>0.25</left>
        <right>0.25</right>
        <bottom>0.2</bottom>
      </general>
    </margins>

I wonder if there are any other drivers like that.

Comment 7 Tim Waugh 2010-03-25 10:50:37 UTC
This was already fixed upstream.  Here's the upstream change:

2010-03-10  OpenPrinting Web Server <webmaster>

        * db/source/driver/chp2200.xml,
          db/source/driver/hpijs-pcl3.xml,
          db/source/driver/hpijs-pcl5c.xml,
          db/source/driver/hpijs-pcl5e.xml,
          db/source/driver/hplip.xml,
          db/source/driver/min12xxw.xml,
          db/source/driver/oki4w.xml,
          db/source/printer/HP-Color_LaserJet_1500.xml,
          db/source/printer/HP-Color_LaserJet_1600.xml,
          db/source/printer/HP-Color_LaserJet_2600n.xml,
          db/source/printer/HP-Color_LaserJet_CP1215.xml,
          db/source/printer/Kyocera-KM-1635.xml,
          db/source/printer/Kyocera-KM-2035.xml:
          The MySQL database on the OpenPrinting web server could not hold
          "<unit>in</unit>" in margin definitions. Fixed the MySQL database
          and exported the corrected entries.

Comment 8 Tim Waugh 2010-03-25 11:11:55 UTC
F-12 not affected.

Comment 9 Tim Waugh 2010-03-25 11:28:46 UTC
I've built foomatic-db-4.0-12.20100204.fc13 with this fix.  Could you try it out please?  You'll need to create the queue again after updating the package.

Comment 10 Tom Horsley 2010-03-25 12:14:36 UTC
Where would I find this new foomatic? Is it in updates-testing, or over
on the build system I never remember how to use? :-). Won't be able to
try it till this evening (EDT) when I can reboot back to f13 at home.

Comment 11 Tim Waugh 2010-03-25 12:33:10 UTC
:-)  Sorry, it's here:

http://koji.fedoraproject.org/koji/buildinfo?buildID=163652

Comment 12 Tom Horsley 2010-03-25 21:02:02 UTC
This new foomatic definitely seems to work. I reinstalled the printer and
it picked hpijs-pcl5e, and this time the test page printed perfectly. It
even looks better than the hl1250 - the pcl5e prints the outer black border
closer to the edge of the paper, so the media limits (now that the units
are accurate :-) seem to be more correct for my HL-2040 with the recommended
driver.

Comment 13 Fedora Update System 2010-03-26 18:30:54 UTC
foomatic-db-4.0-13.20100204.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/foomatic-db-4.0-13.20100204.fc13

Comment 14 Fedora Update System 2010-04-01 19:32:43 UTC
foomatic-db-4.0-13.20100204.fc13 has been pushed to the Fedora 13 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update foomatic-db'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/foomatic-db-4.0-13.20100204.fc13

Comment 15 Fedora Update System 2010-04-09 04:06:29 UTC
foomatic-db-4.0-13.20100204.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.