Red Hat Bugzilla – Bug 99069
libgnomeprint doesn't see all printers
Last modified: 2007-04-18 12:55:38 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20030131
Description of problem:
I have three printers. One is a HP Laser Jet 6MP. I use CUPS on my system and
the driver is a plain postscript one. In 1.9.1 of Abiword, my printer doesn't
show up. The other two do. There is a generic postscript printer option, but
that won't print to the printer either.
My system is a half RedHat 9.0/half RedHat Rawhide. All of the relevant
drivers, libraries, and Abiword are from Rawhide.
This may be a CUPS bug, but I don't think so. I will be reporting this to
RedHat as well hoping it will get fixed.
See bug 3045 in Abiword Rawhide. Again, I am not sure this is Abiword or cups
or something else.
Version-Release number of selected component (if applicable):
1.9.1 from rawhide
Steps to Reproduce:
Unsure, my other printers are Epson C80, and Epson Color Stylus 850.
I guess install all three printer drivers, and try to print a file from Abiword
Actual Results: Abiword doesn't show the HPLJ6MP in the list (that is the name
I gave it, btw.)
Expected Results: It should show up.
There are VERY few files that are still RH9, the rest are Rawhide.
That is 3042 bug in Abiword's bugzilla, not in Abiword rawhide. Sorry, a little
puncy I guess. The 3045 was a typo.
This happens with any app using libgnomeprint (seen with gedit and evolution as
Yes, I hadn't noticed that (I never print from gedit and rarely do from evolution.)
Anyone have any clues yet what happens? Is this an off by one, or is this a hey
its postscript, ignore it?
libgnomeprint won't list any cups printers for which it can't get the
This seems reasonable to me, though I suppose it could fall back to
assumming "generic postscript" in some fashion. But it seems to me
that that should be the responsibility of CUPS.
Throwing this over to Tim Waugh for evaluation of why some printers
wouldn't get a response from cupsGetPPD(), and if anything can be
done about it.
BTW, you should be able to add a PPD file for your printer
lpadmin -pmy_printer -PHP-LaserJet_6MP.ppd
or something close to that.
This is likely to be a wonderful work around. However, this bug seems to have
been fixed in a recent rawhide or beta release. About 2 weeks ago. I have
been meaning to close this, so maybe it is time to close.
Ever since redhat-config-printer was adapted to use CUPS, there should *always*
be a PPD associated with a queue. Otherwise the queue won't work. :-)
So whatever the problem was, the fact that it went away without anything
substantial changing is scary. I would need the output of 'printconf-tui
--Xexport' to find out why a queue isn't getting written out properly I think.
Also, 'printconf-backend --force-rebuild' will force the configuration to be
written out again -- if that gives errors they would be useful to see.
I don't know what happened. I can't really remember when this went
away. But it is gone in Fedora Core 1 and in development for FC 2.