FS#35558 - [cups-pk-helper] Too strict printer name validation

Attached to Project: Arch Linux
Opened by Philipp Wolfer (phw) - Thursday, 30 May 2013, 16:59 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Tuesday, 11 February 2014, 20:36 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Ionut Biru (wonder)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Adding a printer via the Gnome settings failed for me, as the printer name suggested by Gnome is "Photosmart-C3100-series". In journalctl i see this information:

cups-pk-helper: addition of printer Photosmart-C3100-series failed: "Photosmart-C3100-series" is not a valid printer name.

The reason is a too strict printer name validation, upstream has a patch for that at
http://cgit.freedesktop.org/cups-pk-helper/patch/?id=f00aee0b43c31e94087668b23b72e873c660de5e

With the patch applied I was able to add the printer without further issues. As this disables printer configuration in Gnome for many models I suggest to include this patch in the arch package until a new version is released.
This task depends upon

Closed by  Gerardo Exequiel Pozzi (djgera)
Tuesday, 11 February 2014, 20:36 GMT
Reason for closing:  Fixed
Additional comments about closing:  0.2.5-1
Comment by Philipp Wolfer (phw) - Thursday, 30 May 2013, 17:01 GMT
I missed the input field for the bug summary, but I can't change it now. Sorry, my fault. It would be great if you can give this bug report a more meaningful title :)
Comment by Michael Heyns (beanaroo) - Thursday, 30 May 2013, 23:29 GMT
Just to confirm I can confirm I am getting this bug too. I can add printers normally via system-config-printer and cups web interface.
Comment by Alexander F. Rødseth (xyproto) - Sunday, 02 June 2013, 23:18 GMT
Hi, thanks for reporting. In general, Arch Linux does not apply patches, but waits for upstream to make a new release. This is maintains a good separation of concerns. Let's see what the package maintainer chooses to do.
Comment by Antonio Vázquez Blanco (antoniovazquezblanco) - Wednesday, 12 June 2013, 20:28 GMT Comment by Philipp Wolfer (phw) - Friday, 14 June 2013, 11:50 GMT
I can verify that the new release fixes the problem. This bug report can be closed once the new version is packaged.

Loading...