I've had the same problem and the solution is not very nice...
I had to create a secondary directory from where you launch the second client and create a symbolic link to the data directory, then copy the remaining files, including the binaries. You can do:
cd <your directory containing the "ryzom" install directory>
mv ryzom/data backup_data
cp -R ryzom ryzom_2nd
mv backup_data ryzom/data
cd ryzom_2nd
ln -s ../ryzom/data data
Then you run one client from "ryzom" and the other from "ryzom_2nd"
I suspect that both clients otherwise access the same config and/or log files and there is some form of race between the two.
Now it's running smoothly.
I had to create a secondary directory from where you launch the second client and create a symbolic link to the data directory, then copy the remaining files, including the binaries. You can do:
cd <your directory containing the "ryzom" install directory>
mv ryzom/data backup_data
cp -R ryzom ryzom_2nd
mv backup_data ryzom/data
cd ryzom_2nd
ln -s ../ryzom/data data
Then you run one client from "ryzom" and the other from "ryzom_2nd"
I suspect that both clients otherwise access the same config and/or log files and there is some form of race between the two.
Now it's running smoothly.
---