suspend/resume automatic connection does not work if wicd gui already open

[jwhendy]

Greetings,

There are some similar bugs, but not what I experience:
- https://bugs.launchpad.net/wicd/+bug/585266
- https://bugs.launchpad.net/wicd/+bug/411836
- https://bugs.launchpad.net/wicd/+bug/1245070

I'm on arch linux, using openbox. wicd works fine on suspend/resume *as long as it's not open.* If I've opened the gui for some reason and left it open, when I suspend/resume, it won't do anything. I have to catch that its open and then manually select my network.

Is this the intended/desired behavior?

If not, are there further details I can provide?

$ sudo pacman -Q |grep wicd
wicd 1.7.4-1
wicd-gtk 1.7.4-1

$ uname -a
Linux arch_zbook 4.8.13-1-ARCH #1 SMP PREEMPT Fri Dec 9 07:24:34 CET 2016 x86_64 GNU/Linux

$ sudo cat /var/log/wicd/wicd.log ### last cycle

2017/01/15 08:48:45 :: Connecting to wireless network whammy
2017/01/15 08:48:46 :: Putting interface down
2017/01/15 08:48:46 :: Releasing DHCP leases...
2017/01/15 08:48:46 :: Setting false IP...
2017/01/15 08:48:46 :: Stopping wpa_supplicant
2017/01/15 08:48:46 :: Flushing the routing table...
2017/01/15 08:48:46 :: Putting interface up...
2017/01/15 08:48:48 :: Generating psk...
2017/01/15 08:48:48 :: Attempting to authenticate...
2017/01/15 08:48:49 :: Running DHCP with NO hostname
2017/01/15 08:48:58 ::
2017/01/15 08:48:58 :: DHCP connection successful
2017/01/15 08:48:58 :: not verifying
2017/01/15 08:48:58 :: Connecting thread exiting.
2017/01/15 08:48:58 :: Sending connection attempt result success
2017/01/15 14:32:21 :: Connecting to wireless network whammy
2017/01/15 14:32:22 :: Putting interface down
2017/01/15 14:32:22 :: Releasing DHCP leases...
2017/01/15 14:32:22 :: Setting false IP...
2017/01/15 14:32:22 :: Stopping wpa_supplicant
2017/01/15 14:32:22 :: Flushing the routing table...
2017/01/15 14:32:22 :: Putting interface up...
2017/01/15 14:32:24 :: Generating psk...
2017/01/15 14:32:24 :: Attempting to authenticate...
2017/01/15 14:32:25 :: Running DHCP with NO hostname
2017/01/15 14:32:31 ::
2017/01/15 14:32:31 :: DHCP connection successful
2017/01/15 14:32:31 :: not verifying
2017/01/15 14:32:31 :: Connecting thread exiting.
2017/01/15 14:32:32 :: Sending connection attempt result success
2017/01/15 14:41:26 :: trying to load backend external
2017/01/15 14:41:26 :: trying to load backend ioctl
2017/01/15 14:41:26 :: WARNING: python-iwscan not found, falling back to using iwlist scan.
2017/01/15 14:41:26 :: WARNING: python-wpactrl not found, falling back to using wpa_cli.

[jwhendy (jw-hendy)]

Wow, I just went to report this again and launchpad prompted me to take a look at a related bug... turns out it's my exact bug from 2.75yrs ago. This is still an issue and still annoying. If wicd-gtk is open, wicd will not automatically connect to networks upon resume. If wicd-gtk is *not* open, the automatic connection will occur (when that option is marked for the network, obviously).

[Axel Beckert (xtaran)]

There is a probable fix in https://bugs.launchpad.net/wicd/+bug/1709593

This patch is scheduled for the next upload of wicd to Debian (but only to Debian Experimental for now due to the not yet complete Python 3 migration).

If that works well, I'll also commit that patch to the upstream git repository.

[Vincent Lefevre (vincent-vinc17-net)]

This will partly solve the problem, which is actually more complex to make automatic (re)connection work in a nice way. See:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833929#40
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932042