On Fri, 2011-02-11 at 14:33 +0000, 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 certainly can't rule out that this problem existed in karmic either. It is just a warning afterall and perhaps I have just been ignoring it for more releases than I remember. Why don't we look at this another way... in what release was it supposed to have been renamed? Once we can determine that it was something that was supposed to happen and when, we can assess how relevant this bug is or whether it's really quite obsolete and I should just rename the files manually. I am pretty sure this has happened on more than just one Lucid machine I have around here though. -- 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
