I am using Karmic Koala right now: fully updated till date and I still
have this problem. I have successfully reproduced this bug nearly 10
times now; not hard I know. But proof it still exists(no pulseaudio
update: I just checked for any updates now).
--
sound is muted before suspend, but on
I just checked it and it's still existent. verified it's existence so
changing it to confirmed.
** Changed in: pulseaudio (Ubuntu)
Status: Fix Released = Confirmed
--
sound is muted before suspend, but on resume is not muted
https://bugs.launchpad.net/bugs/483900
You received this bug
If this is intended to be fixed for Karmic perhaps we should open up a
distro task, but this is fixed for me as the original reporter out of
the box on Lucid, so I believe the Fix Released is still valid.
** Changed in: pulseaudio (Ubuntu)
Status: Confirmed = Fix Released
--
sound is
Arvind, unless you're running Lucid, you should change this status
back to Fix Released. This bug report deals very specifically with a
script error, not a hardware error. You would need to file a separate
bug report.
--
sound is muted before suspend, but on resume is not muted
Regrettably, the PPA actually prevents the system from suspending. So
it's quite difficult to tell if the fix for this bug really fixed
anything, or simply inhibits suspend.
--
sound is muted before suspend, but on resume is not muted
https://bugs.launchpad.net/bugs/483900
You received this bug
If this bug is fixed, how come when I have applied all updates, I still
do not have any sound?
Rolfe Pope
--
sound is muted before suspend, but on resume is not muted
https://bugs.launchpad.net/bugs/483900
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@rolfepope: This bug is about the sound being unmuted after a
suspend/resume cycle although it was muted before suspending. So, not
getting any sound at all is a different story. I'd propose to file a
separate bug (if there is not already an existing one).
Apart from that, would it be possible to
s/packport/backport/
--
sound is muted before suspend, but on resume is not muted
https://bugs.launchpad.net/bugs/483900
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
See the ubuntu-audio-dev PPA
On Nov 29, 2009 5:45 PM, Thilo-Alexander Ginkel th...@ginkel.com
wrote:
@rolfepope: This bug is about the sound being unmuted after a
suspend/resume cycle although it was muted before suspending. So, not
getting any sound at all is a different story. I'd propose to
This bug was fixed in the package pulseaudio - 1:0.9.21-0ubuntu1
---
pulseaudio (1:0.9.21-0ubuntu1) lucid; urgency=low
[ Daniel T Chen ]
* New upstream bugfix release
* debian/control: pulseaudio-module-raop must Depends
pulseaudio-module-zeroconf (LP: #484870). Thanks,
As per https://wiki.ubuntu.com/Bugs/Importance I'll change this
importance to Low, as it certainly is not a request for a new feature
but in fact a regression.
** Changed in: pulseaudio (Ubuntu)
Importance: Wishlist = Low
** Tags added: regression-release
--
sound is muted before suspend,
Michael, I am happy to reassign this bug to you if you feel that you
wish to implement the feature in PulseAudio.
--
sound is muted before suspend, but on resume is not muted
https://bugs.launchpad.net/bugs/483900
You received this bug notification because you are a member of Ubuntu
Bugs, which
As a triager I am going by the Importances on the wiki. If you'd like
to not classify this is a regression in pulseaudio but instead a new
feature, then there needs to be some task against which we CAN
classify this as a regression becacuse at the distribution level, it
is a regression with a
The symptom points to a regression in pulseaudio's pm-utils script.
Removing the added functions will fix *this* bug and reopen the original
audio anomaly bug. Fixing the symptom requires the addition of features
to both pulseaudio and linux.
--
sound is muted before suspend, but on resume is
Ah okay, thanks for your input. One of the bugs that was marked as a
duplicate of this had a pm-utils task, if that task is valid, does it
make sense to migrate that task to this master report?
--
sound is muted before suspend, but on resume is not muted
https://bugs.launchpad.net/bugs/483900
A pm-utils task would be invalid.
--
sound is muted before suspend, but on resume is not muted
https://bugs.launchpad.net/bugs/483900
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Branch linked: lp:~crimsun/pulseaudio/ubuntu
--
sound is muted before suspend, but on resume is not muted
https://bugs.launchpad.net/bugs/483900
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: pulseaudio (Ubuntu)
Status: Triaged = Fix Committed
--
sound is muted before suspend, but on resume is not muted
https://bugs.launchpad.net/bugs/483900
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Branch linked: lp:~hyperair/pulseaudio/ubuntu-save-muted-state
--
sound is muted before suspend, but on resume is not muted
https://bugs.launchpad.net/bugs/483900
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
For those interested, I've made some changes to the existing
01Pulseaudio script, which now reads the muted state of each sink/source
and saves it using pm-utils' savestate and restorestate features. This
should provide an answer to both issues, i.e. glitches in sound when
** Summary changed:
- HP Mini 311 - sound is muted before suspend, but on resume is not muted
+ sound is muted before suspend, but on resume is not muted
--
sound is muted before suspend, but on resume is not muted
https://bugs.launchpad.net/bugs/483900
You received this bug notification
Thanks Daniel for merging my bug report.
So this is a hardware-specific issue? If that's the case, then in the
interest of usability, shouldn't we keep the old behaviour and wait for
hardware to comply with software?
On second thought - wouldn't it be easier if the current state of PA
On Thu, Nov 19, 2009 at 12:57 PM, Julian Lam julian@gmail.com wrote:
So this is a hardware-specific issue? If that's the case, then in the
interest of usability, shouldn't we keep the old behaviour and wait for
hardware to comply with software?
No, the all unmuted behavior is caused by
23 matches
Mail list logo
