Problem in aster module in 2009.1

I'm experiencing problems when loading old cases with the new salome-meca_2009.1. Geometry and meshes are loaded ok, but when I go to the aster module and select to "edit the code-aster case", the ssystem enter in a loop and the only way to escape is CRTL-D in the shell-salome window.
I have installed salome-meca_2009 aside of the old 2008.1, in a separate directory, so I have at the moment:

1) /opt/SALOME-MECA_2008.1
and
2) /opt/SALOME-MECA_2009.1

I have already deleted astkrc in my home directory, as well all salome related files, but my problem is still in.

If I try to create a new case and then switch to aster module, in the preferencies, Code-Aster 9.4 is correctly shown as current server.




This is the last thing appearing in the shell window:


[code:1]AsterGUI --- customPopup
<qt.QPopupMenu object at 0x9f3c526c>

76
ObjectBrowser
AsterGUI :: OnGUIEvent :::::::::::::::::::::::::::::::::commandID 9044
OnGUIEvent :::::::::: commande associ�e : 9044
as_info serviceConfig-> {'astkExecDir': '/opt/SALOME-MECA-2009.1-GPL/aster/ASTK/
ASTK_SERV/bin', 'userver': 'caelinux', 'mserver': 'mcad-3'}
__rexec_cmd serviceConfig -> {'astkExecDir': '/opt/SALOME-MECA-2009.1-GPL/aster/
ASTK/ASTK_SERV/bin', 'userver': 'caelinux', 'mserver': 'mcad-3', 'mclient': 'mca
d-3', 'uclient': 'caelinux'}
CS_pbruno SERVICE -> unset PYTHONHOME; /opt/SALOME-MECA-2009.1-GPL/aster/ASTK
/ASTK_SERV/bin/as_serv as_info --rcdir=salome2009.1
output
<I> WARNING

---

ASTK services changed starting version 1.6.0.

Old syntax :
/opt/SALOME-MECA-2009.1-GPL/aster/ASTK/ASTK_SERV/bin/as_serv as_info --rcd
ir=salome2009.1

New syntax :
/opt/SALOME-MECA-2009.1-GPL/aster/ASTK/ASTK_SERV/bin/as_run --info --rcdir
=salome2009.1

Please update your client and use new syntax.

---

---

>>> 000000001 [__init__@/local01/assire/SALOME-MECA-2009.1-BUILD/SALOME-MECA-20
09.1/aster/ASTK/ASTK_SERV/lib/as_system.py:174]

ASTER_SYSTEM param :
{'remote_shell_protocol': 'RSH', 'remote_copy_protocol': 'RCP'}
@SERV_VERS@
01.07.01
@FINSERV_VERS@
@PARAM@
plate-forme : LINUX
batch : non
batch_memmax : 12000
batch_tpsmax : 72:00:00
batch_nbpmax : 16
interactif : oui
interactif_memmax : 2048
interactif_tpsmax : 99:00:00
interactif_nbpmax : 16
@FINPARAM@
@VERSIONS@
vers : STA9.4
@FINVERSIONS@
@NOEUDS@
noeud : CAD9
noeud : claut629
@FINNOEUDS@
@MOTD@
@FINMOTD@

EXIT_CODE=0
serviceVerMatch = <_sre.SRE_Match object at 0x9f3c6560>
paramsMatch = <_sre.SRE_Match object at 0x9f3c6520>
asterVerMatch = <_sre.SRE_Match object at 0x9f3c65a0>
noeudsMatch = <_sre.SRE_Match object at 0x9f3c65e0>
as_info serviceConfig-> {'astkExecDir': '/opt/SALOME-MECA-2007.1-GPL/aster/ASTK/ ASTK_SERV/bin', 'userver': 'sti', 'mserver': 'cad9'}
__rexec_cmd serviceConfig -> {'astkExecDir': '/opt/SALOME-MECA-2007.1-GPL/aster/ ASTK/ASTK_SERV/bin', 'userver': 'sti', 'mserver': 'cad9', 'mclient': 'mcad-3', ' uclient': 'caelinux'}
CS_pbruno SERVICE -> rsh -l sti cad9 'unset PYTHONHOME; /opt/SALOME-MECA-2 007.1-GPL/aster/ASTK/ASTK_SERV/bin/as_serv as_info --rcdir=salome2009.1 '
>>> [/code:1]

I found a process consuming 100% of the cpu:

rsh -n -l caelinux mcad-3 echo hello

I don't know if it is related with Salome-Meca or it is something totally unrelated (mcad-3 is the name of the local machine).