Hi, here I am again.
The situation is as follows, chronologically:
1) First I had some performance problems with an older version of aMule (I think it was 2.1.1), so I decided to trash the app and reinstall the latest release version.
2) After installing the new app I got the beachball every time I tried to edit the preferences from within the application, i.e. the app hung whenever I would click the Preferences button.
3) I rolled back to 2.1.1. But then I got the beach ball immediately after startup.
4) I deleted that version, and installed the latest build. At first I got the beachball at startup, just as with 2.1.1. I edited the config file manually, and made it so that the app would not load any files at startup, and would not connect to anything, as a way of troubleshooting the issue. But the app still hung on startup. Then I edited the configfile back to the default values, and voila, somehow this helped, because the app starts up normally.
5) BUT: when I try to edit the config from within the app with the Preferences button, I get the beachball again.
Of course I have already done all the regular maintenance and troubleshooting things, like fixing permissions, running all cronjobs, several reboots, deleting system and user caches, etc. etc. etc.....
I am out of ideas.
