Christian Becke schrieb:
> However, this does not work in
> my tests with a wired and a wireless interface (i.e. the hooks are run,
> but the link state is not as expected).
I'll have to correct this: the patch does work if the connection is
disconnected using the "Disconnect" button of network-ma
Dan Williams schrieb:
> So here's how you'd go about doing this. The dispatcher is currently
> run async and its result is ignored. First, you need to fix up the
> dispatcher to not return the dbus action method until all the scripts
> have completed.
AFAICT the dispatcher scripts are already ru
Alexander Sack a écrit :
> For me it would feel enough to do proper logging with timestamps, so if users
> start filing bugs about "NM times out on connect" or "NM does not connect",
> we
> can easily identify that they have bogus scripts etc.
How hard would it be to have a popup with the name
On Mon, Oct 05, 2009 at 06:36:48PM -0700, Dan Williams wrote:
>
> So here's how you'd go about doing this. The dispatcher is currently
> run async and its result is ignored. First, you need to fix up the
> dispatcher to not return the dbus action method until all the scripts
> have completed. N
On Mon, 2009-10-05 at 19:41 -0400, C. Scott Ananian wrote:
> We'd like to run some hook function after NM thinks the connection is
> 'connected' and before it reports the 'connected' status to NM
> clients. In particular, we find that our users try to connect to
> broken networks of some sort or a
We'd like to run some hook function after NM thinks the connection is
'connected' and before it reports the 'connected' status to NM
clients. In particular, we find that our users try to connect to
broken networks of some sort or another with no way to reach the
outside world, even though NM repor
