Re: [Ltsp-discuss] debian 7 thin client audio

Sat, 08 Jun 2013 19:15:10 -0700

Roland,

On 09/06/13 00:22, Roland Giesler wrote:
Hi Michael,

On Sat, Jun 8, 2013 at 5:05 AM, you wrote:
I've just setup a Debian 7 LTSP server with some thin clients

I have pulseaudio & libasound2-plugins installed in the client image
(and have rebuilt it).

I'm not getting sound from the client.

I tried putting this into the client image file: /etc/asound.conf
pcm.!default {
type pulse
}

ctl.!default {
type pulse
}

Still no go.

I've also put the following into my lts.conf file


Should I be using pulseaudio at all?
[Default]
SOUND_DAEMON=pulse
SOUND = true
LDM_LANGUAGE=en_AU.utf8

 
I presume your client is booting successfully? If so, you should see what your log says.  If you put SCREEN_08=shell into your lts.conf, you will be able to press <ctrL><alt><F8> on the client and inspect the local log at /var/log/syslog.  That would give you some indication of what it going wrong.

regards

Roland Giesler

I think the problem is to do with pulseaudio starting, here the tail of my syslog on the client:

Jun  9 11:11:06 ltsp191 /usr/sbin/cron[3009]: (CRON) INFO (pidfile fd = 3)
Jun  9 11:11:06 ltsp191 /usr/sbin/cron[3012]: (CRON) STARTUP (fork ok)
Jun  9 11:11:06 ltsp191 /usr/sbin/cron[3012]: (CRON) INFO (Running @reboot jobs)
Jun  9 11:11:06 ltsp191 kernel: [   17.208048] eth0: no IPv6 routers present
Jun  9 11:11:07 ltsp191 pulseaudio[3117]: [pulseaudio] main.c: Running in system mode, but --disallow-exit not set!
Jun  9 11:11:07 ltsp191 pulseaudio[3117]: [pulseaudio] main.c: Running in system mode, but --disallow-module-loading not set!
Jun  9 11:11:07 ltsp191 pulseaudio[3117]: [pulseaudio] main.c: OK, so you are running PA in system mode. Please note that you most likely shouldn't be doing that.
Jun  9 11:11:07 ltsp191 pulseaudio[3117]: [pulseaudio] main.c: If you do it nonetheless then it's your own fault if things don't work as expected.
Jun  9 11:11:07 ltsp191 pulseaudio[3117]: [pulseaudio] main.c: Please read http://pulseaudio.org/wiki/WhatIsWrongWithSystemMode for an explanation why system mode is usually a bad idea.
Jun  9 10:40:21 ltsp191 ntpdate[2488]: step time server 192.168.200.1 offset -1848.027901 sec
Jun  9 10:40:34 ltsp191 kernel: [   32.526936] fuse init (API version 7.17)
Jun  9 10:40:35 ltsp191 pulseaudio[3117]: [pulseaudio] x11wrap.c: XOpenDisplay() failed
Jun  9 10:40:35 ltsp191 pulseaudio[3117]: [pulseaudio] module.c: Failed to load module "module-x11-publish" (argument: "display=192.168.200.191:7.0"): initialization failed.
Jun  9 10:40:36 ltsp191 ntpdate[3219]: adjust time server 192.168.200.1 offset 0.000125 sec
Jun  9 10:40:54 ltsp191 pulseaudio[3117]: [alsa-sink] protocol-native.c: Failed to push data into queue
Jun  9 10:41:05 ltsp191 dbus[3016]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper)
Jun  9 10:41:05 ltsp191 dbus[3016]: [system] Activated service 'org.freedesktop.ConsoleKit' failed: Failed to execute program /usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success
Jun  9 10:41:30 ltsp191 pulseaudio[3117]: [alsa-sink] protocol-native.c: Failed to push data into queue

I think this was started from this file: /opt/ltsp/i386/user/bin/start-pulseaudio-x11

I don't have the port 4713 open on the client, should it be?
It's failing to bind to my clients X11 display. This would make sense as when I try and adjust the volume on the client it adjusts the volume on the server instead.

192.168.200.191 is my clients IP & the display is set on '7'.



from
Michael
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Reply via email to