Summary: | KPrinter times out too fast when CUPS server slow to respond | ||
---|---|---|---|
Product: | [Unmaintained] kdeprint | Reporter: | Thibaut Cousin <kde> |
Component: | general | Assignee: | KDEPrint Devel Mailinglist <kde-print-devel> |
Status: | CLOSED FIXED | ||
Severity: | normal | CC: | jlayt, me |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Thibaut Cousin
2006-10-19 10:09:38 UTC
The timeout for KPrinter's connection to CUPS is presently 1.5s and not configurable. I will either increase this value or think of some other, adaptive or interactive (ugh :-( ) mechanism. Thank you. A longer, still not-configurable, value would be fine, I think. When my 802.11g network is really under heavy load (even typing through an SSH connection is slow), a five-second timeout should be OK. If you want to make it configurable, there is a panel for connection preferences in KControl, where various time values can be set. Maybe you could reuse a value there, or add a new one. There was a bug in KDE 3.5.5 which had a way too low timeout value for the CUPS server tor respond. This was fixed after the 3.5.5 release (see bug 135561). Do you know if older KDE versions like 3.5.4 behave correctly? Sorry, I don't know. I only noticed this bug after the KDE 3.5.5 release. Older KDE versions all worked correctly, for me at least. 3.5.5 using konstruct produced the bug. The fix from bug 135561 does indeed fix the issue, and all is OK again. My bug 131926 is still there though (wrong CUPS test page)... Nick Thibaut, can you please check that you have the fix mentioned in bug 135561 applied to your current KDE and if yes, can you please tell me if you still have the problem? Thanks This fix is not included in the current OpenSUSE packages. I will rebuild the package with it today, but testing it will take a bit time, since my network is no longer under heavy load. I'll have to think of something. ;) The patch sets the timeout to 1500. What's the unit? If it's 1500s, isn't it a bit too much? 1500 milliseconds Oh, OK. Are you sure that's enough? In my case, the delay caused by the network load seemed to be several seconds, even though I admit it's really difficult to estimate. But it sure is getter than 1ms. ;-) Thibaut, can you confirm that the fix mentioned in bug report 135561, and in this bug report, in comments 6, 7, 8, solves the problem for you? I'm sorry, that will be difficult. First I can't easily reproduce the heavy network load I had before, and second OpenSUSE has now integrated this patch. Maybe I'll be able to try again by the end of the week. If the problem resurfaces, I'll let you know. Well, after six months the problem never reoccured. :-) Shall we close this bugreport? Yes, we close. It was a known bug in the sources for 3.5.5, fixed subsequently. Thanks. *** Bug has been marked as fixed ***. Closing old Resolved status bug. |