wicd

Disconnect scripts not called if connection is lost

  1. Series 1.6
  2. Bug #455127
Bug #455127 reported by nisc
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
wicd
Fix Released
Low
Adam Blackburn
wicd 1.7.0
Declined for Trunk by Adam Blackburn
1.6
Fix Released
Low
Adam Blackburn
wicd 1.7.0

Bug Description

Wicd 1.6.2.2
Archlinux

As discussed in IRC, the disconnect scripts (/etc/wicd/scripts/*/*) are not called immediately after a connection loss is detected (removing network cable, unstable wlans). They are not run before WICD begins reconnecting to the network.

I need this to inform other software about the connection loss.

Related branches

lp:wicd/1.6
Revision history for this message
Adam Blackburn (adamblackburn) wrote :

I've attempted to fix this in lp:wicd and it works for me, when I drop the connection using the kill switch. On Arch you can try this out by using the wicd-bzr package from AUR. Please let me know if it works.

Revision history for this message
Andrew Psaltis (nacl) wrote :

I'm marking this as released, since nobody has complained that it doesn't work yet.

Changed in wicd:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.