dx-packages team mailing list archive
-
dx-packages team
-
Mailing list archive
-
Message #24445
[Bug 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)
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.
** No longer affects: indicator-sound
** Changed in: indicator-sound (Ubuntu)
Status: Confirmed => Invalid
** Changed in: indicator-sound (Ubuntu RTM)
Status: New => Invalid
** Changed in: ubuntu-touch-session (Ubuntu)
Status: New => In Progress
** Changed in: ubuntu-touch-session (Ubuntu)
Assignee: (unassigned) => Ted Gould (ted)
--
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 “indicator-sound” package in Ubuntu:
Invalid
Status in “ubuntu-touch-session” package in Ubuntu:
In Progress
Status in “unity8” package in Ubuntu:
Confirmed
Status in “indicator-sound” package in Ubuntu RTM:
Invalid
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/ubuntu/+source/indicator-sound/+bug/1389008/+subscriptions