it appears the bug is due to pulseaudio being wrongly configured; even after manually starting pulseaudio (/usr/bin/esd is a wrapper for PA), there is no daemon listening on port 16001. However, I have found that GNOME does start after a timeout (appeared to be more than 30 seconds though?), if you happen to wait long enough. But that can also be due to two other factors:
- I did a apt-get --reinstall install ubuntu-desktop before diving into this problem (which I believe pulled in some missing pulseaudio packages)
- I manually started /usr/bin/esd from VT1 (but I'm assuming that's also done by the GNOME login script)
PA is not running when I start a KDE session; manually starting PA gives the ALSA messages that I also mentioned in the previous post. Full PA output log attached.
arno@master:~$ LC_MESSAGES=C pulseaudio
[...]
ALSA lib pcm.c:2145:(snd_pcm_open_noupdate) Unknown PCM hw:0
E: alsa-util.c: Error opening PCM device hw:0: No such file or directory
E: module.c: Failed to load module "module-alsa-sink" (argument: "device_id=0 sink_name=alsa_output.pci_1106_3059_sound_card_0_alsa_playback_0"): initialization failed.
[...]
ALSA lib pcm.c:2145:(snd_pcm_open_noupdate) Unknown PCM hw:1
E: alsa-util.c: Error opening PCM device hw:1: No such file or directory
E: module.c: Failed to load module "module-alsa-source" (argument: "device_id=1 source_name=alsa_input.usb_device_c45_60af_noserial_if1_sound_card_0_alsa_capture_0"): initialization failed.
it appears the bug is due to pulseaudio being wrongly configured; even after manually starting pulseaudio (/usr/bin/esd is a wrapper for PA), there is no daemon listening on port 16001. However, I have found that GNOME does start after a timeout (appeared to be more than 30 seconds though?), if you happen to wait long enough. But that can also be due to two other factors:
- I did a apt-get --reinstall install ubuntu-desktop before diving into this problem (which I believe pulled in some missing pulseaudio packages)
- I manually started /usr/bin/esd from VT1 (but I'm assuming that's also done by the GNOME login script)
PA is not running when I start a KDE session; manually starting PA gives the ALSA messages that I also mentioned in the previous post. Full PA output log attached.
arno@master:~$ LC_MESSAGES=C pulseaudio (snd_pcm_ open_noupdate) Unknown PCM hw:0 alsa_output. pci_1106_ 3059_sound_ card_0_ alsa_playback_ 0"): initialization failed. (snd_pcm_ open_noupdate) Unknown PCM hw:1 alsa-source" (argument: "device_id=1 source_ name=alsa_ input.usb_ device_ c45_60af_ noserial_ if1_sound_ card_0_ alsa_capture_ 0"): initialization failed.
[...]
ALSA lib pcm.c:2145:
E: alsa-util.c: Error opening PCM device hw:0: No such file or directory
E: module.c: Failed to load module "module-alsa-sink" (argument: "device_id=0 sink_name=
[...]
ALSA lib pcm.c:2145:
E: alsa-util.c: Error opening PCM device hw:1: No such file or directory
E: module.c: Failed to load module "module-