Red Hat Bugzilla – Bug 140900
system-config-printer does not install a ppd from file correctly
Last modified: 2007-11-30 17:10:55 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.5)
Description of problem:
After I install the PPD file for the Kyocera Mita FS-1020 via
system-config-printer -> Action -> Import PPD
the printer driver is not available using the Printer driver menu
Version-Release number of selected component (if applicable):
Steps to Reproduce:
(The printer is already installed using a generic Postscript entry)
1. Start system-config-printer
2. Choose Action -> Import PPD
3. Select files /tmp/Kyocera_Mita_FS-1020_English.ppd
3. Choose Printer -> Edit -> Printer driver
There is no entry for the printer
Actual Results: Messages in the terminal where system-config-printers
Expected Results: An entry for the Kyocera FS-1020 should appear in
the Printer driver menu
I think the installed files should use the printer name not a generic
name like ppd-ppd1-*, ppd-ppd2-*, ...
Are you looking under "Kyocera Mita", which is what the PPD sets Manufacturer to?
Why do the XML file names bother you? They are not user-visible.
There is no entry for "Kyocera Mita"
The XML file names are printed on ther terminal, so i can see them.
If i install PPD files for different printers the ppd-ppd1-*, ppd-ppd2-*, ...
naming scheme is confusing
You probably have to restart system-config-printer after importing the PPD (this
is fixed in rawhide).
I don't see your point with the XML file names at all. How do they confuse you?
You never have to choose between different XML file names.
I did restart system-config-printer after importing the PPD but
It is fixed in rawhide. After i rebuilt
system-config-printer-0.6.117-1.src.rpm from rawhide and installed
i can see Kyocer Mita in the printer manufacturer menu and select and
use the correct printer driver.
My point with the XML file names is the aversion of a long time
systemadministrator against obscure naming scheme when it would be
easy to use descriptive names.
I had to install and delete the ppd files to test this case. I also
experimented with different languages of this driver. I always had to
open the file to see which PPD it belonged to.
If you install the same driver twice then next
is created, the existing is not used.
I missed a choice to delete a wronly installed PPD
Avoiding overwrites is intentional -- you might want to have two different PPDs
alongside one another, but for the same model.
Anyway, glad this is fixed in rawhide. Thanks for testing.