[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
This release of Ubuntu is no longer receiving maintenance updates. If
this is still an issue on a maintained version of Ubuntu please let us
know.
** Changed in: alsa-driver (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
B
After manually reinstalling all alsa i obtained
alsa reload
/sbin/alsa: Warning: Processes using sound devices: 2047(pulseaudio).
Unloading ALSA sound driver modules: snd-hda-codec-hdmi snd-hda-codec-realtek
snd-hda-intel snd-hda-codec snd-hwdep snd-pcm-oss snd-mixer-oss snd-pcm
snd-seq-oss snd
I'm guessing the OP had customized alsa-base in a previous (now EOL)
release, and the file was not renamed. It seems like an obsolete issue
to me.
Can anyone verify that this happens on a fresh install of Lucid (or even
an upgrade from Karmic where the alsa-base file has not been modified)?
--
Y
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: alsa-driver (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/708672
Title:
On Fri, 2011-02-11 at 14:33 +, David Henningsson wrote:
> But looking at Karmic's file list: http://packages.ubuntu.com/karmic/all
> /alsa-base/filelist - the alsa-base file there is already named .conf,
> so how did the non-.conf file get onto your file system in the first
> place?
I certainl
But looking at Karmic's file list: http://packages.ubuntu.com/karmic/all
/alsa-base/filelist - the alsa-base file there is already named .conf,
so how did the non-.conf file get onto your file system in the first
place?
--
You received this bug notification because you are a member of Ubuntu
Bugs
On Fri, 2011-02-11 at 12:35 +, David Henningsson wrote:
> Hmm, seems I was mistaken. There is a postinst script in alsa-utils that
> renames /etc/modprobe.d/sound to /etc/modprobe.d/sound.conf - but that
> doesn't help here, I guess.
No, it doesn't.
> Anyway, it's been named .conf as long as
Hmm, seems I was mistaken. There is a postinst script in alsa-utils that
renames /etc/modprobe.d/sound to /etc/modprobe.d/sound.conf - but that
doesn't help here, I guess.
Anyway, it's been named .conf as long as I've been interested in
Ubuntu's audio stack, so what upgrade path do you have?
--
On Thu, 2011-02-10 at 15:04 +, David Henningsson wrote:
> Actually, this should have been fixed by the upgrade script
Which upgrade script?
> automatically, it should have renamed "alsa-base" to "alsa-base.conf".
> Question is why it didn't work in your case?
Good question, and which script
Actually, this should have been fixed by the upgrade script
automatically, it should have renamed "alsa-base" to "alsa-base.conf".
Question is why it didn't work in your case?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/708672
Title:
WARNING: All config files need .conf: /etc/modprobe.d/alsa-base
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.
12 matches
Mail list logo
