Bug 225738

Summary: KDE applications will not print to CUPS with Kerberos / GSSAPI
Product: [Unmaintained] kdelibs Reporter: Anthony Messina <amessina>
Component: print-dialogAssignee: KDEPrint Devel Mailinglist <kde-print-devel>
Status: RESOLVED UPSTREAM    
Severity: normal CC: jlayt
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Anthony Messina 2010-02-06 17:15:38 UTC 
Version:            (using KDE 4.3.5)
OS:                Linux
Installed from:    Fedora RPMs

Using the latest KDE applications from F12-stable, I am unable to get any
KDE-based applications to print to a CUPS server using Kerberos.  I am using
cups-1.4.2-20.fc12.x86_64

I AM however, able to print just fine with Firefox under KDE to the
Kerberos-enabled CUPS server.  I followed the directions here:
http://cups.org/documentation.php/kerberos.html

From KDE apps, I get the same error as listed here:
http://www.cups.org/str.php?L3435

But that problem was to have been fixed here:
* Tue Dec 08 2009 Tim Waugh <twaugh@redhat.com> - 1:1.4.2-14
- The scheduler did not use the Get-Job-Attributes policy for a
  printer (STR #3431).
- The scheduler added two job-name attributes to each job object
  (STR #3428).
- The scheduler did not clean out completed jobs when
  PreserveJobHistory was turned off (STR #3425).
- The web interface did not show completed jobs (STR #3436).
- Authenticated printing did not always work when printing directly to
  a remote server (STR #3435).

This was reported against Fedora here https://bugzilla.redhat.com/show_bug.cgi?id=558006 and the recommendation was to report this upstream.

This may be related to:
https://bugs.kde.org/show_bug.cgi?id=138414
https://bugs.kde.org/show_bug.cgi?id=113764

both of which, are quite old.
Comment 1 John Layt 2010-02-08 11:59:48 UTC 
KDE4 uses the Qt printing system, and while we add some extra features to the print dialog, at the level of talking to CUPS and authentication that is all Qt and something we cannot change.  You should be able to confirm this by running a 'pure' Qt application such as Qt Assistant.  Sorry, but you will need to raise this even further upstream at http://bugreports.qt.nokia.com/secure/Dashboard.jspa

Thanks!
Comment 2 Anthony Messina 2010-02-08 16:38:42 UTC 
Thank you for your information.  Before I report upstream, would you be able to let me know if this is supposed to work currently?  I guess what I am asking is should I report a feature request or a bug request upstream?

Since I'll be reporting now 3 levels (Fedora -> KDE -> Main Qt) above where I am, I'd like to keep track of where I should land, when I fall.  Thanks.