[Touch-packages] [Bug 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)
** Changed in: ubuntu-touch-session (Ubuntu RTM) Status: Confirmed = Fix Released -- 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: Fix Released 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: Fix Released 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)
** Changed in: canonical-devices-system-image Status: Confirmed = Fix Released -- 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: Fix Released 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)
** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu) Status: Confirmed = Invalid ** Changed in: unity8 (Ubuntu RTM) Status: New = Invalid -- 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: New 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)
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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)
** Branch linked: lp:ubuntu/ubuntu-touch-session -- 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 “indicator-sound” package in Ubuntu: Invalid Status in “ubuntu-touch-session” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Confirmed 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: 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)
This bug was fixed in the package ubuntu-touch-session - 0.108+15.04.2014~rtm-0ubuntu1 --- ubuntu-touch-session (0.108+15.04.2014~rtm-0ubuntu1) 14.09; urgency=low [ Ted Gould ] * Override indicator-sound to wait for pulse audio (LP: #1389008) -- Ubuntu daily release ps-jenk...@lists.canonical.com Tue, 11 Nov 2014 21:44:44 + ** Changed in: ubuntu-touch-session (Ubuntu RTM) Status: New = Fix Released -- 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 “indicator-sound” package in Ubuntu: Invalid Status in “ubuntu-touch-session” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Confirmed Status in “indicator-sound” package in Ubuntu RTM: Invalid Status in “ubuntu-touch-session” package in Ubuntu RTM: Fix Released 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)
** Branch linked: lp:~ted/ubuntu-touch-session/indicator-sound- override-v2 -- 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 “indicator-sound” package in Ubuntu: Invalid Status in “ubuntu-touch-session” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Confirmed 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: 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)
** Tags added: touch-2014-11-06 -- 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 Sound Menu: Triaged Status in “indicator-sound” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Confirmed 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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 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 “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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)
** Also affects: ubuntu-touch-session (Ubuntu RTM) Importance: Undecided Status: New -- 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 “indicator-sound” package in Ubuntu: Invalid Status in “ubuntu-touch-session” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Confirmed Status in “indicator-sound” package in Ubuntu RTM: Invalid Status in “ubuntu-touch-session” 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/ubuntu/+source/indicator-sound/+bug/1389008/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)
** Tags added: rtm14 -- 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 Sound Menu: Triaged Status in “indicator-sound” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Confirmed 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)
** Branch linked: lp:~ted/ubuntu-touch-session/indicator-sound-override -- 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 Sound Menu: Triaged Status in “indicator-sound” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Confirmed 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)
** Changed in: unity8 (Ubuntu RTM) Importance: Undecided = Critical -- 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 Sound Menu: Triaged Status in “indicator-sound” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Confirmed 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New = Confirmed -- 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 Sound Menu: Triaged Status in “indicator-sound” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Confirmed 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-sound (Ubuntu) Status: New = Confirmed -- 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 Sound Menu: Triaged Status in “indicator-sound” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Confirmed 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)
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. ** Attachment added: upstart.svg https://bugs.launchpad.net/indicator-sound/+bug/1389008/+attachment/4255258/+files/upstart.svg -- 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 Sound Menu: Triaged Status in “indicator-sound” package in Ubuntu: New 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)
Oh, my. Found the issue. Unity8 is starting the indicators BEFORE unity8 starts. -- 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 Sound Menu: Triaged Status in “indicator-sound” package in Ubuntu: New 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)
@ted: I added the Unity8 project to this bug report then. ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Also affects: unity8 (Ubuntu RTM) Importance: Undecided Status: New -- 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 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)
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 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 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)
Is it not possible for the indicator to retry the connection? -- 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 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
