Arch Linux

cookiecaper

Member

Registered: 2007-09-22

Posts: 199

[SOLVED] 32-bit chroot no longer functions with host system PulseAudio

I Syu'd both my host and my chroot and rebooted. Since then, no applications can successfully use pulseaudio from the 32-bit chroot.

Applications that attempt to connect print this:

ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Connection refused

ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Connection refused

Logs show the host PA responds with this:

Jun 26 04:23:30 arch pulseaudio[3952]: [pulseaudio] socket-server.c: bind(): Address already in use
Jun 26 04:23:30 arch pulseaudio[3952]: [pulseaudio] module.c: Failed to load module "module-esound-protocol-unix" (argument: ""): initialization failed.
Jun 26 04:23:30 arch pulseaudio[3952]: [pulseaudio] main.c: Module load failed.
Jun 26 04:23:30 arch pulseaudio[3952]: [pulseaudio] main.c: Failed to initialize daemon.
Jun 26 04:23:30 arch pulseaudio[3949]: [pulseaudio] main.c: Daemon startup failed.

After a little bit of tinkering I don't believe this has anything really to do with esound, though of course I could be wrong.

I found bug Debian's bug #694884 ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649884 ) addresses a similar concern. It suggests that the problem can be resolved by ensuring that the chroot's mountpoints for /run are updated. Mine were not, but changing this didn't seem to solve anything (even after a full host reboot). I also ensured that the June update to filesystem was properly applied in the chroot.

I have emptied /tmp/pulse* and ~/.pulse on both host and chroot. I have a tried a default install of PulseAudio configuration also with no luck.

If I start a PA server within the chroot, applications from the chroot seem to connect fine, but of course, my host is not configured to attempt to go through this and just fails without ever contacting the 32-bit server. At best this is a crappy hack to make it so I can use sound in a 32-bit application if I *have* to.

I'd really like to have this addressed and get back to using sound in my 32-bit chroot since I use it pretty frequently. If anyone has insight into this issue, I'd appreciate some help.

Last edited by cookiecaper (2012-07-02 09:41:23)

DSpider

Member

From: Romania

Registered: 2009-08-23

Posts: 2,273

Re: [SOLVED] 32-bit chroot no longer functions with host system PulseAudio

Reboot your computer if you updated the linux package (the Linux kernel). Always reboot after a kernel update.

---

"How to Succeed with Linux"

I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).

cookiecaper

Member

Registered: 2007-09-22

Posts: 199

Re: [SOLVED] 32-bit chroot no longer functions with host system PulseAudio

Thanks, but that is not relevant to this problem. As I stated in the OP, the problem started after a full host reboot (and another reboot after tweaking some settings didn't fix it).

ngoonee

Forum Fellow

From: Between Thailand and Singapore

Registered: 2009-03-17

Posts: 7,362

Re: [SOLVED] 32-bit chroot no longer functions with host system PulseAudio

It would seem that the switch for /var/run and /run would have caused this, though I have no specific idea how (and more to the point, don't have time now to look into it, sorry).

---

Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.

cookiecaper

Member

Registered: 2007-09-22

Posts: 199

Re: [SOLVED] 32-bit chroot no longer functions with host system PulseAudio

The machine-id file is still contained in /var/lib/dbus/ . For some reason the bind stopped working successfully and the chroot had a different value there than the host system. This was causing the breakage; if I manually synchronize the content of /var/lib/dbus/machine-id in the chroot with the content in the host, everything works again.

Marking SOLVED.

tl;dr: make sure /var/lib/dbus/machine-id is properly bound and/or that the contents of this file are identical on host and chroot.