I'm running KDE 4.5.4. Fully uptodate. On every reboot audio was muted with
volume level at 44%.
I've tried all the solutions I could find in this list.
What worked for me was.
Set audio unmuted and at the required volume level using kmix.
(not sure if this is essential)
sudo apt-get purge
I still had the problem after the fix, and one more thing fixed it for
me:
sudo apt-get remove --purge alsa-utils
sudo apt-get install ubuntu-desktop
--
[Maverick] Sound is always muted on startup; unmuting makes the volume at
lowest level
https://bugs.launchpad.net/bugs/592016
You received
I've tried #45 but nothing works on my end (Running on a model 5
Pangolin Performance from System76).
I'm also plagued by
1.) No startup sounds
2.) No log out sounds
--
[Maverick] Sound is always muted on startup; unmuting makes the volume at
lowest level
https://bugs.launchpad.net/bugs/592016
Confirming that it is fixed. If it still appears for you, you're
probably affected by another bug.
** Changed in: pulseaudio (Ubuntu Maverick)
Status: Triaged = Fix Released
--
[Maverick] Sound is always muted on startup; unmuting makes the volume at
lowest level
I still have the problem..it happens randomly, maybe when switching from
Unity to Ubuntu..at start I find the audio off..and if I try to reenable
audio and turn up the volume, tha audio still doesn't work..I managed to
make it work changing the connector 3 times or so in the output tab of
the
and yes, when unmuting the volume is at the lowest level, but not
working at all..
--
[Maverick] Sound is always muted on startup; unmuting makes the volume at
lowest level
https://bugs.launchpad.net/bugs/592016
You received this bug notification because you are a member of Ubuntu
Bugs, which
Initially I was going to comment that the bug showed up on my beta, but
even better I can add that after updating today, it went away. Hope that
proves useful.
--
[Maverick] Sound is always muted on startup; unmuting makes the volume at
lowest level
https://bugs.launchpad.net/bugs/592016
You
Same here, latest update solves the problem! Yeah! Thx all!
--
[Maverick] Sound is always muted on startup; unmuting makes the volume at
lowest level
https://bugs.launchpad.net/bugs/592016
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: pulseaudio (Ubuntu Maverick)
Assignee: (unassigned) = Luke Yelavich (themuso)
--
[Maverick] Sound is always muted on startup; unmuting makes the volume at
lowest level
https://bugs.launchpad.net/bugs/592016
You received this bug notification because you are a member of
I've updated today and done as you said, but no luck.
--
[Maverick] Sound is always muted on startup; unmuting makes the volume at
lowest level
https://bugs.launchpad.net/bugs/592016
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Yes, I had the problem in two different machines and now everything is
fine for me.
--
[Maverick] Sound is always muted on startup; unmuting makes the volume at
lowest level
https://bugs.launchpad.net/bugs/592016
You received this bug notification because you are a member of Ubuntu
Bugs, which
@Luke I followed your instructions as you said in post #45 and now
everything works fine. Thank you very much!
--
[Maverick] Sound is always muted on startup; unmuting makes the volume at
lowest level
https://bugs.launchpad.net/bugs/592016
You received this bug notification because you are a
@Jake, it should be as simple to just change the volume to your
preferred one, then either reboot or log out, and it should store the
latest value, then restore it when you log in again. Repeat this
procedure for every user.
--
[Maverick] Sound is always muted on startup; unmuting makes the
I've done that multiple times and it doesn't work, unfortunately.
--
[Maverick] Sound is always muted on startup; unmuting makes the volume at
lowest level
https://bugs.launchpad.net/bugs/592016
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
What happens to me is the following:
1. I can here sometimes the login sound (once/twice out ten);
2. I never hear the logout sound
3. I sometimes hear the system sounds (but not loud...)
--
[Maverick] Sound is always muted on startup; unmuting makes the volume at
lowest level
I think it got fixed after yesterday's(?) update... Everything's fine on
my HP Pavilion, x32 Maverick Beta with latest updates... :)
--
[Maverick] Sound is always muted on startup; unmuting makes the volume at
lowest level
https://bugs.launchpad.net/bugs/592016
You received this bug
Yes, for me too.
--
[Maverick] Sound is always muted on startup; unmuting makes the volume at
lowest level
https://bugs.launchpad.net/bugs/592016
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
It's working mostly for me again (Maverick 32 with all updates), but I
now find that if I use fast user switching and log in as, say, the guest
user, the wrong audio device is selected and the volume is again muted
and at 0%.
--
[Maverick] Sound is always muted on startup; unmuting makes the
On a single user machine, the latest updates solve the issue for me too.
If I find enough time, I'll try to create a new user and make some
tests.
--
[Maverick] Sound is always muted on startup; unmuting makes the volume at
lowest level
https://bugs.launchpad.net/bugs/592016
You received this
A week ago I fixed this issue - temporarily - by commenting the line
load-module module-device-restore in the file /etc/pulse/default.pa ,
as someone else recommended.
But since the last 2 updates (one this morning and one a few days ago)
no matter if that line is commented or not I stil have no
Daniel, but how would I fix the problem for an existing user? I've
already tried stopping pulse and deleting .pulse* from the home
directory.
I'm glad that when I start my computer and login to my username, my
sound isn't muted upon entering my session anymore. But I'm still
troubled by the fact
I can confirm too, but now sound is muted for the some time.
--
[Maverick] Sound is always muted on startup; unmuting makes the volume at
lowest level
https://bugs.launchpad.net/bugs/592016
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
it is working fine for me (ubuntu 10.10 beta)
--
[Maverick] Sound is always muted on startup; unmuting makes the volume at
lowest level
https://bugs.launchpad.net/bugs/592016
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This is now fixed for me after the latest update to alsa-utils this
morning.
* debian/init: Restore change from 1.0.21-1ubuntu2 lost during merge
that skips muting and zeroing levels prior to shutdown/reboot,
which was a hack for broken drivers. This change closes LP: #21804,
LP:
Perhaps I spoke a little too soon. It does indeed appear to be *mostly*
fixed (sound isn't muted now upon boot), but I just logged out of one
user and into another, and the second user had muted sound. The levels
weren't zeroed, but it was indeed muted when it shouldn't have been. (No
login sound
Jake, was the second user an existing one or a new one? Note that for
existing users, it isn't an alsa issue but what pulseaudio has stored
for that user. You should try and reproduce the issue with a brand new
user.
Note also that the graphical greeter has a corresponding user. :-)
--
so the current factory default levels (e g, what you get if you
boot a Live-CD)
The controls are muted by default by the driver to prevent accidental
damage of the speaker ,
The volume of Live-CD is the result of alsactl init
If you use alsactl store -f original.txt before you logout/reboot
It doesn't happen on my main system with a sb audigy 2 but it does
happen on an older pc with sb live!
--
[Maverick] Sound is always muted on startup; unmuting makes the volume at
lowest level
https://bugs.launchpad.net/bugs/592016
You received this bug notification because you are a member of
I can confirm the always mute problem in beta.
--
[Maverick] Sound is always muted on startup; unmuting makes the volume at
lowest level
https://bugs.launchpad.net/bugs/592016
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
So getting to this seems pretty hard. I think we're going to need a
startup/shutdown expert to fix this the right way.
Here is what *should* happen, in that order:
#1) PulseAudio plays the log-out sound, if any
#2) All applications accessing PA should quit
#3) PA should store current volume,
Subscribing Scott, as a world expert on startup / shutdown :-)
Scott, do you think David's outline in
https://bugs.edge.launchpad.net/ubuntu/+source/pulseaudio/+bug/592016/comments/26
is achievable?
--
[Maverick] Sound is always muted on startup; unmuting makes the volume at
lowest level
OK, I'm reassured you're on the case of the underlying bug :)
With regard to the 65%, I do understand that there are outliers. But I
feel strongly that we should pick a reasonable level, and fix the
outliers. Turning the computer on and having no sound always feels
like a problem. The chances of
@Mark, IIRC, PulseAudio does not mess with the controls unless the
volume control is actually moved, so the current factory default
levels (e g, what you get if you boot a Live-CD) are what you see in
/sbin/alsa-utils (function sanify_levels_on_card()). Most of them
(front, pcm, master) are set to
Isn't this a race between pulseaudio quitting, and alsa-utils muting the
output to prepare for shutdown? Can we fix this by changing /etc/init
/alsa-mixer-save.conf
from
start on starting rc RUNLEVEL=[06]
to something like:
start on (starting rc RUNLEVEL=[06]) and (there is no pulseaudio
I've noticed this with a USB headset. If we're going to have a default
level in Ubuntu it should be 65% please, but the best is to reset to the
former level of the same device.
** Changed in: pulseaudio (Ubuntu)
Importance: Undecided = High
** Also affects: pulseaudio (Ubuntu Maverick)
David: sounds reasonable, go for it!
Regarding Mark's comments, there are actually a couple pieces here.
Firstly, we're incorrectly using alsactl via the udev script; the fix
for that is in maverick's alsa-utils bzr branch. Secondly, percentage
isn't precise for default levels given the
Okay, so just to test, I hacked /sbin/alsa-utils stop a little to wait
for pulseaudio to quit, but I had a timeout of 15 seconds and after that
time, pulseaudio was still alive. So something should tell pulseaudio to
shutdown, but it doesn't.
** Changed in: pulseaudio (Ubuntu Maverick)
Same here. Upgraded after alpha 3 release.
I tried creating a new user and rebooting directly into his account and
no dice.
Doug McMahon workaround [1] fixed this for me.
[1]
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/592016/comments/1
--
[Maverick] Sound is always muted on
I installed Ubuntu 10.10 Beta (64 bit) and encountered the bug, the
sound was muted and when unmuted the sound was set to minimum.
The workaround suggested by Doug McMahon and Jorge Suárez de Lis
(https:/ /bugs.launchpad .net/ubuntu/ +source/ pulseaudio/ +bug/592016/
comments/ 1) fixed the
** Branch linked: lp:~ubuntu-core-dev/alsa-utils/ubuntu.new
--
[Maverick] Sound is always muted on startup; unmuting makes the volume at
lowest level
https://bugs.launchpad.net/bugs/592016
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Same problem here on an Alpha 3 fresh install and fully upgraded.
--
[Maverick] Sound is always muted on startup; unmuting makes the volume at
lowest level
https://bugs.launchpad.net/bugs/592016
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Still present as of pulseaudio 1:0.9.22~0.9.21+stable-
queue-32-g8478-0ubuntu17. No behavioural changes whatsoever.
(BTW, this version is listed in changelog with date 2010-07-21 -- I
wonder which recent updated posting #11 refers to?)
--
[Maverick] Sound is always muted on startup; unmuting
Could you check whether it is still present? Recent updated fixed it for
me.
--
[Maverick] Sound is always muted on startup; unmuting makes the volume at
lowest level
https://bugs.launchpad.net/bugs/592016
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Yep, fixed for me. Marking as fix-released
** Changed in: pulseaudio (Ubuntu)
Status: Confirmed = Fix Released
--
[Maverick] Sound is always muted on startup; unmuting makes the volume at
lowest level
https://bugs.launchpad.net/bugs/592016
You received this bug notification because you
This isn't completely fixed. It's still here in a strange way.
For my account, the issue is gone. But for the second user account on my
machine, the bug still exists. Here are peculiar things I can easily
reproduce:
Consider user A my account - sound always works fine. User B is the
account
Jake, could you clear out all .pulse related files from the user with
the problem, and try again? The easiest way to do this is to log out, go
t a text console, make sure you don't have any pulseaudio processes for
that user running, and rm -rf .pulse* in your home directory.
Thanks.
--
Hi Luke, I tried your suggestion and it didn't help. I actually did it
for both accounts, and now the one that was working is back to having
the muted problem again too. :/
If you yourself try what you suggested, does it make the problem come
back? Or for anyone else?
Is there anything else I
I can confirm Luke's observations.
Doug, I've never fiddled with alsamixer and still have the bug.
** Attachment added: pulseverbose.log
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/592016/+attachment/1520263/+files/pulseverbose.log
--
[Maverick] Sound is always muted on
What has come up is that this may be related to alsa-utils
On machines where alsa-utils is installed, but alsamixer never run then sound
on boot is fine (not muted and or set to 0
Once alsamixer has been run once, then on reboot sound is either muted @level 0
or just set to level 0
maybe in
On a laptop with stereo output installed from 1 day pre alpha 3 this is
no longer an issue other than an occasional boot to MUTED sound
On a desktop with 5.1 analog output, installed alpha 1, commenting the line and
a log out/login produces no change, ie. sound levels stay the same.
However a
Line 3 above should read
. uncommenting the line
--
[Maverick] Sound is always muted on startup; unmuting makes the volume at
lowest level
https://bugs.launchpad.net/bugs/592016
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This appears to be a continuing issue for many - whether the volume is actually
muted or just set to 0 at boot.
Commenting the mentioned line does resolve for most ...
( The pcm levels I mentioned in previous post (5.1 output), were the
actual pcm's that affected the various channel levels -
I can also confirm this issue both on a desktop with a quad core, and a
MacBook Pro 4,1 with a Core2 Duo CPU.
Could everybody with this issue try the following for me:
1. If you have the above line commented, please uncomment it.
2. In your logins ession, set up the volume to your satisfaction.
Actually I like it the way pulse is now - hopefully it won't get messed
up if this is fixed.
With that line commented out pulse will not change the pcm level on boot if
lowered in alsamixer from the inexplicable default of 100.
(there is no reason to use a pcm or any other level of 100 with
On every boot up i also seem to be muted on my eeepc.
--
[Maverick] Sound is always muted on startup; unmuting makes the volume at
lowest level
https://bugs.launchpad.net/bugs/592016
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Yep, same here on a MacBook
--
[Maverick] Sound is always muted on startup; unmuting makes the volume at
lowest level
https://bugs.launchpad.net/bugs/592016
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Can confirm same here - always boots to muted sound
As a temp workaround in /etc/pulse/default.pa find this line and comment
it out (seems counter-intuitive,, but works
load-module module-device-restore
** Changed in: ubuntu
Status: New = Confirmed
** Package changed: ubuntu =
57 matches
Mail list logo
