*** This bug is a duplicate of bug 352732 ***
https://bugs.launchpad.net/bugs/352732
I think I've found a simpler way to fix the problem of setting the audio at a
desidered level at start up.
I used the aslactl function with a custom file
*** This bug is a duplicate of bug 352732 ***
https://bugs.launchpad.net/bugs/352732
** This bug has been marked a duplicate of bug 352732
[jaunty] Sound muted after boot
--
[Jaunty] Sound card outputs start muted after recent updates to use pulseaudio
Mark Rijckenberg's solution from Question 68564 is to comment out line
372 (approx) in the /etc/init.d/alsa-utils file:
# mute_and_zero_levels $TARGET_CARD || EXITSTATUS=1
--
[Jaunty] Sound card outputs start muted after recent updates to use pulseaudio
https://bugs.launchpad.net/bugs/315809
I had the same problem with 5 different computers (netbooks to
stationary) in Jaunty. With pulseaudio the sound was either muted or PCM
was set to 0. The only solution that worked was to uninstall pulseaudio
completely. That worked, and I didn't see any programs having problems
without the
OK, I've had this problem for some time and nothing seemed to work but
various links above took me to this solution which did work.
# WORK-AROUND FOR AUDIO PROBLEM #
1.) Manually adjust the mixer settings to something that is a good
default for your audio needs. These settings will be
A related discussion:
https://answers.launchpad.net/ubuntu/+question/68564
My Distro:
Xubuntu Jaunty x64
For details about the startup scripts:
http://linux.com/news/enterprise/systems-management/8116-an-introduction-to-services-runlevels-and-rcd-scripts
This is a tool you can use to change the
Now, it looks to me like that script started like that should be stopped before
the system halts/reboots:
sudo update-rc.d -f alsa-utils remove
sudo update-rc.d alsa-utils start 50 2 S . stop 50 0 6 .
But this results in the mute on system boot. By removing the stop
links to the script, the
Freddie, why don't you try deleting the /etc/rc6.d/K50alsa-utils ? That script
resets the volume settings, so if you remove it you preserve your mixer
settings. The /etc/rcS.d/S50alsa-utils is not necessary.
It worked for me.
Distro: Xubuntu Jaunty x64
--
[Jaunty] Sound card outputs start
I'm on Debian testing. on my set up the symlink has already been created
at /etc/rcS.d/S50alsa-utils (which fits with the notes atop /etc/init.d
/alsa-utils) so this fix, predictably, doesn't work.
--
[Jaunty] Sound card outputs start muted after recent updates to use pulseaudio
ah, so the problem is master is being muted. note that the user can
configure this in gnome-volume-control if he added the master control in
preference
--
[Jaunty] Sound card outputs start muted after recent updates to use pulseaudio
https://bugs.launchpad.net/bugs/315809
You received this bug
Confirmed. So, as workaround:
sudo ln -s /etc/init.d/alsa-utils /etc/rc2.d/S26alsa-utils
** Changed in: alsa-utils
Status: New = Confirmed
** Changed in: pulseaudio
Status: New = Invalid
** Changed in: linux (Ubuntu)
Status: New = Invalid
--
[Jaunty] Sound card outputs
I tried the workaround but my sound is still muted on reboot.
--
[Jaunty] Sound card outputs start muted after recent updates to use pulseaudio
https://bugs.launchpad.net/bugs/315809
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Not sure if this helps but this only happens on a reboot. If I shutdown
then restart the sound is OK.
--
[Jaunty] Sound card outputs start muted after recent updates to use pulseaudio
https://bugs.launchpad.net/bugs/315809
You received this bug notification because you are a member of Ubuntu
Confirmed on my HP Pavilion dv9830 laptop. Symbolic link in /etc/rcS.d/
is missing. Be sure to check inside /etc/init.d/alsa-utils for the
correct filename to use for the link (the comments near the top of the
file will give you instructions on how to remove the autosave/autoload
features, so just
** Changed in: linux (Ubuntu)
Sourcepackagename: None = linux
--
[Jaunty] Sound card outputs start muted after recent updates to use pulseaudio
https://bugs.launchpad.net/bugs/315809
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
So I solved it for me by establishing a symbolic link inside /etc/rc2.d
as described in the file
/etc/init.d/alsa-utils
ln -s /etc/init.d/alsa-utils S26alsa-utils
try and have fun
--
[Jaunty] Sound card outputs start muted after recent updates to use pulseaudio
This solution worked for me aswell.
--
[Jaunty] Sound card outputs start muted after recent updates to use pulseaudio
https://bugs.launchpad.net/bugs/315809
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Also affects: pulseaudio
Importance: Undecided
Status: New
--
[Jaunty] Sound card outputs start muted after recent updates to use pulseaudio
https://bugs.launchpad.net/bugs/315809
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
jerry, the alamixer is a bit tricky, your outputs can show full volume
but if theres MM under them they are muted. make them active, then hit m
key. Been confused myself by that.
--
[Jaunty] Sound card outputs start muted after recent updates to use pulseaudio
By downgrading my systems (two) from a backup dated jan, 5th and
upgrading step by step it seems to be the update of package
alsa-utils (1.0.18-1ubuntu4 to 1.0.18-1ubuntu5
which is responsible for the malfunction described above (not the
pulseaudio packages)
** Also affects: alsa-utils
Responsible for muted startup seems to be a wrong LABEL inside the
script
/usr/share/alsa/init/00main
- GOTO=00_mainend
- LABEL=00main_end
see attachment (out of last updated package)
** Attachment added: 00main
http://launchpadlibrarian.net/21109056/00main
--
[Jaunty] Sound card outputs
This problem is an usability issue too.
There is no way (or I can't find any) that a casual user could fix the hardware
muted channel issue using graphical gnome-volume-control application and applet.
Going through terminal and alsamixer may be a showstopper.
--
[Jaunty] Sound card outputs
O.K., I see the error inside the script, and corrected it -
Now, how do I get the script installed? Reboot didn't do it, or at least still
no sound.
Thanks, Jerry
--
[Jaunty] Sound card outputs start muted after recent updates to use pulseaudio
https://bugs.launchpad.net/bugs/315809
You
The problem is somewhere in alsactl. store/restore behaves funny. Only
after several attempts was previously stored state restored. First try
restored the muted state, then after some stores the values were stored
and finally the mute switch values stayed in place too.
--
[Jaunty] Sound card
Can confirm muted starting of sounds and the workaround above to solve
the problems. The muted status I can revise by klicking on the panel-
button and the status changes, but pulseaudio output will not be
influenced by changing the level-controller. Either volume-controller
2.25.2 nor
I also had this problem, which I worked around using 'alsamixer -c0' and
unmuting things.
This is particularly pernicious because the default sound control that
Jaunty provides doesn't have these mute buttons, at least for my
hardware, nor are they apparent when I run just 'alsamixer'.
(My
After yesterday's updates, PulseAudio Volume Meter shows bars going back
and forth, but there's no sound out of the speakers. The hardware is HDA
ATI SB = ALC888 Analog on a Compaq Presario
Linux version 2.6.28-4-generic (bui...@palmer) (gcc version 4.3.3 20081217
(prerelease) (Ubuntu
27 matches
Mail list logo
