PULSE_SERVER not set for localapps
Bug #274902 reported by
Stéphane Graber
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ltsp (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
When starting a localapp from the server that will make use of the sound server, it can't access to pulseaudio because this one is listening only on TCP.
In order to make it work, the variable PULSE_SERVER has to be set to 127.0.0.1.
Attached is a patch to xrexecd fixing that.
Related branches
Revision history for this message
| Stéphane Graber (stgraber) wrote | #1 |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in ltsp: | |
| status: | New → Fix Released |
To post a comment you must log in.
This bug was fixed in the package ltsp - 5.1.25-0ubuntu1
---------------
ltsp (5.1.25-0ubuntu1) intrepid; urgency=low
* new upstream version (5.1.25)
* Allow users to shutdown the thin client (LP: #274803)
* Set PULSE_SERVER to 127.0.0.1 for localapps (LP: #274902)
* Fix --prompt-rootpass (LP: #255176)
* Use nbd-client with -persist to reconnect if server breaks
* Add ltsp-cluster option to ltsp-build-client
* Update documentation (LDM_RUNONCE)
* Fix cups support for localapps
* Set LDM_USERNAME correctly for localapps
* Create /var/cache/
* Rename xrexec to localapps
* update packaging for the xrexec => localapps change
-- Stephane Graber <email address hidden> Sat, 04 Oct 2008 22:44:16 -0400