Ryzom FV 2.1.0.6447 fails to start - Entraide GNU/Linux

#22 Ajouté par Xiombarg il y a 9 ans [en]

Hum, your error is very strange, I'll try to test it tomorrow.

gamedev.bnp from RSYNC should support Lua 5.2 and 5.3, Ubuntu client is compiled against Lua 5.2.

---

Kervala - Ryzom volunteer developer - Working on different clients

#23 Ajouté par Xiombarg il y a 9 ans [en]

{translate}

I just tried client from PPA under Ubuntu 15.10 and it worked fine.

I'll try client under Ubuntu 14.04 on my laptop.

---

Kervala - Ryzom volunteer developer - Working on different clients

#24 Ajouté par Xiombarg il y a 9 ans [en]

{translate}

I just tested the 2.1.0.6447-0ubuntu1~trusty1 under Ubuntu 14.04 LTS and it worked perfectly.

Only thing I noticed is that FXAA is enabled by default and you can't switch off in game config :(

If it's slowing down your game, you can disable it adding :

FXAA = 0;

In your ~./ryzom/client.cfg

Dernière édition par Xiombarg (il y a 9 ans).

---

Kervala - Ryzom volunteer developer - Working on different clients

#25 Ajouté par Sennuri il y a 9 ans [en]

{translate}

It's not working at all. I tried disabling FXAA anyway, but wasn't expecting anything because Ryzom quits before showing the login screen (before showing any 3D).
Any other ideas? It worked fine until yesterday, when I got the update through the regular Update Manager.

I also tried an uninstall, removed the .ryzom dir, and reinstalled. Still no luck.

Dernière édition par Sennuri (il y a 9 ans).

#26 Ajouté par Xiombarg il y a 9 ans [en]

{translate}

What graphics driver are you using ?

How do you launch the game ?

There should be only 2 ways to launch Ryzom Ubuntu clients :

1. click on Ryzom icon in Unity
2. open a terminal and type : /opt/ryzom/ryzom.sh

All others ways to launch client should be prohibited until you know what you do.

If no way is working, you could have corrupted files, so you should move these files in a backup directory :

1. ~/.ryzom/client.cfg
2. ~/.ryzom/user
3. ~/.ryzom/save

All files in data will be checked by RSYNC and downloaded if modified.

If you modified /opt/ryzom/ryzom_client, I suggest you to reinstall the package because new static clients are in beta test and are not compatible with ones in PPA :)

---

Kervala - Ryzom volunteer developer - Working on different clients

#27 Ajouté par Sennuri il y a 9 ans [en]

{translate}

I'm using an AMD HD5450 with Catalyst drivers (fglrx 15.200). But if this is a driver issue, remember that the game worked perfectly before this update. And the video driver did NOT get an update recently, so it's the game that stopped working, not the driver.

Icon: splash screen shows, then quits, no error message.
Script: quits without error message, but somehow closes the terminal window completely.

I do not have corrupted files, I just told you I deleted the ryzom folder. I also just told you I already reinstalled the game without succes, so I did not try a modified client.

Sorry if I seem a bit edgy, but to me it seems as if you don't pay much attention to what I write. Just as in your previous message about FXAA slowing down my game, while you know I can't start the game at all right now.

#28 Ajouté par Karu il y a 9 ans [en]

{translate}

Sennuri

Icon: splash screen shows, then quits, no error message.
Script: quits without error message, but somehow closes the terminal window completely.

Delete ~/.ryzom/log.log file, run client and then post content of that file to http://pastebin.com/

It's would also help if you could run ryzom from terminal to see if it outputs any messages.

If it's 'PANIC: unprotected error in call to Lua API (attempt to index a nil value)', then you need new client

---

Hello!

#29 Ajouté par Sennuri il y a 9 ans [en]

{translate}

I posted the log here, easier for me than pastebin.
And the error msg you posted is exactly what I get, the same as I posted yesterday.

What do you mean by new client? A reinstall of version 6447 didn't solve the problem. Do I need a newer version?

#30 Ajouté par Karu il y a 9 ans [en]

{translate}

Sennuri

I posted the log here, easier for me than pastebin.
And the error msg you posted is exactly what I get, the same as I posted yesterday.

Thats strange. You have Ubuntu trusty (14.04) fully updated, you using ryzom-isv ppa (version 2.1.0.6447-0ubuntu1~trusty1 amd64)... and it does not work.

I see that you running /opt/ryzom/ryzom_client directly. Have you tried running /opt/ryzom/ryzom.sh to make sure ryzom files are updated?

Dernière édition par Karu (il y a 9 ans).

---

Hello!

#31 Ajouté par Sennuri il y a 9 ans [en]

{translate}

I'm not running the client directly. I posted the results I get when clicking on the icon, when starting the .sh script, and when starting the client directly. When you asked me to post the log, I started Ryzom from the icon.

Dernière édition par Sennuri (il y a 9 ans).

#32 Ajouté par Karu il y a 9 ans [en]

{translate}

Can you run and post the results?

ldd /opt/ryzom/ryzom_client | grep lua

It should be something like this

liblua5.2.so.0 => /usr/lib/x86_64-linux-gnu/liblua5.2.so.0 (0x00007f8de6b51000)
libluabind.so.0.9.1 => /usr/lib/libluabind.so.0.9.1 (0x00007f8de6934000)

Also to verify ryzom_client, could you run

md5sum /opt/ryzom/ryzom_client

and see if it matches

e5c60d198d52e9882d0595156ebc2f6c  /opt/ryzom/ryzom_client

---

Hello!

#33 Ajouté par Sennuri il y a 9 ans [en]

{translate}

arumes@RMS-DESK:~$ ldd /opt/ryzom/ryzom_client | grep lua

    liblua5.1.so.0 => /usr/lib/x86_64-linux-gnu/liblua5.1.so.0 (0x00007f4bf3db3000)

    libluabind.so.0.9.1 => /usr/lib/libluabind.so.0.9.1 (0x00007f4bf3b96000)

    liblua5.2.so.0 => /usr/lib/x86_64-linux-gnu/liblua5.2.so.0 (0x00007f4bf07bd000)

arumes@RMS-DESK:~$ md5sum /opt/ryzom/ryzom_client

390718c47ede6e47a4ef8d665a1ac52c /opt/ryzom/ryzom_client

So there's no match. For now, I'll just switch back to the previous version, because I think the problem lies with the PPA, not with my system. And now that I'm switching back, I notice that the version you mentioned is the 'old' version. The latest version for 14.04 is called 2.1.0.6447-0ubuntu1, so without the "~trusty1" at the end. Now that I reverted the upgrade, Ryzom is working again:

Could you take this up with the maintainer of the PPA? Seems like that's where the problem is.

Dernière édition par Sennuri (il y a 9 ans).

#34 Ajouté par Xiombarg il y a 9 ans [en]

{translate}

I'm sorry, I just understood what happened :p

Canonical finally updated Ryzom from Ubuntu Software Center but they applied the wrong version for Ubuntu 14.04 :( So there is a conflict between the 2 versions.

For the moment, I suggest you to uninstall the one from Ubuntu Software Center and reinstall the one from the ryzom-isv PPA.

Since I could again talk to a Canonical employee, we'll be able to fix this problem :)

Thanks for discovering it :)

---

Kervala - Ryzom volunteer developer - Working on different clients

#35 Ajouté par Dukenono il y a 9 ans [fr]

{translate}

Xiombarg

Canonical finally updated Ryzom from Ubuntu Software Center...

C'est une bonne nouvelle si ça bouge enfin chez Canonical.

---

Ducocinnio Nono, dit Duke Nono
Noble Matis, artisan de la maison noble La Firme
Gardien du Royaume et Béni de Jena

#36 Ajouté par Xiombarg il y a 9 ans [en]

{translate}

The problem that was happening is the following :

They applied the client for Precise (12.04) to all Ubuntu versions.

Under Precise, Ryzom was using Luabind linked against Lua 5.1, under Trusty Luabind is compiled against Lua 5.2.

So it tries to mix both Lua 5.1 and 5.2, which is creating these crashes :s

To fix your problem, I'm compiling new versions on PPA for Precise and Trusty (version 2.1.0.6449) with no changes in code but since version is greater, it shouldn't have conflicts anymore :)

Next step is to contact the Canonical Employee and explain to her that we are using dynamic linking and she shouldn't copy Precise package for all other Ubuntu versions.

---

Kervala - Ryzom volunteer developer - Working on different clients