unity-api-bugs team mailing list archive

[Niklas Wenzel <nikwen.developer@xxxxxxxxx>]

** Description changed:

+ 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?

** Summary changed:

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

** Also affects: ubuntu-rtm
   Importance: Undecided
       Status: New

** Package changed: ubuntu-rtm => indicator-sound (Ubuntu RTM)

-- 
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to The Sound Menu.
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 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