On 06/13/2012 10:39 AM, Richard Doyle wrote:
>> E: [pulseaudio] module-console-kit.c: GetSessionsForUnixUser() call
>> failed: org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute
>> program /usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success
>> E: [pulseaudio] module.c: Failed to load module "module-console-kit"
>> (argument: ""): initialization failed.
>
> Are consolekit, dbus and hal running on your server?
>
> Google says that
>
> rm -rvf ~/.pulse/
>
> and then a reboot solved it (for some folks).
The quoted errors came from trying to start pulseaudio on the thin
client. So I'll answer about the thin client instead of the LTSP server:
hal - is not running, and I don't think it should be.
[hal has been deprecated in favour of udev since
Ubuntu 10.04 -- according to Wikipedia.]
dbus - had some issues. Before posting my original query,
I added the Ubuntu package dbus-x11 to the chroot
because it seemed like the command "dbus-launch"
that it provides might be of some use. But in short,
yes, it's running.
consolekit - does not start by default. But in the thin client
I can say "sudo /usr/sbin/console-kit-daemon start" and
this seems to "stick" when I check with "ps aux". Once
I do this, the thin client command "pulseaudio -D"
starts the daemon OK. This establishes my operating
state for the rest of this reply.
Both the thin client and the LTSP-server include files named
~/.pulse-cookie, and these files appear to be identical.
On the LTSP-server, pulseaudio does not get started when I log in from
the thin client. However, the environment variable PULSE_SERVER is set.
Saying "pulseaudio --start" gives an error message quoted earlier;
saying just "pulseaudio" starts the system with no error message, but
the thin client doesn't seem to receive any sounds, either.
I tried installing pavucontrol in the chroot for the thin client. After
manually starting pulseaudio on the thin client, I can use the thin
client command "aplay" to play .WAV files. They sound fine, and the
GUI of pavucontrol reacts -- suggesting that the thin client's
pulseaudio setup is correctly hooked into the pipeline that links a
player application on the TC to the audio hardware on the TC.
I also read on Google that cleansing one's home directory of all files
and directories named .pulse* might solve the problem. The folks for
whom that works are luckier than I am, I guess -- it didn't do the job
for me. Unfortunately I am still stuck.
Thanks a lot for the suggestions, though.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_____________________________________________________________________
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
