[Touch-packages] [Bug 569526] Re: Having multiple pulseaudio instances open causes physical sinks to be muted upon resume

2017-05-08 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 569526

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Changed in: pulseaudio (Ubuntu)
   Status: Triaged => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/569526

Title:
  Having multiple pulseaudio instances open causes physical sinks to be
  muted upon resume

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
affects ubuntu/pulseaudio
status triaged

  I noticed this the other day after accidentally going into "Switch User" 
mode: I
  had my own pulseaudio instance, and gdm had its own. I then suspending my
  machine, and upon resuming, sound was muted.

  The reason for this happening is due to a bug in the 01Pulseaudio pm-utils 
hook.
  1. First, it checks the status of gdm's pulseaudio, stores it, then mutes it.
  2. Then, it checks the status of my pulseaudio, stores it, and also mutes it.
  Due to #1, the sink is already muted, as both sinks were pointing to the same
  physical device. Hence, the stored states are as follows: gdm's sink is not
  muted, but mine is.

  Upon resuming:
  1. It reads gdm's state, and unmutes the sink.
  2. Then it reads my pulseaudio's saved state, and mutes the sink again.

  Result: The sink is muted after resuming from suspend.

  N.B.:
  This seems to be a corner case that only occurs when multiple pulseaudio
  instances are running, and both contain sinks pointing to the same underlying
  device. It can probably be fixed by changing the pm-utils hook order to read 
and
  store all the states of the sinks prior to muting them.

  -- 
  Kind regards,
  Chow Loong Jin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/569526/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 569526] Re: Having multiple pulseaudio instances open causes physical sinks to be muted upon resume

2017-07-07 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/569526

Title:
  Having multiple pulseaudio instances open causes physical sinks to be
  muted upon resume

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
affects ubuntu/pulseaudio
status triaged

  I noticed this the other day after accidentally going into "Switch User" 
mode: I
  had my own pulseaudio instance, and gdm had its own. I then suspending my
  machine, and upon resuming, sound was muted.

  The reason for this happening is due to a bug in the 01Pulseaudio pm-utils 
hook.
  1. First, it checks the status of gdm's pulseaudio, stores it, then mutes it.
  2. Then, it checks the status of my pulseaudio, stores it, and also mutes it.
  Due to #1, the sink is already muted, as both sinks were pointing to the same
  physical device. Hence, the stored states are as follows: gdm's sink is not
  muted, but mine is.

  Upon resuming:
  1. It reads gdm's state, and unmutes the sink.
  2. Then it reads my pulseaudio's saved state, and mutes the sink again.

  Result: The sink is muted after resuming from suspend.

  N.B.:
  This seems to be a corner case that only occurs when multiple pulseaudio
  instances are running, and both contain sinks pointing to the same underlying
  device. It can probably be fixed by changing the pm-utils hook order to read 
and
  store all the states of the sinks prior to muting them.

  -- 
  Kind regards,
  Chow Loong Jin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/569526/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp