https://bugzilla.novell.com/show_bug.cgi?id=776080
https://bugzilla.novell.com/show_bug.cgi?id=776080#c46
--- Comment #46 from Johannes Meixner 2012-12-14 10:19:03 CET ---
Eric Schott,
for general information regarding the various ways
of option settings and possible confusions, see
http://en.opensuse.org/SDB:Print_Settings_with_CUPS
I think in your case the default option settings
via lpoptions might mix up with the individual
option settings via lp command line parameters '-o...'
or with individual option settings in print menues of
application programs so that in the end the CUPS filters
might get self-contradicting option settings like
sides=two-sided-long-edge sides=two-sided-short-edge
(one from lpoptions the other one from lp command)
CUPS filters get all option settings via argv[5],
see "man 7 filter". To see which option settings
have been actually used for a print job, set in
/etc/cups/cupsd.conf "LogLevel debug" and
restart the cupsd. Then argv[5] will be shown
in /var/log/cups/error_log
If CUPS filters get self-contradicting option settings
it would be random which option setting is actually used.
Furthermore in comment#43 you wrote
"/etc/cups/lpoptions" and "remote client":
If I remember correctly, /etc/cups/lpoptions is only applied
for print jobs that are submitted on the host where the
/etc/cups/lpoptions is. This means that for print jobs that
come in from a remote client a /etc/cups/lpoptions file
on that client is used but a /etc/cups/lpoptions file on
the print server is not used. The actual behaviour may
even depend on the CUPS version.
See in particular the "Suggestion for Keeping an Overview" in
http://en.opensuse.org/SDB:Print_Settings_with_CUPS
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.