Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

I installed 10.04 a couple of weeks ago. My primary OS is Windows and i could not install Linux up until very recently because of lack of hardware support for my notebook.

10.04 is the only distribution that i managed to get to install on my notebook, but my problem is, that even though i set the volume at a low level, every time after booting and login into Ubuntu, the sounds will play at the highest volume. The volume indicator will still show the low volume setting, but sounds play at the highest volume until i click the volume setting again manually

Is there a config-file i need to update to fix this, or is it a known bug?
Anybody had the same problem?

share|improve this question
    
Please don't forget to add your hardware specs to this question. –  Bobby Oct 20 '10 at 11:04
    
Probably a bug from ALSA but we need to know what is your sound card to find which one. –  Nyamiou The Galeanthrope Oct 20 '10 at 15:07
    
Gio, did you find a solution? I have the same problem on 10.10, and on my system "loud" means 106 db with no hardware volume regulator. Sound card Onkyo Wavio SE-U55SX. –  rumtscho Dec 10 '10 at 20:17
    
If it's a bug, this should be reported elsewhere, with all the details, so it can be fixed. I have the same problem with 11.10 (and I think it has come and gone with earlier distributions) –  Sean Houlihane Dec 14 '11 at 8:32
    
Try updating alsa, I also had same kind of problem and updated to the latest in my 10.10.It is now fixed (but BUGS are BUGS, now music delays when alert sound plays-not always, Rarely) –  Prasad RD Mar 9 '12 at 12:01
add comment

2 Answers

Please try this approach - it might help.

share|improve this answer
add comment

I think this issue is related to a known bug, that is already in proggress: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/206315

share|improve this answer
1  
That specific bug is very old, and very likely fixed now. –  fluteflute Oct 22 '10 at 14:57
1  
It's not fixed, there are still issues that are associated with it. –  Rafał Cieślak Oct 28 '10 at 16:02
    
A new bug might be a better way to raise the profile of this, despite some un-tracable reference to it being fixed in git at the end. –  Sean Houlihane Dec 14 '11 at 8:30
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.