[Kde-print-devel] [Bug 90283] initializing managers hangs when the CUPS server is offline

[Sean E.Russell]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=90283         




------- Additional Comments From kdebugzilla ser fdns net  2006-01-05 17:02 -------
I've started noticing this with KDE3.5 (it didn't happen before).

I have a remote print server (actually, in the same room, on the same subnet).  The host is declared in the /etc/hosts file.

The strange thing is that this only happens every other time.  It works once, and then the next time I try to print, it hangs.  I kill it, and try again, and it works.  Next time, it hangs.  Etc, ad nauseum.  It is, in this respect, reproducable.  I can even open three different Konqueror windows to the same document.  Opening the print dialog on the first is OK; opening it on the second hangs; opening it on the third is OK.  There are no errors being dumped to .xsession-errors relating to this.

In my case, it has nothing to do with the print server (AFAICT) being off-line -- I can always access the CUPS server via http://192.168.1.2:631, even while KDE is hanging, and as I said, while one process is hanging I can open print from a second Konqi instance -- and it has nothing to do with DNS, unless KDE is trying to route around the /etc/hosts file and get DNS info for my subnet entries every other time.

Again, I didn't see this problem with KDE3.4; the upgrade to 3.5 is the only thing that has changed in the equation.  There have been no software upgrades on the server; it is possible that CUPS on the client was upgraded, but why would that matter?

As an aside, I think the original poster had a point about the fact that the entire print system is off-line if something happens to the network.  This means that, even if all you want to do is print to a PDF, the KDE print system locks up if there is a network problem.

--- SER