Indicators are started while dbus session is not ready yet

[Xavi Garcia]

Related to bug: #1432689

I've observed that when starting the sound indicator sometimes the session dbus is not ready, and when the indicator tries to acquire its dbus name it gets an error.

I've created a branch that does a retry mechanism to wait for the connection to be available, but that would be a temporary workaround.

This is happening more often in sound indicator as the very first thing that indicator does is to acquire the dbus name, but it might happen to other indicators and or processes.

Note: is far more easy to recreate this on the Nexus 4 than in the BQ (in fact I didn't manage to recreate it in the BQ yet)

[pitwalker (pitwalker)]

:-(

On Fri, Dec 11, 2015 at 12:30 PM, Xavi Garcia <
<email address hidden>> wrote:

> Public bug reported:
>
> Related to bug: #1432689
>
> I've observed that when starting the sound indicator sometimes the
> session dbus is not ready, and when the indicator tries to acquire its
> dbus name it gets an error.
>
> I've created a branch that does a retry mechanism to wait for the
> connection to be available, but that would be a temporary workaround.
>
> This is happening more often in sound indicator as the very first thing
> that indicator does is to acquire the dbus name, but it might happen to
> other indicators and or processes.
>
> Note: is far more easy to recreate this on the Nexus 4 than in the BQ
> (in fact I didn't manage to recreate it in the BQ yet)
>
> ** Affects: upstart
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to upstart
> .
> https://bugs.launchpad.net/bugs/1525183
>
> Title:
> Indicators are started while dbus session is not ready yet
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/upstart/+bug/1525183/+subscriptions
>