Hilfe Zu GNU/Linux

Thanks to all of you for your responses.

As for graphics drivers, I have installed a driver from Additional Drivers section, but now I can't see what it was. It says: "No proprietary drivers are in use on this system" and doesn't offer any options like before it showed two. Don't know what's wrong here.

On top of all, the internet connection I used to use is gone now and I've been using a wifi through my phone and it happens to be quite selective of the connections it allows. I'm unable to download anything from the Software Center and I'm afraid that even if I could get Ryzom to work, it might not allow the connection for it. This is due to the software on my phone doesn't allow certain types of connections in the free version of the software and the price for the full version is simpy too high for me right now.

I'll try to download the static Linux client and report back to you.

Downloaded the 64bit static Linux version and here's what it said:

susa@ASUS-U35JC:~/Desktop/RyzomStatic$ ./ryzom_client_static64_2.0-1
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib pcm_dmix.c:957:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib pcm_dmix.c:957:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib audio/pcm_bluetooth.c:1614:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
ALSA lib pcm_dmix.c:957:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
ERR f47e5740 client_cfg.cpp 1954 init <Unknown> : cannot find client_default.cfg
-------------------------------

Log with no filter:
-------------------------------

Log Starting [2012/12/09 02:29:42]
2012/12/09 02:29:42 <Unknown> INF f47e5740 client.cpp 552 : Pre-Login Init of Ryzom...
2012/12/09 02:29:42 <Unknown> DBG f47e5740 time_nl.cpp 271 : Timer resolution: 1000000000 Hz
2012/12/09 02:29:42 <Unknown> DBG f47e5740 time_nl.cpp 272 : Time identical: 0, backwards: 0, regular: 128, skipping: 0, frequency bug: 0
2012/12/09 02:29:42 <Unknown> INF f47e5740 init.cpp 404 : CPUInfo: CPUMask before change: 0, after change: 0, CPUID: 0, hasHyperThreading: NO
2012/12/09 02:29:42 <Unknown> INF f47e5740 init.cpp 740 : RYZOM VERSION : FV RYZOM CORE (Oct 13 2012 21:38:02)
2012/12/09 02:29:42 <Unknown> ERR f47e5740 client_cfg.cpp 1954 : cannot find client_default.cfg
-------------------------------
User Crash Callback:
-------------------------------
UserId: 4294967295
HomeId: 0
ShardId: 0
On a Mainland Shard
Application: NotFound
No user entity information
ViewPosition: 0.00 0.00 0.00
Time in game: 0h 0min 0sec
LocalTime: 2012/12/09 02:29:42
ServerTick: 0
ConnectState: NotInitialised
LocalAddress: :0 (0.0.0.0)
Language: <NotExist:LanguageName>
ClientVersion: RYZOM CORE
PatchVersion:
Client is online
NumServerHOP: 0
NumFarTP: 0
NumReselectPerso: 0
Connection Events:
Memory: 2987MB/3744MB
Process Virtual Memory: 0B
OS: Linux version 3.2.0-34-generic (buildd@allspice) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #53-Ubuntu SMP Thu Nov 15 10:48:16 UTC 2012
Processor: Intel(R) Core(TM) i3 CPU M 370 @ 2.40GHz / ? Family 6 Model 37 Stepping 5 / GenuineIntel / 933.000MHz / 4 Processors found
CPUID: 0
HT: NO
CpuMask: f
NeL3D: No driver
No sound
-------------------------------
Aborted (core dumped)

The last line of the error log hints at a missing client_default.cfg: Did you drop the static client into a new, empty directory?

Before you start it, try to change your working to your ryzom install directory. The client needs to find its config files. Use the "cd" command inside the terminal to do that. Then start the client by using the full path ~/Desktop/RyzomStatic/ryzom_client_static64_2.0-1
Even better: move the static client into the ryzom install directory, then cd into that directory and use ./ryzom_client_static64_2.0-1

That should remove the problems with missing configs.


Then you also seem to have lots of issues with your sound setup. As I presume the client still does not open up, you need to change any config settings by starting a text editor and modifying the config files. Edit the default_config.cfg and disable sound completely. Currently I can't lookup the exact line to change. Then retry to start.

I moved the static client to the install folder and ran it, but it still says the client_default.cfg is missing. Also tried to edit the .cfg to disable sound but there's no difference.

Does the file exist?
If you cd into the install folder, then type a

find . -name client_default.cfg

what's the output?

it does exist and that's where I edited the sound, but now it's in the original state.

I might be a bit late but just regarding this pat of the issue:

client_default.cfg is the default configuration and not supposed to be edited.
If you want to change the settings try client.cfg instead (if a setting doesn't exist just copy it from the default)


----

I can't really help you regarding your general problem as I usually play on a windows machine...
but: since you have a 64bit system it might be that some libraries are 64bit and needed as 32bit (or the other way around after your switch to the 64bit client)

In addition to that:
Who is the owner of the client_default.cfg and what rights are set for it? (on command line go to the directory and do "ls -l", of course without the quotes, to get the full list)
Is it the same as your user or another one?

I was wondering what ever happened to you Likka. Sadly I'm not a computer expert and don't have anything more than some encouragement. I hope you can get it fix soon, and hope to see you back in witherings. Good luck!