I'm noticing this, because right now my sound system isn't working and I get error messages like (this is no big deal; I'll have it working again in no time):
ALSA lib pcm_direct.c:224:(make_local_socket) connect failed: /tmp/alsa-dmix-12345: No such file or directory
ALSA lib pcm_dmix.c:894:(snd_pcm_dmix_open) unable to connect client
I'm starting evince from the command line with a .pdf file as parameter, and as soon as the window opens, the message appears.
What in the world is a PDF viewer doing with my sound device? I'm just wondering. Maybe this is one call and one dependency that can be optimized away. Or maybe there *is* a reason for using ALSA, but I've never heard any sounds when opening PDF files, and I don't see why that application should have any business in the sound area at all. Click when I follow a hyperlink?
Binary package hint: evince
(for no good reason, I think)
I'm noticing this, because right now my sound system isn't working and I get error messages like (this is no big deal; I'll have it working again in no time): c:224:( make_local_ socket) connect failed: /tmp/alsa- dmix-12345: No such file or directory c:894:( snd_pcm_ dmix_open) unable to connect client
ALSA lib pcm_direct.
ALSA lib pcm_dmix.
I'm starting evince from the command line with a .pdf file as parameter, and as soon as the window opens, the message appears.
What in the world is a PDF viewer doing with my sound device? I'm just wondering. Maybe this is one call and one dependency that can be optimized away. Or maybe there *is* a reason for using ALSA, but I've never heard any sounds when opening PDF files, and I don't see why that application should have any business in the sound area at all. Click when I follow a hyperlink?