Pulse startup errors
by selfprogrammed from LinuxQuestions.org on (#6DF2V)
I am typing this out by hand, because I could not find a way to capture the error messages on the system console. Thus it will be slightly different from actual appearance.
Code:GPM: mousetype = logi
GPM: gpm_mousetype = logi
starting gpm: /usr/sbin/gpm and some more stuff
timidity test: access to config and patches
# This starts some timidity tests which I wrote long ago to deal with erratic timidity startup.
timidity test: done
Welcome to Linux (blah blah blah)
login:
# Error messages from pulse startup ?, that were delayed just enough to appear here in console output.
Home directory not accessible:Permission denied
ALSA lib pulse.c;242:(pulse connect) PulseAudio: unable to connect: Connection refused
Can't open pcm device 'default'.
Couldn't open ALSA pcm device ('s')
mumap_chunk(): invalid pointerI have not seen such error messages before.
They have not appeared before on this system, nor any of the MANY previous installations I have done.
Question: Has anyone seen such before, or is this some new Hell that I have discovered.
My sound config tool:
I have been writing a sound config tool.
It currently has four settings.
0. no sound mixer (standard ALSA setup, before Pulse)
1. ALSA standard setup
2. ALSA DMIX
everybody uses DMIX, multiple connections allowed
(Have not got DMIX working yet)
3. PulseAudio mixer.
ALSA is redirected to PulseAudio.
Invoking the tool will change the current /etc files to properly configure the sound.
This allows changing the sound setup easily depending upon what is the current need.
I prefer the ALSA choice.
1. XMMS works as I expect. I can play jazz in the background, and work in system consoles.
(Please do ask why I use system console, it is not part of the question.)
Current: I have the PulseAudio Mixer selected, and see the above error messages.
The current config files should have been restored to what Slackware had when it was initially installed.
As far as I know, it is configured to run pulse on user demand. It should not be starting a system pulse daemon.
Later I will probably show more of this, but I want present this initial question before the responders try to reconfigure my system to look like their system. I have no intention of doing that.
I want to fix this tool so it configures properly under multiple conditions, so I need to understand what is going on here. After that, I will fix the tool better, IF I CAN.
I have had trouble finding a way to force ALSA to re-read its config files.
I have read all the ALSA documentation that I can find, and I know about forcing ALSA to re-read card setup, but that does not seem to include the /etc/asound.conf file.
I do not trust it until after the next reboot. But in some ways its seems to respond to mixer change immediately.
Code:GPM: mousetype = logi
GPM: gpm_mousetype = logi
starting gpm: /usr/sbin/gpm and some more stuff
timidity test: access to config and patches
# This starts some timidity tests which I wrote long ago to deal with erratic timidity startup.
timidity test: done
Welcome to Linux (blah blah blah)
login:
# Error messages from pulse startup ?, that were delayed just enough to appear here in console output.
Home directory not accessible:Permission denied
ALSA lib pulse.c;242:(pulse connect) PulseAudio: unable to connect: Connection refused
Can't open pcm device 'default'.
Couldn't open ALSA pcm device ('s')
mumap_chunk(): invalid pointerI have not seen such error messages before.
They have not appeared before on this system, nor any of the MANY previous installations I have done.
Question: Has anyone seen such before, or is this some new Hell that I have discovered.
My sound config tool:
I have been writing a sound config tool.
It currently has four settings.
0. no sound mixer (standard ALSA setup, before Pulse)
1. ALSA standard setup
2. ALSA DMIX
everybody uses DMIX, multiple connections allowed
(Have not got DMIX working yet)
3. PulseAudio mixer.
ALSA is redirected to PulseAudio.
Invoking the tool will change the current /etc files to properly configure the sound.
This allows changing the sound setup easily depending upon what is the current need.
I prefer the ALSA choice.
1. XMMS works as I expect. I can play jazz in the background, and work in system consoles.
(Please do ask why I use system console, it is not part of the question.)
Current: I have the PulseAudio Mixer selected, and see the above error messages.
The current config files should have been restored to what Slackware had when it was initially installed.
As far as I know, it is configured to run pulse on user demand. It should not be starting a system pulse daemon.
Later I will probably show more of this, but I want present this initial question before the responders try to reconfigure my system to look like their system. I have no intention of doing that.
I want to fix this tool so it configures properly under multiple conditions, so I need to understand what is going on here. After that, I will fix the tool better, IF I CAN.
I have had trouble finding a way to force ALSA to re-read its config files.
I have read all the ALSA documentation that I can find, and I know about forcing ALSA to re-read card setup, but that does not seem to include the /etc/asound.conf file.
I do not trust it until after the next reboot. But in some ways its seems to respond to mixer change immediately.