[cups.general] STR #1923 fix incomplete?
Tim Waugh
twaugh at redhat.com
Thu Feb 15 08:33:45 PST 2007
The fix for STR #1923 (no way to distinguish user-set job default
options from system defaults) doesn't quite seem to fix the original
problem.
With the fix in place, there is at least a way of finding out *what* the
job default options are even for options that aren't user-set, but there
is no way to know if any given option has been set by the user or if it
is a system default.
The only hack I can think of is to experimentally alter the queue: try
removing an option and re-fetch, to see if it has changed. But even
this would not let me discover a user-set option that has been set
(coincidentally) to the system default's value.
Let me explain why this is an issue for me: the user interface we use in
Fedora for altering these options is an add/remove type, as shown in the
attachment. Currently this is implemented by fetching printers.conf and
parsing it for 'Option' lines, which of course requires the root
password. The reason I filed STR #1923 is to avoid the need for the
root password when displaying the options screen.
Tim.
*/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot-Printer configuration - localhost.png
Type: image/png
Size: 38605 bytes
Desc: not available
URL: <https://lists.cups.org/pipermail/cups/attachments/20070215/c514a3d5/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <https://lists.cups.org/pipermail/cups/attachments/20070215/c514a3d5/attachment.bin>
More information about the cups
mailing list