Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[amuler]

Hello,

I have just updated from 2.1.0 to 2.1.1. Now the Win remote GUI (v2.1.1) cannot connect anymore.

When I start the GUI the connection dialog shows and then nothing. The GUI process is still running but does not show a applikation window.

The server on debian sarge show the following message for every trial:
>> CECSocket error: Invalid socket (uninitialized)

Version 2.1.0 worked fine except of a lot of minor bugs.

Regards,
Marco

[Kry]

I tested it here and works perfectly. review your setup, make sure both GUI and amuled are the same version, check logs, etc.

[amuler]

logfile sagt "Unkorrekte EC Versions-ID".

Aber davor steht auch "FEHLER: Info  --- Dies ist das erste Mal, dass du aMule 2.1.1 startest ---"

Und am Client starte ich sicher aMuleGUI-2.1.1-MSW.zip

Vielleicht sind ja falsche Version auf der Web-Site?

[Gerd78]

English, please.

Originally posted by amuler
logfile sagt "Unkorrekte EC Versions-ID".

Incorrect EC version ID - are you 100% sure that you are not mixing components from different releases with each other?

Originally posted by amuler
Aber davor steht auch "FEHLER: Info  --- Dies ist das erste Mal, dass du aMule 2.1.1 startest ---"

This is normal. aMule keeps a log file and informs you each time you run a new version for the first time. It will no longer appear next time you run it.

[amuler]

Incorrect EC version ID - are you 100% sure that you are not mixing components from different releases with each other?

The server is from a current debian package and as you see it states that it is 2.1.1 and the client is from the current aMuleGUI-2.1.1-MSW.zip from the amule.org site.

Are there CVS versions 2.1.1 which are not compatible with the win remote GUI 2.1.1? I did not compile the server myself. How can I check which version it actually is?

Can somebody confirm that aMuleGUI-2.1.1-MSW.zip currently available from amule.org is compatible with 2.1.1?

Why does the server print out "CECSocket error: Invalid socket (uninitialized)"?

[Kry]

Well I did build it and test it so yeah, it seems to work on my side.

[thedude0001]

Originally posted by amuler
How can I check which version it actually is?

'amuled --version' should help, just like 'amulegui --version' on the client.

[amuler]

It is so satisfying to know that it works on your side

But please help me to make it run on my side. I stated some questions which I think could help to find the root of the problem.

Probably you know better what could be the reason for it. Please help me.

[amuler]

Code: [Select]

$ amuled -v
amuled: OnInit - starting timer
aMuled 2.1.1 using wxGTK2 v2.6.2 (Unicoded) (Snapshot: rev. 38) (OS: Linux)
Is this "snapshot" compatible with aMuleGUI-2.1.1-MSW.zip?

[thedude0001]

That "Snapshot" is not a snapshot, it's the regular 2.1.1, the wrong version info is somewhat my fault, I'll fix that right now... But that shouldn't prevent amulegui from connecting to it. Can you give us the output of 'amulegui --version', too?

[amuler]

The windows gui does not support the --version option.

--verbose brings a window with the message:

looking for catalog 'wxstd' in path 'C:\Programme\aMule...

[thedude0001]

OK, I've had a similar report on the german forums, and it worked for that user after he updated amuled to the new version I uploaded earlier today which fixed the wrong version info. Please try 'apt-get update && apt-get dist-upgrade' on your debian box and check if the problem is still present.

[amuler]

done - solved - thx - regards

[thedude0001]

OK, good to hear. Sorry about the inconvenience ^^