| 2010-04-24 11:49:48 |
Chow Loong Jin |
bug |
|
|
added bug |
| 2010-04-26 17:54:40 |
Daniel T Chen |
pulseaudio (Ubuntu): status |
New |
Triaged |
|
| 2010-04-26 17:54:45 |
Daniel T Chen |
pulseaudio (Ubuntu): importance |
Undecided |
Low |
|
| 2010-04-26 23:08:14 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-core-dev/pulseaudio/ubuntu.2a |
|
| 2010-04-26 23:13:14 |
Daniel T Chen |
summary |
Having multiple pulseaudio instances open causes physical sinks to be muted upon resume |
Short-circuit in pm-utils hook can cause incorrect mixer state to be (re)stored |
|
| 2010-04-26 23:21:18 |
Daniel T Chen |
description |
Binary package hint: pulseaudio
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. |
-- Lucid SRU report follows --
Impact: A short-circuit in PulseAudio's pm-utils hook to check for the ConsoleKit active seat when (re)storing sink and source states can result in the wrong states being stored. (This change was introduced for suspend-to-* and resume optimization.)
Bug resolution: By removing the ConsoleKit active seat check from the hook, PulseAudio will now (re)store sink and source states for all users that have a PA daemon. This change has been made in revision 290: http://bazaar.launchpad.net/~ubuntu-core-dev/pulseaudio/ubuntu.2a/revision/290
Minimal patch: http://bazaar.launchpad.net/%7Eubuntu-core-dev/pulseaudio/ubuntu.2a/diff/290
TEST CASE: Detailed below in the original defect report
Regression potential: Suspend-to-* and resume will require [negligibly] more time. Otherwise, there are no identified regressions.
-- Original defect report follows --
Binary package hint: pulseaudio
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.
|
|
| 2010-04-26 23:22:39 |
Daniel T Chen |
nominated for series |
|
Ubuntu Lucid |
|
| 2010-04-26 23:22:39 |
Daniel T Chen |
bug task added |
|
pulseaudio (Ubuntu Lucid) |
|
| 2010-04-26 23:23:12 |
Daniel T Chen |
pulseaudio (Ubuntu Lucid): milestone |
|
lucid-updates |
|
| 2010-04-26 23:23:24 |
Daniel T Chen |
pulseaudio (Ubuntu Lucid): assignee |
|
Daniel T Chen (crimsun) |
|
| 2010-04-26 23:23:33 |
Daniel T Chen |
pulseaudio (Ubuntu Lucid): status |
Triaged |
Fix Committed |
|
| 2010-04-27 23:09:38 |
Launchpad Janitor |
branch linked |
|
lp:~crimsun/pulseaudio/ubuntu.2a |
|
| 2010-04-27 23:38:48 |
Daniel T Chen |
description |
-- Lucid SRU report follows --
Impact: A short-circuit in PulseAudio's pm-utils hook to check for the ConsoleKit active seat when (re)storing sink and source states can result in the wrong states being stored. (This change was introduced for suspend-to-* and resume optimization.)
Bug resolution: By removing the ConsoleKit active seat check from the hook, PulseAudio will now (re)store sink and source states for all users that have a PA daemon. This change has been made in revision 290: http://bazaar.launchpad.net/~ubuntu-core-dev/pulseaudio/ubuntu.2a/revision/290
Minimal patch: http://bazaar.launchpad.net/%7Eubuntu-core-dev/pulseaudio/ubuntu.2a/diff/290
TEST CASE: Detailed below in the original defect report
Regression potential: Suspend-to-* and resume will require [negligibly] more time. Otherwise, there are no identified regressions.
-- Original defect report follows --
Binary package hint: pulseaudio
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.
|
-- Lucid SRU report follows --
Impact: A short-circuit in PulseAudio's pm-utils hook to check for the ConsoleKit active seat when (re)storing sink and source states can result in the wrong states being stored. (This change was introduced for suspend-to-* and resume optimization.)
Bug resolution: Prior to suspend-to-*, save all PA users' sink & source states and then mute only the active ConsoleKit seat's sink & source. After resume, restore all PA users' pre-suspend sink & source states. This change has been made in revision 292: http://bazaar.launchpad.net/~ubuntu-core-dev/pulseaudio/ubuntu.2a/revision/292?remember=284&compare_revid=284 .
Minimal patch: http://bazaar.launchpad.net/%7Eubuntu-core-dev/pulseaudio/ubuntu.2a/diff/292/284?remember=284
TEST CASE: Detailed below in the original defect report
Regression potential: Suspend-to-* and resume will require [negligibly] more time. Otherwise, there are no identified regressions.
-- Original defect report follows --
Binary package hint: pulseaudio
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.
|
|
| 2010-05-08 15:15:10 |
Launchpad Janitor |
pulseaudio (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2010-05-08 16:15:32 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/pulseaudio |
|
| 2011-09-19 21:14:35 |
Ubuntu Foundations Team Bug Bot |
tags |
|
testcase |
|
| 2015-06-17 11:35:32 |
Rolf Leggewie |
pulseaudio (Ubuntu Lucid): status |
Fix Committed |
Won't Fix |
|
