Version: 0,10,1 (using KDE KDE 3.5.3) Installed from: Gentoo Packages OS: Linux It is possible to select to start mlnet when kmldonkey starts or when kde starts. On a system on wich mlnet is started as a deamon by init, it forces kmldonkey users to try to start second instance of core. Solution: Add third option "Core is always active / started manually".
This is done by choosing "External Core" rather then "Managed Core". So, it's not needed to add additional option that does in fact exactly what the "External Core" is for. If that option got selected, KMLDonkey want try to start a new core rather then trying to connect to an already started core (you just need to define the matching address+port at the connections). So, report marked as worksforme.
Sorry for poor quality of my english resulting in incomplete description. I meant that in Startup Wizard should be an option to choose external core. Currently, this wizard may make people think that it's impossible - and in such cases makes configuration more complex, instead of simplyfying it.
Lack of "External core" option in Startup Wizard, suggesting there is no such option.
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years and I will be closing this bug.