Torsdag den 21. oktober 2010 07:13:28 skrev Marc Chamberlin:
I have a number of client computers running SuSE11.2 with KDE4.5.2 and a single printer server using CUPs. I set up all my clients using YaST, to do all my printing via one remote CUPS server and point them at the printer server (also running SuSE11.2 with KDE4.5.2) The profile that the CUPS server is set up with is the Default profile that comes as is with SuSE.
Recently I changes my passwords on the server, something I am prone to do once in awhile, and now I have an interesting situation that points me to think there is a KDE issue of some kind. CUPS, FF, OOo, xemacs.. doesn't sound KDE related to me.
Maybe log into icewm or twm and try printing from there, to check if the problem really only exists in kde sessions. Thanks Martin for replying! I admit I am guessing as to where the
On 10/21/2010 4:18 AM, Martin Schlander wrote: problem might lie, and my reasoning was as follows - Since a command line argument works - lpr - and I can enter an interactive session of queries for id and password, I know that basically my communication with the CUPs printer server is working from my client systems. Since it is all the GUI based applications that are failing to properly ask for authorization, I guessed that the common component is the window manager. I don't know much about how window managers are designed for Linux, or where responsibilities lie, but it would seem to me that it, or some other layer should be responsible for handling the interface to printers, and in particular something GUI based, for the authorization process as well as setting various default printer options. Since these apps are not command line oriented, the only way to do that is via a window dialog box. If there isn't some sort of print management layer, and each app is responsible for handling the printer authorization process on it's own, (and setting of printer options) then it would be highly likely that printer management will be inconsistent at best, and lead to a lot of user frustration. That would certainly argue for better handling of printers, and the window management layer seems like the place where such common requirements can be handled. Therefore I guessed that it should be providing such a service to the apps. If not, then who should? (My first guess was to look in the Personal Settings dialog for the KDE desktop, but there is nothing there to handle printers!) I tried icewm and got the same results so apparently the window management designers do not feel the same way as I do and have left the printer problem for others to solve. So is it each apps individual responsibility to fully implement a printer interface and handle the authorization process? To include an interface for setting all the various printer options?? For different possibilities for each printer??? I hope NOT!!! Again, not understanding how printers are handled in Linux, how do I get GUI based applications to interact with, or use a setting somewhere, so as to be able to send a print job to a CUP's server that requires authorization? (as an aside, the fact that Firefox does provide an authorization dialog box for id and password suggests that it is the apps responsibility for handling the printer interface, but I am going to argue that is really the wrong model! What is really worrying me about Firefox though is that I am able to print using my old password. The CUPs server is configured to use Basic authentication and not Digest. SO why is it accepting a password that is different from the one for my user account, on the server machine, is configured to use? I know, this is probably a CUPs question, but I am missing something here. It is really wrong that Firefox should be able to print using that particular password!!! And again this is the sort of inconsistent behavior problems one is going to encounter if there is not a common interface for handling the printers. If I print from a command line, then I MUST use the new password that I set up for my account on the server, it won't accept the old password as I would expect.) Thanks again for any advice and help offered, in advance... Marc Chamberlin -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org