@André: I can see no obvious reason why 1.5.3-0ubuntu3 would reintroduce this bug - could you please check if updating again to cups 1.5.3-0ubuntu3 (this should be as simple as running update-manager) breaks it again for you?
Once we've verified that 1.5.3-0ubuntu3 is the problem we'll need to work out why.
@André: I can see no obvious reason why 1.5.3-0ubuntu3 would reintroduce this bug - could you please check if updating again to cups 1.5.3-0ubuntu3 (this should be as simple as running update-manager) breaks it again for you?
Once we've verified that 1.5.3-0ubuntu3 is the problem we'll need to work out why.