dx-packages team mailing list archive

[Michał Sawicz <michal.sawicz@xxxxxxxxxxxxx>]

> 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 ;)

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1389008

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

Status in Sound Menu:
  Triaged
Status in “indicator-sound” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New
Status in “indicator-sound” package in Ubuntu RTM:
  New
Status in “unity8” package in Ubuntu RTM:
  New

Bug description:
  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?

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-sound/+bug/1389008/+subscriptions