Bug 552731

for example with the 8160 Avery labels i have to put to spaces on the left of the furtherest label for it to print right.

*furthest left label

What does 'lpoptions -p queuename' say for that queue?

[brandon@localhost ~]$ lpoptions -p queuename

[brandon@localhost ~]$ 


[brandon@localhost ~]$ lpoptions
auth-info-required=none copies=1 device-uri=hp:/usb/Deskjet_3900?serial=CN572170WF048H finishings=3 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 media=na_letter_8.5x11in number-up=1 printer-commands=none printer-info='HP Deskjet 3900' printer-is-accepting-jobs=true printer-is-shared=true printer-location=localhost.localdomain printer-make-and-model='HP Deskjet 3900, hpcups 3.9.8' printer-state=3 printer-state-change-time=1262801337 printer-state-reasons=none printer-type=167948 printer-uri-supported=ipp://localhost:631/printers/Deskjet-3900
[brandon@localhost ~]$

*the printer is actually a 3940v not a 3940

I meant for you to replace 'queuename' with the name of your queue.  Is 'Deskjet-3900' the queue you are having problems with?

Try using this driver instead:

HP DeskJet 3940 Foomatic/hpijs

You'll have to change the model from 'Deskjet 3900' to 'DeskJet 3940' in order to do that.

I would also like to see the output of 'lpinfo -l -v', run as root (i.e. run 'su -' first), in order to see the device-id field for that device.

Oh, you'll need to run this command first, as root:

yum --enablerepo=updates-testing update foomatic-db

sorry I just copied and pasted I was on auto pilot.... I put for argv[2] as Deskjet-3900 because that is what the printer was listed as....


and i got the following:

[brandon@localhost ~]$ lpoptions -p Deskjet-3900
auth-info-required=none copies=1 device-uri=hp:/usb/Deskjet_3900?serial=CN572170WF048H finishings=3 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 media=na_letter_8.5x11in number-up=1 printer-commands=none printer-info='HP Deskjet 3900' printer-is-accepting-jobs=true printer-is-shared=true printer-location=localhost.localdomain printer-make-and-model='HP Deskjet 3900, hpcups 3.9.8' printer-state=3 printer-state-change-time=1262801243 printer-state-reasons=none printer-type=167948 printer-uri-supported=ipp://localhost:631/printers/Deskjet-3900

[brandon@localhost ~]$ su -c 'yum --enablerepo=updates-testing update foomatic-db'
Password: 
Loaded plugins: presto, refresh-packagekit
Setting up Update Process
Package(s) foomatic-db available, but not installed.
No Packages marked for Update
[brandon@localhost ~]$ 


[brandon@localhost ~]$ su -c 'lpinfo -l -v'
Password: 
Device: uri = lpd
        class = network
        info = LPD/LPR Host or Printer
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = smb
        class = network
        info = Windows Printer via SAMBA
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = serial:/dev/ttyS0?baud=115200
        class = serial
        info = Serial Port #1
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = https
        class = network
        info = Internet Printing Protocol (https)
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = ipp
        class = network
        info = Internet Printing Protocol (ipp)
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = scsi
        class = direct
        info = SCSI Printer
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = usb://HP/Deskjet%203900?serial=CN572170WF048H
        class = direct
        info = HP Deskjet 3900
        make-and-model = HP Deskjet 3900
        device-id = MFG:HP;MDL:Deskjet 3900;CMD:LDL,DYN;CLS:PRINTER;DES:3940;SN:CN572170WF048H;S:0380008000020020002c1480045c2500035;Z:007;
        location = 
Device: uri = http
        class = network
        info = Internet Printing Protocol (http)
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = socket
        class = network
        info = AppSocket/HP JetDirect
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = hp:/usb/Deskjet_3900?serial=CN572170WF048H
        class = direct
        info = HP Deskjet 3900 USB CN572170WF048H HPLIP
        make-and-model = HP Deskjet 3900
        device-id = MFG:HP;MDL:Deskjet 3900;CLS:PRINTER;DES:Deskjet 3900;SN:CN572170WF048H;
        location = 
Device: uri = hpfax
        class = direct
        info = HP Fax (HPLIP)
        make-and-model = Unknown
        device-id = 
        location = 
[brandon@localhost ~]$

1st command did not run would yum install work instead?
2nd command ran did you get what you needed.

[brandon@localhost ~]$ lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 003: ID 046d:c044 Logitech, Inc. LX3 Optical Mouse
Bus 004 Device 002: ID 0a5c:2101 Broadcom Corp. A-Link BlueUsbA2 Bluetooth
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 03f0:7604 Hewlett-Packard DeskJet 3940
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

[brandon@localhost ~]$ yum list installed | grep kernel
abrt-addon-kerneloops.x86_64
abrt-plugin-kerneloopsreporter.x86_64
kernel.x86_64      2.6.31.6-166.fc12
kernel.x86_64      2.6.31.9-174.fc12
kernel-devel.x86_64
kernel-devel.x86_64
kernel-firmware.noarch
kernel-headers.x86_64

(In reply to comment #9)
> [brandon@localhost ~]$ su -c 'yum --enablerepo=updates-testing update
> foomatic-db'
> Password: 
> Loaded plugins: presto, refresh-packagekit
> Setting up Update Process
> Package(s) foomatic-db available, but not installed.
> No Packages marked for Update
> [brandon@localhost ~]$ 

> 1st command did not run would yum install work instead?

Yes, please run this instead:

yum --enablerepo=updates-testing install foomatic-db

> 2nd command ran did you get what you needed.  

Yes thanks -- confirmation that this device identifies itself as model number '3900' in its IEEE 1284 Device ID string.

since you got what you needed to you still need me to install foomatic-db.... what does foomatic-db do?

also please look at lsusb ouput.

Created attachment 382307 [details]
screen shot1

Created attachment 382309 [details]
screen shot2

Created attachment 382310 [details]
Screen shot3\

Created attachment 382311 [details]
Results

(In reply to comment #13)
> since you got what you needed to you still need me to install foomatic-db....

Yes.

Install foomatic-db, then follow the instructions in comment #6.  Here they are again in more detail:

After installing foomatic-db, edit the printer's settings by selecting System->Administration->Printing from the main desktop menu and double-clicking on the icon for the queue.

Click the 'Change...' button which is next to 'Make and Model: ...' to change the driver.

Select 'HP' if it is not already selected, and click Forward.

Select "DeskJet 3940" in the models list, and choose this driver:

HP DeskJet 3940 Foomatic/hpijs

Click Forward and Apply.

Then try printing to that queue again.

Created attachment 382670 [details]
Install of foomatic-db and driver change

Install and change of driver did not fix error.

You're still using the hpcups driver, i.e.:

HP Deskjet 3940, hpcups 3.9.8

Change it to this driver:

HP DeskJet 3940 Foomatic/hpijs

Created attachment 383010 [details]
Foomatic-db driver not showing

foomatic-db driver not showing

Run 'yum install foomatic' as well, then try again.

that command worked for installing the foomatic driver... the driver does a better than cups. but the foomatic driver is still off by about .1 inches which is way better than cups .4 inches....



is there anything else possible to do to improve printing.

Created attachment 394866 [details]
Testpage

Comment to Attachment Testpage:
With the default drivers in Fedora 12 the testpage is shifted. Only after the additional installation of foomatic drivers printing if ok. Example with HP Deskjet 2280.

This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.