Fixed in lucid
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Fix Released
--
Move to pulse audio is not resetting volume levels at ALSA level
https://bugs.launchpad.net/bugs/418620
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
No alsactl component involved here.
** Changed in: alsa-utils (Ubuntu)
Status: New => Invalid
--
Move to pulse audio is not resetting volume levels at ALSA level
https://bugs.launchpad.net/bugs/418620
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Marking oem-priority as fixed as pulse audio will now reset to some
default level if the alsamixer is tweaked.
@Cyril this would be a pulseaudio issue and probably an alsa one. You probably
want to try and install package
"linux-backport-modules-alsa-karmic-generic".
** Changed in: oem-prior
I expect to have the same audio settings before and after boot. So
resetting to some default values is not a good idea at all I think.
I have a desktop with audio inputs/outputs in front and behind the case.
The front levels are separated from the other levels and I can only
change those levels us
This may not be the place sorry am very new to ubuntu pulseaudio ? problem
pulse sound is good but i still need trebel & Bass
and Everytime i play song in totem or rhythmbox or any other my headphone sound
becomes one speaker .Ok Go In terminal write alsamixer and then set headphone 1
volume up
On Thu, Oct 1, 2009 at 7:50 PM, Jerone Young wrote:
> A simple way to resolve this is to reset the alsa levels on reboot. So
> if a person does fall into this situation they can get out by simply
> rebooting.
That's actually exactly where the culprit lies. There's a race in when
alsactl store is
The issue here is that what your average user is exposed to is what is
in the gnome-volume-control.
If for some reason (what ever that reason is) someone or something
changes the alsamixers. Users will be changing the controls in the
gnome-volume-mixer and nothing will be happening to resolve thei
Based on Daniel's comment, this really sounds like an alsa-utils bug,
not a pulseaudio bug.
--
Move to pulse audio is not resetting volume levels at ALSA level
https://bugs.launchpad.net/bugs/418620
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: pulseaudio (Ubuntu)
Assignee: Canonical Desktop Team (canonical-desktop-team) => (unassigned)
--
Move to pulse audio is not resetting volume levels at ALSA level
https://bugs.launchpad.net/bugs/418620
You received this bug notification because you are a member of Ubuntu
Bugs,
I'm not too sure if I understand the real issue here. I have experienced
a 'learning curve' with pulse audio but have got it to work. It is
dynamic and you need to have an application running and using audio in
order to see the application (and controls) listed in the Applications
tab in the Sound
** Changed in: pulseaudio (Ubuntu)
Status: New => Incomplete
--
Move to pulse audio is not resetting volume levels at ALSA level
https://bugs.launchpad.net/bugs/418620
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
> But your new, average, & novice users may not have a clue that their
> is a alsamixer.
Right, I wouldn't expect them to. I just said that the same program
that was used to change the setting could be used to change it back.
> The problem is the settings are not being restored currently. Try
> t
Err, alsa-utils is still seeded by default for desktop, no?
The volume not being restored correctly is a race that I'm investigating,
but I'm traveling for work until Saturday...
On Sep 23, 2009 9:10 AM, "Jerone Young"
wrote:
@Martin
Now alsamixer is completely hidden away (not even inst
@Martin
Now alsamixer is completely hidden away (not even installed anymore by
default). The cases both of you describe are advanced users. But your new,
average, & novice users may not have a clue that their is a alsamixer .
The problem is the settings are not being restored cu
We have had /etc/init.d/alsa-utils storing hw settings on
shutdown/restoring on boot pretty much since day one in Ubuntu, for the
reasons pointed out by David; note that this has a "reset" command, to.
To be honest I don't quite follow the reasoning here: if a user uses a
program like alsamixer to
I would say more users use alsamixer to fix their sound, rather than
screwing it up.
So it seems to me like the suggested solution will make things worse
(and we will probably be overwhelmed with regression bug reports). I
would say it would be better to expose users to the alsamixer layer, at
lea
** Changed in: pulseaudio (Ubuntu)
Assignee: (unassigned) => Canonical Desktop Team (canonical-desktop-team)
--
Move to pulse audio is not resetting volume levels at ALSA level
https://bugs.launchpad.net/bugs/418620
You received this bug notification because you are a member of Ubuntu
Bugs,
** Visibility changed to: Public
--
Move to pulse audio is not resetting volume levels at ALSA level
https://bugs.launchpad.net/bugs/418620
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.ub
18 matches
Mail list logo
