Bug 212338 - print dialog to remote CUPS printers is painfully slow
Summary: print dialog to remote CUPS printers is painfully slow
Status: RESOLVED DUPLICATE of bug 179955
Alias: None
Product: kab3
Classification: Unmaintained
Component: printing (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Tobias Koenig
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-30 01:47 UTC by andrew
Modified: 2009-10-30 01:53 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description andrew 2009-10-30 01:47:21 UTC
Version:            (using KDE 4.3.2)
OS:                Linux
Installed from:    Unlisted Binary Package

I have a mac mini to which my printers are connected.  This runs CUPS v1.1.20.  By and large printing works just fine: all the remote printers are detected and I can print documents.  However opening of the print dialog is painfully slow when using KDE applications (much more responsive when using OOO or firefox).

Some debugging on the server indicates that it is sending the PPD of each printer, twice, to the KDE client before the print dialog is even drawn.  By comparison the PPD of only the default printer is sent to non-kde applications.  As there seems to be some slowness about this file transfer this seems to explain the relative slowness of KDE printing.

Note also that the KDE print dialog seems to download the PPD again when the a new printer is selected via the pull-down on the print dialog.  Even though that ppd will already have been downloaded at least twice already.

All in all KDE needs to be a lot smarter about caching this information in order to provide a responsive remote printer interface.

Thanks.
Comment 1 andrew 2009-10-30 01:50:10 UTC
my appologies: this seems to be a duplicate of 207890, which is in turn a duplicate of 179955
Comment 2 andrew 2009-10-30 01:53:13 UTC

*** This bug has been marked as a duplicate of bug 179955 ***