bilyoFirst can you slip back into your reply #5 and just move the full stop at the end of the links outside the html tags. It is important references you have given there and I think it will catch many unaware and seem to indicate dead site.
When you report output from konsole use the code tags, ie the # key icon above the edit window, another item to make sure readability is better. Also make sure to include the promptline, ie copy and paste enough from console as shown below:
I will remove this later when you have edited your previous post, sorry I am just trying to make sure that the thread will get people in and keep them reading.

[root@localhost gert]$ lpstat -t < -------------------------- include this line, sometimes give valuable information to user mode without having to ask question
scheduler is running
system default destination: HPPPrem309gm
device for EPSONSPR1800: usb://EPSON/Stylus%20Photo%20R1800
device for HPPP309gmhpi: hp:/net/Photosmart_Premium_C309g-m?ip=192.168.2.100
device for HPPPrem309gm: hp:/net/Photosmart_Premium_C309g-m?ip=192.168.2.100
EPSONSPR1800 accepting requests since Mon 03 May 2010 07:44:25 PM CDT
HPPP309gmhpi accepting requests since Fri 08 Oct 2010 07:13:26 PM CDT
HPPPrem309gm accepting requests since Fri 08 Oct 2010 02:24:22 PM CDT
printer EPSONSPR1800 is idle. enabled since Mon 03 May 2010 07:44:25 PM CDT
printer HPPP309gmhpi is idle. enabled since Fri 08 Oct 2010 07:13:26 PM CDT
printer HPPPrem309gm is idle. enabled since Fri 08 Oct 2010 02:24:22 PM CDT
HPPP309gmhpi-139 root 21504 Fri 08 Oct 2010 02:13:29 PM CDT
HPPP309gmhpi-141 bill 3999744 Fri 08 Oct 2010 07:13:26 PM CDT
[root@localhost gert]$ < ---------------------- include this line to indicate it really is the end
I will pick up where you installed the ppd file. It may pay that you set up your own
personal directory for keeping your special ppd files, you might get curious and experiment a lot and dig out your own.
The file I sent you was or we will call it an
original ppd file, this is used to generate another ppd file you can call the
print que ppd file, this links with the total printing path for the particular printer you have set up. When you use a
CUPS ppd install, that special file will be given your
printer name and all CUPS ppd print install are kept:
/etc/cups/ppd/xxxx.ppdYou have just added
HPPP309gmhpi.ppd to this directory (and the original file), well I have done a bit of guessing here but if you check your directory you will figure it out.
It is of course up to you, if you can manage to remember that you may have two sets of different files in this directory, leave it at that. There is a correct place for the original files but it got too difficult for me to try and keep up with that.
1.. Correct to ignore the ppd check I believe, most ppd files fails this check. The check procedure was tightened up some time ago but with thousands of files to test I think this was just left. If one has trouble with a file it is worth remembering that perhaps the file could be a problem. I don't know at present if this will be a problem or where it may show. I have checked a number of ppds that I use and all failed but seem to work fine.
2.. Because I have bypassed the big hp installation database, which was problem for me, I have to make a change inside the ppd. Your line number seems to high, I will investigate, but somewhere the
-hplip has to go.
Edit:Ouch, something has changed again. Some database re-write which I should have remembered. In theory should not matter but CUPS foomatic-rip is an ordinary exe file. Foomatic-rip-hplip is a Perl Script doing the same job I hope. This all belongs to a CUPS/Foomatic upgrade as I understand.
In this file
HPPP309gmhpi.ppd if I have picked the right one, make below change and see what happens.
Lines 234/235 approximately:
*cupsFilter: "application/vnd.cups-postscript 100 foomatic-rip-hplip"
*cupsFilter: "application/vnd.cups-pdf 0 foomatic-rip-hplip"
Change to this
*% Following is Bill's special attempting to fix duplex
*%cupsFilter: "application/vnd.cups-postscript 100 foomatic-rip-hplip"
*%cupsFilter: "application/vnd.cups-pdf 0 foomatic-rip-hplip"
*cupsFilter: "application/vnd.cups-postscript 100 foomatic-rip"
*cupsFilter: "application/vnd.cups-pdf 0 foomatic-rip"
Edit2:I have no problem reproducing your error here despite not having your printer model, looking into the validity of above change in ppd.
Edit3:I should have edited my original file, as described above, truncating the foomatic-rip-hplip string, but I will wait until you confirm that at least the error disappears in the printer management. I edited the file and saved it again. You will need root access to do that.
Hmmm, I just looked in Gnome, did not have a file editor that I recognise. Sorry I keep forgetting you use Gnome, you are on your own
I edited the proper que ppd in my
etc/cups/ppd/ directory.
When you have done that then in a su konsole, do
[root@localhost gert]$ service cups restart < ---- just these three words, the response is what my system gave
Stopping CUPS printing system: [ OK ]
Starting CUPS printing system: [ OK ]
Re-enabling disabled print queues:
[root@localhost gert]$
If you look in your CUPS management for the offending printer the error should be gone.
If it will print properly that is the interesting question.