This bug was fixed in the package pulseaudio - 1:4.0-0ubuntu11.1
---
pulseaudio (1:4.0-0ubuntu11.1) trusty; urgency=medium
* 0107-sink-source-Fix-restore-of-volume-on-devices-without.patch:
- Fix initial volume for sink (LP: #598308)
-- Ricardo Salveti de Araujo
I second this, a package for 14.04 would be highly welcome as at this
moment my Xonar card is just laying on a shelf without any use.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/598308
Title:
** Summary changed:
- Volume at login set to Maximum
+ Volume at login set to Maximum after a reboot
** Also affects: pulseaudio (Ubuntu Utopic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hello buddyd16, or anyone else affected,
Accepted pulseaudio into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:4.0-0ubuntu11.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package.
** Branch linked: lp:ubuntu/trusty-proposed/pulseaudio
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/598308
Title:
Volume at login set to Maximum after a reboot
To manage notifications about this
This update fixed the bug for me.
Tested pulseaudio 1:4.0-0ubuntu11.1 (amd64).
Hardware is Intel Corporation 82801I (ICH9 Family) HD Audio Controller,
using S/PDIF digital (coaxial) output.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug
** Description changed:
Release: Ubuntu 10.04 64-bit Desktop Edition
What You Expected to Happen: System volume to remain as set before reboot and
as shown in volume panel applet
What Happened Instead: After reboot/shutdown at and after login system volume
is set to maximum
** Changed in: pulseaudio (Ubuntu Trusty)
Status: New = In Progress
** Changed in: pulseaudio (Ubuntu)
Assignee: (unassigned) = Ricardo Salveti (rsalveti)
** Changed in: pulseaudio (Ubuntu Trusty)
Assignee: (unassigned) = Ricardo Salveti (rsalveti)
** Changed in: pulseaudio
Anyone? Chance of a backport to the current LTS release? It'd be nice to
have this fix included before 16.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/598308
Title:
Volume at login set to
Sorry for adding a comment to a 'fix released' bug, but, is there a plan
for the updated pulseaudio package to get backported to 14.04? I just
checked and it's on 1:4.0-0ubuntu11 with nothing in the updates
repository.
It would be nice to have this fix available for LTS.
--
You received this
** Branch linked: lp:ubuntu/utopic-proposed/pulseaudio
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/598308
Title:
Volume at login set to Maximum
To manage notifications about this bug go to:
This bug was fixed in the package pulseaudio - 1:4.0-0ubuntu19
---
pulseaudio (1:4.0-0ubuntu19) utopic; urgency=medium
* 0210-module-device-restore-adding-property-to-skip.patch:
- Adding property to skip device store/restore per sink/source
* 0211-fix-volume-max-boot.patch:
I can confirm that this fixes the problem for me, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/598308
Title:
Volume at login set to Maximum
To manage notifications about this bug go to:
Yes, module-device-restore saves the volume per port/sink.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/598308
Title:
Volume at login set to Maximum
To manage notifications about this bug go to:
do pulseaudio save volume setting of all ports ?
if headphones were plugged during shutdown
but unplugged before next boot
will pulseaudio restore the speaker volume ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
how do user know pulseaudio really save the sound setting ?
any program which dump those pulsraudio database file to verify the
sound setting is really saved ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
That depends if module-device-restore is load in your env (it is by
default).
You can check the volume database at ~/.config/pulse/hash-device-
volumes.tdb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can also confirm this issue, and affects ubuntu touch. After the
device is booted, when playing something, it'll always be set to maxium,
even though pactl list sinks shows the right volume
Once I change volume up or down, it gets to the right and expected
volume level (abruptly changing the
Tracking down the pa_sink_set_volume call (which is what pactl set-sink-
volume uses), the original sink had the correct real volume, but a wrong
soft_volume (as in my use case the driver/hw is not providing hardware
volume support). The soft_volume was actually at the max volume, which
is the
As a test I created the following patch, that fixes the initial broken
behaviour for my driver/hw:
diff --git a/src/pulsecore/sink.c b/src/pulsecore/sink.c
index ccf6ea1..0f1a0b8 100644
--- a/src/pulsecore/sink.c
+++ b/src/pulsecore/sink.c
@@ -283,7 +283,10 @@ pa_sink* pa_sink_new(
So this is the call trace I'm getting with my device:
1) module specific (droid in my case) - pa_sink_new
2) pa_sink_new fires up PA_CORE_HOOK_SINK_FIXATE before finishing setting up
the sink, giving the original data (pa_sink_new_data) to the callback;
3) module-device-restore gets
[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
Bugs, which is subscribed to Ubuntu.
In my case the package pulseaudio-equalizer (or depencencies) from
ppa:nilarimogard/webupd8 caused this issue. After removing, the problem
is solved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://wiki.ubuntu.com/Audio/AlsaInfo
pactl list
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/598308
Title:
Volume at login set to Maximum
To manage notifications about this bug go to:
Intel HD Audio Chipset using S/PDIF coax out to speakers and system
audio set to digital output
do your HDA codec SPDIF has volume control ???
** Changed in: pulseaudio (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
I also am affected by this bug. (Xonar DX)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/598308
Title:
Volume at login set to Maximum
To manage notifications about this bug go to:
I have this same problem. Upon reboot Digital Output (S/PDIF) volume is
always set to maximum.
I think I've traced it to the pulse module module-device-restore.
Attached is a log, loglevel=4. I can see that module-device-restore
opens the TDB file, but I never see in the log something like
I am also having this issue. I am using an USB Creative X-FI 5.1 sound
card. I having flat-volumes on just made matters worse as every new
song played moved to 100% and having it off leaves things like the
basic description. The other suggestions also didn't resolve the issue
for me.
--
You
I started to get this problem when I put in a new soundcard.
The new soundcard is Asus Xonar DX.
The alsa volumes are restored as they should but pulse volume is set to like
100% but the slider in ubuntu/unity 12.04 is set to what is was before reboot.
Just changing the slider a little bit sets
I started being affected by this after installing the JACK audio plugin
for pulseaudio in synaptic. The problem persists, however, after I have
purged the previouslyy mentioned packaged.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've been affected by this too:
Kubuntu 11.04 amd64
kmix 4:4.6.2-0ubuntu2
Comment #7 fixed it for me.
After doing rm ~/.kde/share/config/kmix* and cycling , was saved.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: pulseaudio (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/598308
Title:
Volume at login set to Maximum
--
ubuntu-bugs mailing list
I followed Aaddron's suggestion in comment #18 and then #16 but I had no
luck. Using Creative Sound Blaster X-Fi on Kubuntu Natty i386.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/598308
Title:
Just found a working fix for my hardware: tell Pulse to control just one
mixer control.
1. edit /etc/pulse/default.pa
2. uncomment the line that says
#load-module module-alsa-sink
3.change it to
load-module module-alsa-sink control=PCM
4. save reboot
--
You received this bug notification
This bug has terrorized my hearing for a while - I use headphones
through an external soundcard, and I've nearly deafened myself several
times forgetting to slightly adjust the volume before listening to
music.
Aaddron, you solution worked great! Just tested it. I hope there are no
side effects,
Small update, you only need to put the ; before flat-volume = no.
Glad it worked for you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/598308
Title:
Volume at login set to Maximum
--
I finally found a fix for my bug! As they are vary similar, possibly
even the same it might work for you too, here's what I did:
sudo gedit /etc/pulse/daemon.conf
add a ; and a space to these four lines:
resample-method = speex-float-1
flat-volumes = no
default-fragments = 8
Not that I'd expect any different as it's only Alpha 1 but this bug is
still around in 11.04 Alpha 1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/598308
Title:
Volume at login set to Maximum
--
I have an idea for a workaround but have no idea how to do it or even if
it's possible. Make a script that runs during boot or maybe right after
log in that adjust the volume by +1 or -1 automatically... in theory
this would fix the issue and the change in volume would be so slight
it would be
I'm sure PCM being set to max by default isn't the cause of this. Using
the directions in a workaround for another bug I set PulseAudio to only
control the Master pipeline and then lowered PCM in alsamixer... this
lower the volume of the bugged sound but as soon as you move the
volume slider
I have pretty much word for word the exact same issue except updates
didn't fix it. Are you sure it was the updates that fixed it and not
something else?
--
Volume at login set to Maximum
https://bugs.launchpad.net/bugs/598308
You received this bug notification because you are a member of Ubuntu
It doesn't appear to have been completely fixed but the volume is no
longer at a maximum when I reboot now it is however still louder than
what it should be.
--
Volume at login set to Maximum
https://bugs.launchpad.net/bugs/598308
You received this bug notification because you are a member of
I'm getting the same behaviour, Ubuntu 10.10 32-bit also happens in
64-bit. Before I found this report I made one for this issue with what
I've noticed so far, I marked it a duplicate of this bug. Here's the
link:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/661885
So far I've
@Aaddron Your symptom isn't precisely the same as the cause for this
bug. If you're using KMix (or any environment that uses KMix, e.g.,
Kubuntu), you have a stale KMix configuration file. Please remove it
and cycle your login.
--
Volume at login set to Maximum
I'm new to this so if you say so but how is my bug report not a
duplicate of his? Both running Ubuntu and we both have described the
same issue. That sounds a lot like a duplicate to me.
The only reason I brought up Kubuntu was because I found it odd that
Kubuntu worked fine until this release
KMix handles restoring of volume state *in addition* to pulse. Can you
reproduce this symptom from a boot of the Kubuntu10.10 live cd?
--
Volume at login set to Maximum
https://bugs.launchpad.net/bugs/598308
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Yes and like Ubuntu moving the volume slider even slightly fixes it
until rebooting, also forgot to say that you can log out and back in
without issue it's only after booting.
--
Volume at login set to Maximum
https://bugs.launchpad.net/bugs/598308
You received this bug notification because you
Please note that volumes being set to max is a design decision of
PulseAudio; see http://pulseaudio.org/wiki/PulseAudioStoleMyVolumes
--
Volume at login set to Maximum
https://bugs.launchpad.net/bugs/598308
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Based on how the volume reacts when I adjust it via the tray icon and
the values that show up in alsamixer it seems there is some kind of
disconnect between pulse and alsa. Based on the page you linked pulse
goes through and adjusts the alsa channel levels at startup, shouldn't
these adjustments
It seems a recent update to pulseaudio has fixed my issue. Updated my
system yesterday, june 12, which also came with a kernel update which
prompted a reboot per usual and volume levels seem to be normal now
after reboot and after a shutdown and restart.
--
Volume at login set to Maximum
** Package changed: ubuntu = pulseaudio (Ubuntu)
--
Volume at login set to Maximum
https://bugs.launchpad.net/bugs/598308
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
This does not seem to be related to libgtk2-ex-volumebutton-perl.
** Package changed: libgtk2-ex-volumebutton-perl (Ubuntu) = ubuntu
--
Volume at login set to Maximum
https://bugs.launchpad.net/bugs/598308
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Forgive me if I misspeak as I am still very new to using linux but it
seems that this may be a problem with pulseaudio and its interaction
with alsa on startup. When I run alsa-mixer in terminal at startup the
volume levels indicated match that of those displayed on the slider in
the panel applet.
** Description changed:
Release: Ubuntu 10.04 64-bit Desktop Edition
What You Expected to Happen: System volume to remain as set before reboot and
as shown in volume panel applet
What Happened Instead: After reboot/shutdown at and after login system volume
is set to maximum
** Package changed: ubuntu = libgtk2-ex-volumebutton-perl (Ubuntu)
--
Volume at login set to Maximum
https://bugs.launchpad.net/bugs/598308
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
55 matches
Mail list logo
