xpra icon
Bug tracker and wiki

Changes between Initial Version and Version 1 of Ticket #1001


Ignore:
Timestamp:
10/14/15 08:56:31 (5 years ago)
Author:
Antoine Martin
Comment:

I can't guarantee that I will get around to fixing this bug as the focus is now on 0.16.x which has improved sound forwarding support, and in particular more reliable process monitoring.

The problem here is that communicating with the sound process over pipes is inherently racy with sending signals for killing it. Not an easy problem to solve.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1001

    • Property Status changed from new to assigned
  • Ticket #1001 – Description

    initial v1  
    11System: both Ubuntu 14.04, Server 64bit client 32bit. Since xpra 0.15.6 and still here in 0.15.7. I do not leave pulse audio sound forwarding all the time, but turning it on and off several times in each session on demand, via system-tray gui menu. Sometimes, but not always, this command is left running on the server:
     2{{{
    230:00 /usr/bin/python /usr/bin/xpra _sound_record - - pulsesrc  wav  1.0 -d
     4}}}
    35even after turning off the sound. And after turning on the sound again, the old process till run. Indeed, even after client disconnect, the sound process still runs from the old session.
    46
     
    68
    79This does not seem to affect sound performances. So it's not a blocker bug. But I think it is probably better if the process
     10{{{
    811/usr/bin/python /usr/bin/xpra _sound_record - - pulsesrc  wav  1.0 -d
     12}}}
    913get turned off each time I turn off the sound. And certainly when a client disconnect from a session, all the sound processes related to that session should be terminated.
    1014
    1115This is forwarding speaker, not microphone.
    12 When starting the client, I have --speaker=off to begin with, and turn sound on and off on demand.
     16When starting the client, I have {{{--speaker=off}}} to begin with, and turn sound on and off on demand.