(*** This bug was imported into bugs.kde.org ***) Package: knode Version: 0.6.1 (using KDE 2.2.1 ) Severity: normal Installed from: Unspecified Linux Compiler: Not Specified OS: Linux OS/Compiler notes: Not Specified knode dont display artikels correct if leafnode is configured with delaybody=1. leafnode saves the later loadet body under an other number then the header but knode serches for the number of the header. (Submitted via bugs.kde.org)
Hello ! It seems that I have the same bug ! Systeminformations: Suse 7.3 Linux Kernel: 2.4.10 KDE 2.2.1 Knode 0.6.1 leafnode 1.9.19 Nothing is compiled by myself everything are RPMs of my Distribution ! regards Kim Neunert
knode looks for the Xref: header set by leafnode. After fetching the news via fetchnews all old articles have got a new Xref: header with a new number so that knode can't get it from the news server leafnode. Why doesn't use knode the message ID? This should stay consistent. -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net
Can you please give us an updated on whether this is still a problem for either of you with a more recent version of knode?
Knode 0.7.1 and Leafnode 1.9.25.rel misbehave when delaybody=1. SuSE 7.0 KDE 3.0.4 kernel 2.2.19
Knode now works with the leafnode option of delaybody=1 if the new leafnode option of delaybody_in_situ=1 is set int /etc/leafnode/config I am using; leafnode-1.9.41-1mdk Knode 0.7.2 KDE 3.1.4 Mandrake cooker
Is it reasonable to close this bug as FIXED? or as WONTFIX? Rainer
Neither. I will fix it. There is a workaround for now, though. Besides setting delaybody=1 in Leafnode's configuration, also set the option below: delaybody_in_situ = 1 Then go to Settings -> Configure KNode -> Reading News -> Memory Consumption and set the "Cache size for articles" to 0KB. That should do it.
Replaced fnoack@t-online.de with null@kde.org due to bounces by reporter
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug.