Opened 5 years ago
Closed 6 months ago
#59103 closed defect (fixed)
pulseaudio @12.99.3_0+x11: autolaunch/dbus not working
Reported by: | quentinmit (Quentin Smith) | Owned by: | Ionic (Mihai Moldovan) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | mohd-akram (Mohamed Akram) | |
Port: | pulseaudio |
Description
pulseaudio autolaunch/dbus doesn't work on my machine. When run from Terminal.app, pulseaudio --start just prints:
$ pulseaudio --start -vvvvv W: [] caps.c: Normally all extra capabilities would be dropped now, but that's impossible because PulseAudio was built without capabilities support. D: [] conf-parser.c: Parsing configuration file '/opt/local/etc/pulse/client.conf' D: [] conf-parser.c: /opt/local/etc/pulse/client.conf.d does not exist, ignoring. E: [] main.c: Daemon startup failed.
When I run it without --start
, we find out it's because pulseaudio can't talk to dbus:
$ pulseaudio W: [] caps.c: Normally all extra capabilities would be dropped now, but that's impossible because PulseAudio was built without capabilities support. dbus[52757]: Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory dbus[52757]: Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory dbus[52757]: Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory dbus[52757]: Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory dbus[52757]: Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory dbus[52757]: Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory dbus[52757]: Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory dbus[52757]: Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory dbus[52757]: Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory dbus[52757]: Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory dbus[52757]: Dynamic session lookup supported but failed: Unable to find launchd socket when setuid E: [] core-util.c: Failed to connect to system bus: Not enough memory W: [] pid.c: Stale PID file, overwriting. E: [] module-coreaudio-device.c: Skipping device with more channels than we support (64) E: [] module-coreaudio-device.c: Skipping device with more channels than we support (64) dbus[52757]: Dynamic session lookup supported but failed: Unable to find launchd socket when setuid W: [] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NoMemory: Not enough memory dbus[52757]: Dynamic session lookup supported but failed: Unable to find launchd socket when setuid W: [] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NoMemory: Not enough memory
The error doesn't make any sense to me because pulseaudio is definitely not setuid:
$ ls -lh /opt/local/bin/pulseaudio -rwxr-xr-x 1 root admin 101K Sep 5 05:28 /opt/local/bin/pulseaudio
Interestingly, if I run pulseaudio /as myself/ with sudo, it doesn't complain about talking to dbus:
$ sudo -u quentin pulseaudio W: [] caps.c: Normally all extra capabilities would be dropped now, but that's impossible because PulseAudio was built without capabilities support. W: [] pid.c: Stale PID file, overwriting. E: [] module-coreaudio-device.c: Skipping device with more channels than we support (64) E: [] module-coreaudio-device.c: Skipping device with more channels than we support (64)
Finally, dbus in general seems to be working fine on my machine. dbus-monitor
happily prints messages on the bus, and the DBUS_LAUNCHD_SESSION_BUS_SOCKET environment variable is set in my bash environment.
Change History (2)
comment:1 Changed 5 years ago by jmroot (Joshua Root)
Owner: | set to Ionic |
---|---|
Status: | new → assigned |
comment:2 Changed 6 months ago by mohd-akram (Mohamed Akram)
Cc: | mohd-akram added |
---|---|
Resolution: | → fixed |
Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
As of [fd9e82cb56afcc86a42b66f4b6ac9c273f8a562b/macports-ports], autospawn should be working and there's no need to launch
pulseaudio
manually. Let me know if you still have issues.