The problem here is
https://www.cups.org/str.php?L4725
and this one I have fixed in the Ubuntu CUPS package, in version
2.1.0-4ubuntu1.
** Package changed: chromium-browser (Ubuntu) => cups (Ubuntu)
** Changed in: cups (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1490055
Title:
Print dialog hangs when PPD file in /etc/cups/ppd/ is not world-
readable
Status in cups package in Ubuntu:
Fix Released
Bug description:
It seems that the print dialog of the Chromium browser (the browser's
own one with the preview) tries to read the PPD file (the file
containing the printer's properties and the printer-specific user-
settable options) in /etc/cups/ppd/ directly to be able to display the
dialog with correct options and correct preview. The correct method
(which is also actually used by the GTK print dialog) is to use the
API of the CUPS library or IPP requests to the CUPS daemon.
As it depends on the configuration of CUPS whether the PPD files in
/etc/cups/ppd/ are world-readable and so readable for desktop apps run
by ordinary users, it easily happens that the direct reading does not
work. Therefore it is very important that print dialogs are properly
done.
What I am observing currently is that if the PPD of the selected
printer is not world-readable the print dialog hangs and is not able
to display the preview and the options. The user can only click the
link to use the standard GTK dialog.
See also
https://www.cups.org/str.php?L4703
about the world-readability of PPD files.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1490055/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
