Hej!
Thanks for your answer!
Yeah, of coarse I read that page, and I have seen what you point out there.
Though I didn't believe this was valid for fat clients...
And what does it mean? For the ability to get sound on my fat clients? Do I need to implement the steps described in:
"Running PulseAudio as System-Wide Daemon"
Like adding pulse as a user and group, etc?Do you really mean that sound is not on by default, when you install fat clients?
Or have I misinterpreted you here...?
If I have misinterpret you(which I hope), what have I done wrong to get my sound not to work?
Best regards from/Med vänliga hälsningar från
Johan Kragsterman
Capvert
-----Vagrant Cascadian <vagr...@debian.org> skrev: -----
Till: ltsp-discuss@lists.sourceforge.net
Från: Vagrant Cascadian <vagr...@debian.org>
Datum: 2014-04-10 22:09
Ärende: Re: [Ltsp-discuss] Ang: no sound on fat clients
Från: Vagrant Cascadian <vagr...@debian.org>
Datum: 2014-04-10 22:09
Ärende: Re: [Ltsp-discuss] Ang: no sound on fat clients
On Thu, Apr 10, 2014 at 02:55:47PM +0200, Johan Kragsterman wrote:
> I give myself, and you other guys a hint, since I found this on pulseaudio in
> system mode:
>
> http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/
> WhatIsWrongWithSystemWide/
If you read that page, you'll see:
"System mode is around for usage on thin client or embedded setups, wher no
real local user exists, where access is exclusively via the network, and
where state data is flushed on each session termination."
So this actually is appropriate. Not sure we flush state data on each session
termination though... and even though we're using pulseaudio in one of the
use-cases appropriate for system mode, there's no way to turn off the warning.
We could potentially rewrite some things and actually start per-user pulseaudio
daemons since we tend to actually have a local user (due to localapps or
fatclients), but LTSP5 is essentially in maintenance mode, and would rather
move major feature development towards LTSP6...
live well,
vagrant
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_____________________________________________________________________
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
> I give myself, and you other guys a hint, since I found this on pulseaudio in
> system mode:
>
> http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/
> WhatIsWrongWithSystemWide/
If you read that page, you'll see:
"System mode is around for usage on thin client or embedded setups, wher no
real local user exists, where access is exclusively via the network, and
where state data is flushed on each session termination."
So this actually is appropriate. Not sure we flush state data on each session
termination though... and even though we're using pulseaudio in one of the
use-cases appropriate for system mode, there's no way to turn off the warning.
We could potentially rewrite some things and actually start per-user pulseaudio
daemons since we tend to actually have a local user (due to localapps or
fatclients), but LTSP5 is essentially in maintenance mode, and would rather
move major feature development towards LTSP6...
live well,
vagrant
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_____________________________________________________________________
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
------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees
_____________________________________________________________________
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
