mindpirate, on Mar 4 2007, 06:39 AM, said:
Hm, I haven't heard of anyone having Kad-specific problems with eMule under Wine before. You say you're using 0.9.32 on Kubuntu, but 0.9.32 was only released yesterday. Which repository did you get it from (or did you build from source)?
Oops... sneaky updates. It was 0.9.31, but I updated to .32 now for real.

I get my updates from WineHQ APT Repository (see download page...)
mindpirate, on Mar 4 2007, 06:39 AM, said:
Also, have you tried installing eMule to a fresh directory and bootstrapping Kad from some random client?
Nope. Maybe I'll try later (unfortunately those tests are time intensive)...
It seems, the problem arises when I close my laptop's lid.

The Network connection somehow gets disturbed when I do this...
Around that time I got for example
Quote
05.03.2007 01:22:05: Error: Client UDP socket, failed to receive data: Error 10035
And since then KAD started to drop one node after another and completely disconnected a few minutes later. No further messages in verbose log. Wine also don't gives any error messages in it's console window.
But KAD doesn't always immediately die when the network connection gets confused this way... I also got many other errors then and sometimes a LowID, too. Strange... Maybe some driver error...
mindpirate, on Mar 4 2007, 06:39 AM, said:
I still try aMule from time to time just for laughs. Last time was a couple of weeks ago, and apart from the usual crappy user interface design issues, I wasn't surprised to discover, as you did, that it can't stay connected to Kad for more than a few minutes. This is one of the reasons this HowTo was created, and why it will continue to exist -- nothing beats eMule.

Yup, Full ack. These bugs in aMule are known for years now and... oh well... too bad eMule doesn't run without its GUI though.
This post has been edited by KastenKopf: 05 March 2007 - 01:44 AM