Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)

[Charles Kerr]

Often after boot indicator-sound fails to connect to Pulseaudio and to unity-notifications using libnotify. Therefore, volume notifications aren't shown and changes to the volume role go unnoticed, which then results in improper volume control.

As already mentioned in the original bug description, running "restart indicator-sound" resolves the issue.

Original description:

Happens often after phone boot where changing volume by touch or by phone buttons. Volume correctly changes, but the org.freedesktop.Notifications popup isn't displayed.

The problem seems fixes itself if you run "restart indicator-sound", so maybe there's an issue with i-sound and unity-notifications starting at the same time, with the former querying the latter's capabilities before it's ready for business?

[Niklas Wenzel (nikwen)]

I'm adding log files for comparison when this is broken and when it isn't.

[Ricardo Salveti (rsalveti)]

Making it critical as the phone can get into a state where you're unable to hear alarms and other roles (as you're just controlling the master volume).

[Ricardo Salveti (rsalveti)]

Something made indicator-sound to start a bit earlier than before, which might be causing this race.

It's starting even before pulse, which is only depending on dbus to be up at the session level. We might want to adjust the upstart job to wait for the other pieces to be fully up before starting itself.

[Ricardo Salveti (rsalveti)]

Also, this often happens with mako, but couldn't reproduce it yet on krillin (probably because it's a race).

[Ted Gould (ted)]

Went ahead and rendered the startup sequence of tasks, the indicators are pretty far down the line. Perhaps we can look at when Unity8 is sending the signal for them to start, perhaps to make it at the end of it's init.

[Ted Gould (ted)]

Oh, my. Found the issue. Unity8 is starting the indicators BEFORE unity8 starts.

[Niklas Wenzel (nikwen)]

@ted: I added the Unity8 project to this bug report then.

[Michał Sawicz (saviq)]

> Oh, my. Found the issue. Unity8 is starting the indicators BEFORE unity8 starts.

Yes, because when we were adding that signal, we were told that that's desired ;)

[Michał Sawicz (saviq)]

Is it not possible for the indicator to retry the connection?

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Ted Gould (ted)]

Marking the indicator-sound items as invalid as we had to fix this with an indicator-sound override in ubuntu-touch-session because it has a pulseaudio job that is not in desktop. Eventually that should move to indicator-sound with the pulse job, but that's where the fix will come from today.

[Launchpad Janitor (janitor)]

This bug was fixed in the package ubuntu-touch-session - 0.108+15.04.20141111-0ubuntu1

---------------
ubuntu-touch-session (0.108+15.04.20141111-0ubuntu1) vivid; urgency=low

  [ Ted Gould ]
  * Override indicator-sound to wait for pulse audio (LP: #1389008)
 -- Ubuntu daily release <email address hidden> Tue, 11 Nov 2014 21:44:44 +0000

[Launchpad Janitor (janitor)]

This bug was fixed in the package ubuntu-touch-session - 0.108+15.04.20141111~rtm-0ubuntu1

---------------
ubuntu-touch-session (0.108+15.04.20141111~rtm-0ubuntu1) 14.09; urgency=low

  [ Ted Gould ]
  * Override indicator-sound to wait for pulse audio (LP: #1389008)
 -- Ubuntu daily release <email address hidden> Tue, 11 Nov 2014 21:44:44 +0000

[Oliver Grawert (ogra)]

reverted in RTM due to issues with first boot ...

ubuntu-touch-session (0.108+15.04.20141111-0ubuntu2) 14.09; urgency=medium

  * revert the former override change since it was found to be not working on
    first boot on fresh installs during milestone testing.

ubuntu-touch-session (0.108+15.04.20141111-0ubuntu1) vivid; urgency=low

  [ Ted Gould ]
  * Override indicator-sound to wait for pulse audio (LP: #1389008)

Date: 2014-11-12 17:47:09.485214+00:00

[Pat McGowan (pat-mcgowan)]

ubuntu-touch-session sync