desktop-packages team mailing list archive

[Till Kamppeter <1490055@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: chromium-browser (Ubuntu)
     Importance: High
         Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser 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 chromium-browser package in Ubuntu:
  New

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/chromium-browser/+bug/1490055/+subscriptions