touch-packages team mailing list archive

Thread
Date

[Bug 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)

To: touch-packages@xxxxxxxxxxxxxxxxxxx
From: Pat McGowan <pat.mcgowan@xxxxxxxxxxxxx>
Date: Tue, 13 Jan 2015 22:00:20 -0000
Reply-to: Bug 1389008 <1389008@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

ubuntu-touch-session sync

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

** Changed in: canonical-devices-system-image
       Status: New => Confirmed

** Changed in: canonical-devices-system-image
    Milestone: None => ww05-2015

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-sound in Ubuntu.
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 the base for Ubuntu mobile products:
  Confirmed
Status in indicator-sound package in Ubuntu:
  Invalid
Status in ubuntu-touch-session package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Invalid
Status in indicator-sound package in Ubuntu RTM:
  Invalid
Status in ubuntu-touch-session package in Ubuntu RTM:
  Confirmed
Status in unity8 package in Ubuntu RTM:
  Invalid

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/canonical-devices-system-image/+bug/1389008/+subscriptions