On Thu, Dec 13, 2007 at 08:23:20AM +0000, Neil Bird wrote: > > Of late on my main box (I don't know for how long), pretty much any > ALSA-based app. (audacious, xmms, etc.) gives the following error: > > ALSA lib pcm.c:2106:(snd_pcm_open_conf) Cannot open shared library > /usr/lib/alsa-lib/libasound_module_pcm_empty.so > > Has anyone got a clue as to what this is about? Some audio things do > work, like MythTV, audacity (editor), but I don't know how they're accessing > the sound subsystem.
I didn't reply to this mail, as I have never seen it and it looks like
no one on the list had, still a reply is due.
> The reason I'm asking here is that, although I think I have all standard
> alsa RPMs installed, I initially started using ALSA from atrpms in the early
> Fedora days (even maybe before?), and I'm not certain I've ended up with an
> entirely pukka configuration.
>
> I'm running F7, which has only ever been upgraded (yes, I know, but it's
> always 'just worked' and been less hassle than a reinstall) since Red Hat 6.1.
I would start rpm -V'ing all packages that you think could be ill. In
doubt nuke everything [*] alsa related even with rpm -e --nodeps
(don't tell anyone I ever used the nodeps word ...), make sure there
is nothing regarding alsa anywhere on your system and then let
smart fix
cure everything again.
[*] The assumption is that missing alsa libs and tools will not break
any login procedure, rpm itself etc. If you do see something
suspicious like gdm depending on alsa for "bells and whistles"
then don't remove alsa ... :)
--
Axel.Thimm at ATrpms.net
pgpWpEc5EzqQl.pgp
Description: PGP signature
_______________________________________________ atrpms-users mailing list [email protected] http://lists.atrpms.net/mailman/listinfo/atrpms-users
