Comment 7 for bug 951627

Unfortunately, the 1.5.3 release will not land in time for Precise, what we have to do is either to ship the current SVN snapshot as the CUPS of Precise or to find out which change fixed your problem. The former has the risk to introduce another bug before things can be "unready" in the current development state, the latter is more work and missing already introduced fixes for other bugs. The "more work" will have to be done mainly by you as my HP printers do not show the bug. What has to be done is to go through all the changes since 1.5.2 and find the one which fixes your problem. There are two methods: Look into "svn log" and see what can be the appropriate change and try it, the other is bisecting, which means a binary search for the fix: If rev m does not work and rev m works, try rev (m+n)/2 if this works n := (m+n)/2 otherwise m := (m+n)/2 and try again. svn has perhaps some functionality for this.