Cimmo, for Gutenprint it is really different. The cupsys-driver-gutenprint package does not ship any PPDs but a much smaller PPD generator. This generator is invoked by CUPS if a client asks CUPS for PPD listings or PPDs. The KDE Printing Manager does not ask CUPS for PPDs. It searches by itself in the file system and also browses Foomatic XML files. So it does not find PPDs for cupsys-driver-gutenprint. Therefore the suggestion by Jonathan and me to replace cupsys-driver-gutenprint by foomatic-db-gutenprint and ijsgutenprint.
The change of the optimization level can be done independently to fix the other, independent PPD listing problem.
Cimmo, for Gutenprint it is really different. The cupsys- driver- gutenprint package does not ship any PPDs but a much smaller PPD generator. This generator is invoked by CUPS if a client asks CUPS for PPD listings or PPDs. The KDE Printing Manager does not ask CUPS for PPDs. It searches by itself in the file system and also browses Foomatic XML files. So it does not find PPDs for cupsys- driver- gutenprint. Therefore the suggestion by Jonathan and me to replace cupsys- driver- gutenprint by foomatic- db-gutenprint and ijsgutenprint.
The change of the optimization level can be done independently to fix the other, independent PPD listing problem.