I installed fresh 9.04 x64 ext4, and I seem to get mute on boot. And
when I unmute it and make sure PCM volume is turned up there is still no
sound. Last night I was able to fix it by selecting other sound options
(cards?) and eventually went back to my HDA Intel (alsa mixer) and PCM
was set to bot
I still have the same problem in my fully updated Jaunty: no sound after
boot. However, the issue is not always reproducible: sometimes the audio
is properly restored after boot, and sometimes is muted.
$ cat /proc/asound/cards
0 [VT82xx ]: HDA-Intel - HDA VIA VT82xx
HDA VIA
Although this bug is fixed, alsa-utils is still shipping with muted
defaults so there is no sound after a fresh ubuntu install.
--
[Jaunty] Sound channels are muted after reboot
https://bugs.launchpad.net/bugs/316430
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Sean, you're probably experiencing bug #322374
--
[Jaunty] Sound channels are muted after reboot
https://bugs.launchpad.net/bugs/316430
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
That is a different bug. I guess it is some kind of race condition what
gets started first, either pulseaudio or the canberra startup sound. If
you don't have alsa configured to use pulseaudio, then canberra, if it
gets started before pulse, probably detects that no pulseaudio is
running and then u
I'm getting a situation where the login sounds play, but the GNOME mixer
seems to think there's no output devices and similarly I get no sound in
things like the Movie Player.
The usual suspects look like this:
$ cat /proc/asound/cards
0 [Intel ]: HDA-Intel - HDA Intel
See Bug 320798.
--
[Jaunty] Sound channels are muted after reboot
https://bugs.launchpad.net/bugs/316430
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
https://lists.ubuntu.com/m
See Bug 320798.
--
[Jaunty] Sound channels are muted after reboot
https://bugs.launchpad.net/bugs/316430
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
https://lists.ubuntu.com/m
This bug was fixed in the package alsa-utils - 1.0.18-1ubuntu7
---
alsa-utils (1.0.18-1ubuntu7) jaunty; urgency=low
[ Daniel T Chen ]
* Add fixes from git:
- force_state_reinit_when_new_mixer_elements_exist.patch,
- fix_possible_fpe_speaker-test.patch
* Ensure sound chan
I can confirm that deleting those two lines solves my case as well.
@Daniel:
In udev rules is forking a process which waits for a file or files
deprecated?
I notice that the hotplug.functions file is added to udev with a debian
patch and that Ubuntu no longer uses the debian udev package.
--
The issue is solely the fault of alsa-utils's incorrect udev.script.
** Changed in: udev (Ubuntu)
Status: New => Invalid
** Changed in: alsa-utils (Ubuntu)
Importance: Undecided => Low
Assignee: (unassigned) => Daniel T Chen (crimsun)
Status: Confirmed => Fix Committed
--
Commenting the two lines which referenced that file/functions from that
file made it work again.
I'm adding udev to this report as this is the package where the
according file is included in Debian.
** Also affects: udev (Ubuntu)
Importance: Undecided
Status: New
--
[Jaunty] Sound cha
I think I found the problem:
sebast...@sebastian-laptop:~$ /lib/udev/alsa-utils
.: 11: Can't open /lib/udev/hotplug.functions
sebast...@sebastian-laptop:~$ dpkg -S hotplug.functions
dpkg: *hotplug.functions* not found.
--
[Jaunty] Sound channels are muted after reboot
https://bugs.launchpad.net
** Attachment added: "dmesg - I didn't find anything suspicious, but I thought
I should add it anyway"
http://launchpadlibrarian.net/21329700/dmesg.txt
--
[Jaunty] Sound channels are muted after reboot
https://bugs.launchpad.net/bugs/316430
You received this bug notification because you are
** Attachment added: "output of amixer -Dhw:0 after running
"/etc/init.d/alsa-utils start""
http://launchpadlibrarian.net/21329665/amixer_after_alsa-utils_start.txt
--
[Jaunty] Sound channels are muted after reboot
https://bugs.launchpad.net/bugs/316430
You received this bug notification bec
** Attachment added: "asound.state directly after reboot"
http://launchpadlibrarian.net/21329642/asound.state
--
[Jaunty] Sound channels are muted after reboot
https://bugs.launchpad.net/bugs/316430
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
** Attachment added: "amixer -Dhw:0 output directly after reboot"
http://launchpadlibrarian.net/21329604/amixer.txt
--
[Jaunty] Sound channels are muted after reboot
https://bugs.launchpad.net/bugs/316430
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Please attach, separately, the contents of /var/lib/alsa/asound.state
and the output from `amixer -Dhw:0'. (Be sure to also include a separate
`amixer -Dhw:$i' output for each $i that corresponds to card indices in
/proc/asound/cards.)
--
[Jaunty] Sound channels are muted after reboot
https://bug
I can confirm this problem on my laptop.
In /var/lib/alsa/asound.state it looks like the mixers should be turned up.
Also the following works:
sudo /etc/init.d/alsa-utils stop
alsamixer -c0
#changing some levels
sudo /etc/init.d/alsa-utils start
#everything is reset again to the level before stop
** Attachment added: "messages"
http://launchpadlibrarian.net/21131309/messages
--
[Jaunty] Sound channels are muted after reboot
https://bugs.launchpad.net/bugs/316430
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
20 matches
Mail list logo
