Was the latest cups update not meant to address this issue (too)?
Since today's update, the issue is resolved for me.
Was the latest cups update not meant to address this issue (too)?
Since today's update, the issue is resolved for me.