[Quantal] CUPS / Gutenprint cannot print - Outdated PPD

[Swâmi Petaramesh]

Since upgraded from Precise to Quantal Alpha3, and now Beta1 with all updates applied, I could not print anymore.

CUPS logged things like :

D [13/Sep/2012:19:29:30 +0200] [Job 66] Gutenprint: using PPD file /etc/cups/ppd/Stylus-CX3600.ppd
D [13/Sep/2012:19:29:30 +0200] [Job 66] Set job-printer-state-message to "The PPD version (5.2.8-pre1) is not compatible with Gutenprint 5.2.9.", current level=ERROR
D [13/Sep/2012:19:29:30 +0200] [Job 66] Gutenprint: If you have upgraded your version of Gutenprint
D [13/Sep/2012:19:29:30 +0200] [Job 66] Gutenprint: recently, you must reinstall all printer queues.
D [13/Sep/2012:19:29:30 +0200] [Job 66] Gutenprint: If the previous installed version of Gutenprint
D [13/Sep/2012:19:29:30 +0200] [Job 66] Gutenprint: was 5.0.0 or higher, you can use the `cups-genppdupdate.5.2'

Actually, I could solve the issue the following way :

root@tethys:~# cups-genppdupdate
Updated /etc/cups/ppd/Stylus-CX3600.ppd using gutenprint.5.2://escp2-cx3600/expert
Updated 1 PPD file. Restart cupsd for the changes to take effect.

root@tethys:~# restart cups
cups start/running, process 18915

Once done, it prints, but I assume users aren't expected to do this ;-)

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: printer-driver-gutenprint 5.2.9-1ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3
Uname: Linux 3.5.0-14-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
CheckboxSubmission: 1ea6109db29b53f721a523a77b7f3abf
CheckboxSystem: d00f84de8a555815fa1c4660280da308
Date: Thu Sep 13 19:40:18 2012
EcryptfsInUse: Yes
SourcePackage: gutenprint
UpgradeStatus: Upgraded to quantal on 2012-08-28 (16 days ago)

[Logan Rosen (logan)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 932882, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.