In Karamic I commented out line 378 of /etc/init.d/alsa-utils, and my
sound is no longer muted after I log in.
However, I still get no actual sound output until I kill X and log back
in.
--
[jaunty,karmic] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug
I'm currently on Karmic but have had this problem since Jaunty.
Commenting out the mute_and_zero_levels line (thread comments 38 and 67)
worked for me as well. Thanks!
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because you are a
This bug affects me as well. I have made the changes suggested by Gavindi and
hoping that it works.
Thanks a lot
The sound configuration is
cat /proc/asound/cards
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xd320 irq 16
--
[jaunty] Sound muted after boot
@actionparsnip - comment #67: worked for me on my karmic installs.
Thanks.
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I was able to solve this issue on karmic beta via other means...
I found a K50alsa-utils symlink to /etc/init.d/alsa-utils in /etc/rc0.d/
and /etc/rc6.d/ . Once I redirected those symlinks to an empty file, my
sound settings are correctly restored throughout the boot and login
process.
Not sure
They're created at package creation time by dh_installinit(1). It's
interesting that removing them resolves the issue for you. Can you
verify that they're in fact storing muted settings? You may need to
modify /etc/init.d/alsa-utils to write timestamps out to a file in
/var/tmp or something...
--
Had to edit out:
mute_and_zero_levels $TARGET_CARD || EXITSTATUS=1
Mines on line 378. Someone in #ubuntu has it on 379
in /etc/init.d/alsa-utils
and rebooted, worked a treat
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because
Hey, guys. I have a few workarounds for this, and they're quite simple,
so rejoice!
The first one is SUPER easy. just sudo gedit ~/.xinitrc and add this
line:
amixer -c 0 sset Master,0 100%
Now, even though you still have the muting problem, your pc will run
this command on boot to unmute it.
Crap! I'm sorry. My last comment had a typo. The command you add to
.xinitrc SHOULD be:
exec amixer -c 0 sset Master,0 100%
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I actually don't have this problem anymore. It's fixed for me now, must
have been in one of the karmic updates.
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I am using Debian testing and I am getting exactly this problem --
volumes muted after reboot. This is definitely because of the
/etc/init.d/alsa-utils script getting executed twice. To discover this,
I did the following:
Copy /usr/sbin/alsactl to /usr/sbin/alsactl.exe
Create new
Could you please suggest a work around for a while.
I use /usr/bin/amixer -q set Master 100% unmute to unmute volume, But
I failed to automate this by: startup application,.bash.rc,
/etc/rc.local, .. . Still in search for the solution to run this command
automatically.
--
[jaunty] Sound muted
Yep, I can confirm this bug. Sound is muted on startup.
$ apt-cache policy pulseaudio
pulseaudio:
Zainstalowana: 1:0.9.16~test4-0ubuntu6
Kandydująca: 1:0.9.16~test4-0ubuntu6
Tabela wersji:
*** 1:0.9.16~test4-0ubuntu6 0
500 http://pl.archive.ubuntu.com karmic/main Packages
I have upgraded to Ubuntu Karmic, and the problem persists - i have to
unmute sound after every boot.
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I notice the same error.
My apport bug report is to be found in bug # 395594.
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Another reboot, and again the sound is muted. However, this morning's
startup works perfectly, with unmuted sound. An erratic behavior.
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Unfortunately, after turn on my computer today, the sound goes muted
again when goes into the desktop. Obviously this fix doesn't solve the
issue (I'm using .
According to that and the fact that another user claims the same, I'll
reopen this bugreport.
** Changed in: pulseaudio (Ubuntu)
Sorry for the wrapped comment. I mean I'm using the latest packages
from Luke's PPA.
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I dont think Luke's PPA has 0090_fix_sw_mute_desync.patch in it yet. The
Karmic package from the Ubuntu repositories should though and i am still
getting the problem with that.
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because
@Jared:
I can see the following in my
/usr/share/doc/pulseaudio/changelog.Debian.gz:
pulseaudio (1:0.9.15-3ubuntu1~ppa2) jaunty; urgency=low
* libltdl-dev - libltdl7-dev
-- Luke Yelavich them...@ubuntu.com Sun, 14 Jun 2009 09:36:29 +1000
pulseaudio (1:0.9.15-3ubuntu1~ppa1) jaunty;
@Ricardo
Just to put things in perspective, I'm on Karmic and the mute problems
disappeared. I wonder if there is another unrelated problem with your
system? Do you have a spare partition on your machine where you can test
a fresh Karmic install?
--
[jaunty] Sound muted after boot
@David
Unfortunately I can't install another OS without a complete hard disk
reorganization :(.
I'll try to do something and investigate it further. Besides that, I'm
not the only user affected by this issue that thinks it's not fixed with
the fix_sw_mute_desync patch.
Thanks anyway.
--
Daniel, Luke:
Could you please provide an updated binary package for Jaunty via PPA or
something similar? It could be great in order to test the fix on Jaunty.
If not, what about backporting the 0090_fix_sw_mute_desync.patch to the
current pulseaudio 1:0.9.14-0ubuntu20 on Jaunty?
Thanks in
Well I tried installing the Karmic package in Jaunty and the sound was
still muting on boot.
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I'm not a great programmer, but I tried backporting the
0090_fix_sw_mute_desync.patch to pulseaudio 0.9.14 (it's a small set of
changes). After rebooting, all seems to works OK, although I need to do
a deeper investigation due to the erratic and random nature of this
issue in my system (i.e.
Sorry for the bug spam, I forgot to include the URL to the PPA.
https://launchpad.net/~themuso/+archive/ppa
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Has anyone tried Luke Yelavich's PPA? He just updated the Pulseaudio
package a few days ago.
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Yes I am using Luke's PPA package now and still have the problem.
I have used the /etc/init.d/alsa-utils editing workaround successfully.
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because you are a member of Ubuntu
Bugs, which
@Jimmy:
That's exactly what I was looking for. Thanks! I'm using it now and
things are going well for now.
@Jared:
Have you tried to login with a freshly new user account?
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because you
No I didnt try with a new user account.
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
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
Can you please let us know what the fix was?
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
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 bug was fixed in the package pulseaudio - 1:0.9.15-3ubuntu1
---
pulseaudio (1:0.9.15-3ubuntu1) karmic; urgency=low
[ Daniel T Chen ]
* debian/patches/0001_change_resample_and_buffering.patch: Bump
default resampler to ffmpeg. We cannot peg the cpu, and we cannot
have
** Branch linked: lp:~crimsun/pulseaudio/ubuntu
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
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
** Package changed: alsa-driver (Ubuntu) = pulseaudio (Ubuntu)
** Changed in: pulseaudio (Ubuntu)
Status: Confirmed = Fix Committed
** Changed in: pulseaudio (Ubuntu)
Assignee: (unassigned) = Daniel T Chen (crimsun)
--
[jaunty] Sound muted after boot
Gavindi's solution works, in the sense that if I comment that line I
have all volumes up after the desktop is loaded. But the strange thing
is that it makes the login sound disappear. Summing up, this is how it
works for me:
1) with the line un-commented (default situation)
- drum sound at the
For me, that would be:
1) with the line un-commented (default situation)
- drum sound at the beginning
- NO login sound at desktop loading
- master channel muted
2) with the line commented (Gavindi's solution)
- drum sound
- login sound
- master channel unmuted
To add to Gavindi's theory, I
Ok,
I've found a fix that works for me. I was find that if I didn't shut down my
computer gracefully (and there letting /etc/init.d/alsa-utils run it's stop
procedure) that the sound levels would be set and un-muted on next boot.
Therefore, I commented out line 372 in /etc/init.d/alsa-utils:
#
I love you, Gavindi, that worked!
I'd like to run more tests though, because I only tried restarting.
Will do that ASAP.
On Mon, Jun 1, 2009 at 19:47, Gavindi gavi...@gmail.com wrote:
Ok,
I've found a fix that works for me. I was find that if I didn't shut down my
computer gracefully (and
Mmmm that didn't do it for me:
$ sudo /etc/init.d/alsa-utils restart
* Shutting down ALSA...
[OK ]
* Setting up ALSA...
and still no sound. I also tried:
$ sudo alsa reload
lsof: WARNING: can't stat() fuse.gvfs-fuse-daemon file system /home/ptn/.gvfs
Output information
Hi PTN,
Yeah my bad. Upon further investigation, my suggestion wasn't working as
I thought it was
Keep looking
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
For me, manually running /etc/init.d/alsa-utils restart will unmute the
sound.
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Bug watch added: PulseAudio sound server #572
http://pulseaudio.org/ticket/572
** Also affects: pulseaudio via
http://pulseaudio.org/ticket/572
Importance: Unknown
Status: Unknown
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug
** Changed in: pulseaudio
Status: Unknown = New
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
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
If this can have some interest I found that adding /lib/udev/alsa-utils in
sessions can solve the problem, but what happens is:
1) the splash image that I added with the Gnome utility appears
2) the login sound start (I put a large sound, about 30 seconds)
3) during the execution the login sound
I can confirm that the sound is not muted when booting after a system
crash.
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I confirm what Jimmy Buck already said: when you shutdown your system in
a forced way (or if it crashes, as it was in my case), the sound is not
muted after a reboot. It looks like something mutes the channels upon
shutdown, and then re-mutes them upon login. That's why the master
channel is
I can confirm that after booting, but before logging in, my master
channel is *not* yet muted, as it should be. So it's something in the
Gnome login process with mutes it, PulseAudio is a prime suspect ;-)
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received
Disregard my previous comment about staying in Gnome doesn't exhibit the
problem. It definitely does.
I did, however, find that it doesn't happen when forcing a reboot
instead of using the menu in Gnome to reboot. If I do a 'sudo reboot',
the sound isn't muted when coming back up.
Either way,
Same issue here. I followed
http://idyllictux.wordpress.com/2009/04/21/ubuntu-904-jaunty-keeping-
the-beast-pulseaudio-at-bay/ but it didn't help, I enabled alsa-utils
in Services but still nothing. My ~/.asoundrc* files didn't have the
lines mentioned, so I didn't try deleting them.
I miss the
Disabling alsa-utils in System - Administration - Services solves the
problem for me
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Same thing is happening to me with my Intel HDA chipset.
If I stay within Gnome, everything seems to work fine. But if I set my
default session to XBMC (possible in the latest builds of XBMC), the
master channel is at 0% when I boot up sometimes.
I haven't tried building XBMC with Pulse Audio
The same is happening with KDE too. Volume gets muted every 60 seconds or
something. Disabling pulseaudio following this guide helped:
http://idyllictux.wordpress.com/2009/04/21/ubuntu-904-jaunty-keeping-the-beast-pulseaudio-at-bay/
--
[jaunty] Sound muted after boot
I have this problem as well.
Whenever I boot, the master channel is turned all the way down and
muted. I can unmute and turn it up and then it works fine until I
reboot.
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because you are
GDM has sound to make the login ready sound.
If I run alsamixer instantly on starting my window manager (dwm) I see
that all my volume settings are correct.
Moments later they are wrong.
It is not the gnome-settings-daemon... it does it even with that off.
I am beginning to suspect the
Confirmed the problem is PulseAudio.
Used http://idyllictux.wordpress.com/2009/04/21/ubuntu-904-jaunty-
keeping-the-beast-pulseaudio-at-bay/ (well, almost, had to put exit at
the top of /etc/init.d/pulseaudio, because update-rc.d wouldn't
cooperate, and ran asoundconf reset-default-card at the
In my case the problem was solved using this:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/318942
But I'm not sure if everyone experiencing this bug is using a hp mini
nettop (or if it might work for you anyway). Good luck!
--
[jaunty] Sound muted after boot
i got the same problem here. i can turn my sound on again by booting
windows... so where can be the problem?
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I'm having the same problem as Alexander - sound on the main speakers
NEVER works. Master channel gives no output, but headphone jack works
just fine. HP mini 1035nr. Fresh install of jaunty RC1, upgraded to
latest. It seems like sometimes alsa starts with audio muted on both the
Master and PCM
Well, this morning again I had a Master channel muted, even with the
Audio settings management enabled. Now I'm officially confused.
Daniel, I don't know what can I do in order to debug the problem. Can
you take a quick look, please?
--
[jaunty] Sound muted after boot
Since I enabled the Audio settings management in
System-Administration-Services some days ago, I can't reproduce the
problem. Maybe a coincidence?
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because you are a member of Ubuntu
Bugs,
Ricardo: I'm not sure you are experiencing the same bug. For me, the
sound is *always* muted. Also enabling the Audio settings management
in the services did not improve things for me, as I said above.
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this
I'd just booted my computer this morning, and again I had a Master
channel muted. This bug is definitely NOT solved for me.
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Bad luck: today I booted the computer again, and I still had the Master
channel muted. I don't know what else I can do :(
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I did have a home-grown ALSA config file, though system-wide in
/etc/asound.conf containing the same config as yours. Removing did
indeed *not* solve the problem.
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because you are a member
** Attachment added: Audio device unmuted after running sudo
/lib/udev/alsa-utils
http://launchpadlibrarian.net/25380624/Pantallazo-1.png
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because you are a member of Ubuntu
Bugs,
Today, I turn on the computer and I see the sound muted again. Alsamixer
shows the device muted, too.
After doing sudo /lib/udev/alsa-utils in a terminal prompt, the device
gets unmuted.
I attach two screenshots (before and after running sudo /lib/udev/alsa-
utils, respectively).
** Attachment
I can confirm that executing sudo /lib/udev/alsa-utils unmutes my
soundcard.
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
More info, step by step:
1. I boot the computer.
2. When GDM appears, I go into VT1 (Ctrl-Alt-F1) and log into my user.
3. If I do alsamixer -Dhw:0 or alsamixer -c0, I get all the channels
unmuted.
4. If I then do alsamixer, I get only one muted PulseAudio channel, and the
following error
OK, now I can see the problem. I't my fault. We had two files,
~/.asoundrc and ~/.asoundrc.asoundconf. The last one contained the
following:
pcm.!default { type pulse }
ctl.!default { type pulse }
The above was causing troubles. I'd just removing the two files, and now
it seems to works
Seems to be a problem in the udev rule. I've patched the /etc/init.d
/alsa-utils script this way:
case $1 in
start)
date /root/alsa-utils.log # Log the script startups
EXITSTATUS=0
TARGET_CARD=$2
[...]
So I can see when the script has been started. And I see that the
I can't confirm that the problem is in the udev rule. I manually
created:
$ cd /etc/rc2.d
$ sudo ln -s ../init.d/alsa-utils S40alsa-utils
so now alsa-utils is always called at boot time. However, the mixer is
still muted when I go into GNOME.
--
[jaunty] Sound muted after boot
I can confirm this problem in my Jaunty, too. However, it's not always
reproducible: sometimes the audio is properly restored after boot, and
sometimes is muted. The problem appears in Jaunty; working perfectly in
Intrepid.
$ cat /proc/asound/cards
0 [VT82xx ]: HDA-Intel - HDA VIA VT82xx
Upon sudo invoke-rc.d alsa-utils, the mixer levels seem to get saved and
restored successfully. What else can I check here?
I noticed that in System-Administration-Services, Audio settings
management had been unticked, though ticking it did not solve the
problem.
--
[jaunty] Sound muted after
** Package changed: ubuntu = alsa-driver (Ubuntu)
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
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
** Attachment added: amixer_Dhw:0_after_set_vol
http://launchpadlibrarian.net/24593219/amixer_Dhw%3A0_after_set_vol
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: amixer_Dhw:0_after_boot
http://launchpadlibrarian.net/24593210/amixer_Dhw%3A0_after_boot
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: asound.state_after_setting_vol
http://launchpadlibrarian.net/24593238/asound.state_after_setting_vol
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: asound.state_after_boot
http://launchpadlibrarian.net/24593230/asound.state_after_boot
--
[jaunty] Sound muted after boot
https://bugs.launchpad.net/bugs/352732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
78 matches
Mail list logo
