To Cirroz: Please see bug #330056 for a simple patch that should resolve
your error. Your problem is not the same as that reported by this bug.
--
01ifupdown does not receive down event
https://bugs.launchpad.net/bugs/263712
You received this bug notification because you are a member of Ubuntu
I have error log nm-dispatcher.action: Script
'/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1. when
up/down pptp connection
there are several cases in the script
/etc/NetworkManager/dispatcher.d/01ifupdown: up, down, pre-up and post-down
but with pptp the script starts
ok thanks. sometimes dbus has instabilities. maybe that caused the
confusion. or NM upload fixed it. Thanks for verifying.
** Changed in: network-manager (Ubuntu)
Status: Incomplete = Fix Released
--
01ifupdown does not receive down event
https://bugs.launchpad.net/bugs/263712
You
tested again at hardy with (network-manager 0.6.6-0ubuntu5) - it works as
expected
introducing 'env | logger -t $*' into
/etc/NetworkManager/dispatcher.d/01ifupdown produces something like attached
** Attachment added: hardy.log
http://launchpadlibrarian.net/17247736/hardy.log
--
OK - the same correct behaviour occurs with up to date intrepid. Seamed
to be my fault. You can resolve my report as invalid. THX.
--
01ifupdown does not receive down event
https://bugs.launchpad.net/bugs/263712
You received this bug notification because you are a member of Ubuntu
Bugs, which is
My fault was: last test was done with NM 0.6.6, but not with 0.7. I did not
made a full upgrade.
Tested now again at intrepid alpha 4 with (network-manager 0.7) - it works NOT
introducing 'env | logger -t $*' into
/etc/NetworkManager/dispatcher.d/01ifupdown produces something like attached
**
last log was not complete ... take this one
** Attachment added: intrepid.log
http://launchpadlibrarian.net/17252471/intrepid.log
--
01ifupdown does not receive down event
https://bugs.launchpad.net/bugs/263712
You received this bug notification because you are a member of Ubuntu
Bugs, which
Did this start with nm 0.7 or before? Does this also happen when the
ip/route actually changes on reconnect?
please attach a complete complete syslog taken after reproducing this.
** Changed in: network-manager (Ubuntu)
Importance: Undecided = Medium
Status: New = Incomplete
--
