in our case, the optimization level definitely made the difference. On the new system described above, switching from -O3 to -O2 removed the error. Our older systems, which were compiled with -O2 right from the start, never showed the symptoms at all. So, at least in the case of the HP and Lexmark PPDs I used, KDEPrint itself seems innocent.
It is of course possible that other, actual errors show up for other PPDs, such as the Canon PPDs you mention. In that case, you should open a new bug report here (with a possible link to this report) and attach your PPDs.
I report again the solution:
from comment #9 in http:// bugs.kde. org/show_ bug.cgi? id=142220
Cimmo,
in our case, the optimization level definitely made the difference. On the new system described above, switching from -O3 to -O2 removed the error. Our older systems, which were compiled with -O2 right from the start, never showed the symptoms at all. So, at least in the case of the HP and Lexmark PPDs I used, KDEPrint itself seems innocent.
It is of course possible that other, actual errors show up for other PPDs, such as the Canon PPDs you mention. In that case, you should open a new bug report here (with a possible link to this report) and attach your PPDs.