On 08/02/13 08:32, Aleksander Morgado wrote:
> Make sure we cleanup all the signals when we remove our internal reference to
> the 'MMManager' object.
> ---
> src/modem-manager/nm-modem-manager.c | 64
>
> 1 file changed, 51 insertions(+), 13 deletions(-)
Ple
The 'GDBusObjectManagerClient' won't signal added or removed objects when it
was created but no name owner was available in the bus. We can still use it for
name-owner changes, but in order to have added/removed object signals, we'll
need to re-create the whole 'MMManager' when we know the service
Make sure we cleanup all the signals when we remove our internal reference to
the 'MMManager' object.
---
src/modem-manager/nm-modem-manager.c | 64
1 file changed, 51 insertions(+), 13 deletions(-)
diff --git a/src/modem-manager/nm-modem-manager.c
b/src/mode
The 'GDBusObjectManagerClient' won't signal added or removed objects when it
was created but no name owner was available in the bus. We can still use it for
name-owner changes, but in order to have added/removed object signals, we'll
need to re-create the whole 'MMManager' when we know the service
Make sure we cleanup all the signals when we remove our internal reference to
the 'MMManager' object.
---
src/modem-manager/nm-modem-manager.c | 64
1 file changed, 51 insertions(+), 13 deletions(-)
diff --git a/src/modem-manager/nm-modem-manager.c
b/src/mode
On Thu, 2013-02-07 at 16:47 +0100, Aleksander Morgado wrote:
> We avoid requesting to auto-start the service when the 'MMManager' is created,
> so that we can use it to follow name-owner changes (when auto-starting
> requested the 'MMManager' creation may fail).
>
> We still handle the periodic po
We avoid requesting to auto-start the service when the 'MMManager' is created,
so that we can use it to follow name-owner changes (when auto-starting
requested the 'MMManager' creation may fail).
We still handle the periodic poking to the service, but instead of re-creating
the 'MMManager', we jus
