Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Meranor

Pages: [1]
1
Linux Specific Issues / Re: [solved] No sound with Client 0.3.016 on SuSE 10.0 with alsa-1.0.12-0.pm.0
« on: September 19, 2006, 07:21:37 pm »
Quote from: Xordan on September 19, 2006, 01:10:33 pm
Remember to run fixlibs.sh after updating.

Are you sure? The fixlibs.sh script has been moved away into 'moved/' by the last update...
I'd have read this as "Donot use anymore"...

Meranor

2
Linux Specific Issues / Re: [solved] No sound with Client 0.3.016 on SuSE 10.0 with alsa-1.0.12-0.pm.0
« on: September 17, 2006, 01:21:26 am »
Quote from: Bereror on September 15, 2006, 09:20:48 pm
The main reason is to stop people complaining that libraries are not delivered with the system ;)

Ok, but could the installer maybe check, if an appropriate version is already installed? And only if not, download and install the other version?

Meranor

3
Linux Specific Issues / [solved] No sound with Client 0.3.016 on SuSE 10.0 with alsa-1.0.12-0.pm.0
« on: September 15, 2006, 09:00:50 pm »
Hi!

Just discovered, that the PlaneShift sound system stopped working on my system (see above). It's caused by the fact that the Linux client comes with its own 1.0.11 (!=1.0.12) version of ALSA. The error message I get is:
Code: [Select]
DEBUG: Sound System Software Renderer Initializing...
ALSA lib pcm_direct.c:224:(make_local_socket) connect failed: �Z/tmp/alsa-dmix-7347-1158337114-512350: Directory or file not found
ALSA lib pcm_dmix.c:894:(snd_pcm_dmix_open) unable to connect client

Please note the very strange characters before "/tmp/alsa-dmix..."! Looks like a binary incompatibility...

Solution:
Remove the offending files "libs/libasound.so.*" in the PlaneShift directory.

Honestly speaking, I find it questionable to deliver such system libraries with the client. Is there a convincing reason?

Cheers,

Meranor's guiding spirit


Pages: [1]