Public bug reported:
The pulseaudio upstart user session job from ubuntu-touch-session,
/usr/share/upstart/sessions/pulseaudio.conf, runs a post-start script
that polls for /run/user/`id -u`/pulse/dbus-socket. Versions of
pulseaudio in wily or later do not appear to create this socket anymore;
they only create /run/user/$id/pulse/native.
It's possible this is because the /etc/pulse/touch.pa config is not
being properly applied and therefore module-dbus-protocol.so is not
being loaded. Regardless of the root cause, the symptom I'm seeing is
that an emulator instance running wily fails to ever start the
pulseaudio job.
The post-start script shown in this job, where the script polls waiting
for the creation of the socket, is also quite bad. upstart does have
inotify support; the affected jobs can instead be started directly on
creation of the relevant socket.
** Affects: ubuntu-touch-session (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-touch-session in
Ubuntu.
https://bugs.launchpad.net/bugs/1526077
Title:
ubuntu-touch-session pulseaudio job looks for wrong socket
Status in ubuntu-touch-session package in Ubuntu:
New
Bug description:
The pulseaudio upstart user session job from ubuntu-touch-session,
/usr/share/upstart/sessions/pulseaudio.conf, runs a post-start script
that polls for /run/user/`id -u`/pulse/dbus-socket. Versions of
pulseaudio in wily or later do not appear to create this socket
anymore; they only create /run/user/$id/pulse/native.
It's possible this is because the /etc/pulse/touch.pa config is not
being properly applied and therefore module-dbus-protocol.so is not
being loaded. Regardless of the root cause, the symptom I'm seeing is
that an emulator instance running wily fails to ever start the
pulseaudio job.
The post-start script shown in this job, where the script polls
waiting for the creation of the socket, is also quite bad. upstart
does have inotify support; the affected jobs can instead be started
directly on creation of the relevant socket.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-session/+bug/1526077/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
