I have been running Open Suse 10.3 for a couple of months now & with it I have been using amule for about a month, originaly I installed amule from yast, it is listed there, after configuring & opening the appropriate ports all has been working well. Last night I was typing a letter with Open Office Two, Writer, which has never given any problems, when suddenly everything hung, the only solution was to use reset. On reboot everything seemed to be well cept that the logon screen did not appear, it just went straight to the desktop, I was logged on as user. On the user desktop, some icons which had previously been visible on the root desktop only, now were on the user desktop also. When I tried to open amule, it briefly flickered but nothing else happened, on trying again with a "top" window showing, amule briefly appeared on the "top" window, then disappeared. I have tried uninstalling amule with yast, rebooting & then reinstalling it, no difference. I tried moving the contents of the amule, incoming & temp, folders to differently named folders on the desktop, no effect.
So everything on the system seems to work OK, cept for the problem with amule & the missing logon screen.
Any ideas will be welcome, I don't really want to wipe the disk & reinstall 10.3, but I am thinking that this will be the only way.
Thanks.

Check this out! SUSE 10.3 sucks man. The thread title may be different here, but a lot of people have had the same problem. And that includes me too!

Thanks deepumnit.
I looked at the link but nothing seems relevant to my prob, my system does not normaly hang, nor does it suffer from overheating, it still runs OK cept for the amule & loggon prob's.

Further to my original post. I entered "amule, & then amule --sync,
in a terminal, with the following results.
Does this help any?

~> amule
Initialising aMule
Checking if there is an instance already running...
No other instances are running.
HTTP download thread started
The program 'amule' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 629 error_code 11 request_code 144 minor_code 5)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)

~> amule --sync
Initialising aMule
Checking if there is an instance already running...
No other instances are running.
HTTP download thread started
The program 'amule' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 1176 error_code 11 request_code 144 minor_code 5)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
~>

It seems like a 'bug' in the program. You know to debug? If you do not, you can report this on the Amule website.

Thanks deepumnit, I'll try that, regards.