| Summary: | knode freezes when connecting to server | ||
|---|---|---|---|
| Product: | [Unmaintained] knode | Reporter: | kdnp |
| Component: | general | Assignee: | kdepim bugs <pim-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 0.6.1 | ||
| Target Milestone: | --- | ||
| Platform: | RedHat Enterprise Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
kdnp
2001-10-12 05:23:40 UTC
I have the same symptoms as the bug report 33611. I have just updated my Suse 7.1 to 7.3. I was already running KDE 2.2.1 after updating kde with rpm's supplied by Suse earlier in the year. I decided to let suse re-install KDE 2.2.1 as I felt this would offer less chance of corrupting the current KDE installation. After the install everything in KDE works except Knode. It will start and I can close it down ok but as soon as I try to download new headers Knode will freeze saying connecting to server. I then can only exit Knode by using the killall -9 knode command. I upgraded two PC's which were both running suse 7.1 KDE 2.2.1 (but different hardware) and they both have the same problem. Hope this helps Tim -- Today is the tomorrow you worried about yesterday! The last update to this bug report was many months ago. Can you please give us an updated on whether this is still a problem for you with a more recent version of knode? If it is not a problem - the status of this bug report will be changed to closed. |