Description of problem:
In Konqueror (and most other kde applications) the printer settings previous selections are not automatically remembered next time printer dialogue is used nor is there a method to save the settings. This is both: time consuming when multiple pages with same settings requirements are printed and; a step backwards from the modus operandi of kde 3. It is an old bug present in Fedora 9 and later, just hoping reporting it here may make a difference.
Version-Release number of selected component (if applicable):
Konqueror Version 4.3.4 (KDE 4.3.4)
Steps to Reproduce:
1.Using Konqueror Browser
2.File => Print
3.Options => HTML Settings
4.Uncheck Print Images
6.Then Repeat 2 and 3
Print Images Checked
Print Images Unchecked
This bug has been reported both to KDE and QT in the past. It'll be interesting to see if anything is done now it's in RHEL6
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
Well, in Fedora, and AFAIK RHEL6 inherits the relevant patches from Fedora, the Qt/KDE print dialog should at least be honoring the settings you set as defaults in CUPS, thanks to this Qt patch:
(The patch comes from the KDE bug report and handles Duplex, Color/Grayscale and Collate.)
But it still won't remember previous settings in the dialog itself.
-- Kevin Kofler, comaintainer of Qt and KDE in Fedora
Linking the Fedora bug (bug 480954) as well.
AFAIK, RHEL6 also carries this backported patch:
from upstream Nokia which is included in 4.6.3 and newer releases of Qt.
This patch makes the Qt/KDE print dialog default to the paper size set in the CUPS settings. See Fedora bug 523846.
Oops, I meant to link the KDE bug, too, but somehow it got forgotten.
(Well, it's just getting ignored. Does Bugzilla not accept upstream bug references on RHEL bugs? Sorry for the bugspam.)
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.