Debian Bug report logs - #557156
wired_connect_mode behavior doesn't match the wicd-manager-settings.conf(5) man page

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Vincent Lefevre <vincent@vinc17.net>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: wicd deconfigures the wired (eth0) interface at suspend or cable unplugged

Date: Thu, 19 Nov 2009 23:41:10 +0100

Package: wicd
Version: 1.6.2.2-3
Severity: important

When I suspend my laptop or unplug the Ethernet cable, wicd
deconfigures the wired (eth0) interface, even though I wasn't
connected via wicd. I don't know whether wicd does that directly
or whether this is done by dhclient (the logs show that dhclient
is started at this time, and it is started by wicd, because if I
stop the wicd daemon, this no longer happens). In any case, wicd
is the culprit, because starting dhclient when I suspend my laptop
or unplug the Ethernet cable makes no sense!

This is an important problem, because at wake up or when I plug in
the cable, the eth0 interface isn't reconfigured and my connection
remains lost.

Note: in manager-settings.conf, I have "wired_connect_mode = 1",
in order not to connect automatically. I don't use wicd for eth0
because it is too limited: depending on the environment (remote
router), I sometimes need a static IP address and sometimes need
to use DHCP (this is possible with ifup + guessnet, but not with
wicd).

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.31-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages wicd depends on:
ii  adduser                     3.111        add and remove users and groups
ii  dbus                        1.2.16-2     simple interprocess messaging syst
ii  debconf [debconf-2.0]       1.5.28       Debian configuration management sy
ii  dhcp3-client                3.1.3-1      DHCP client
ii  ethtool                     6+20090323-3 display or change Ethernet device 
ii  iproute                     20090324-1   networking and traffic control too
ii  iputils-ping                3:20071127-2 Tools to test the reachability of 
ii  lsb-base                    3.2-23       Linux Standard Base 3.2 init scrip
ii  net-tools                   1.60-23      The NET-3 networking toolkit
ii  psmisc                      22.8-1       utilities that use the proc file s
ii  python                      2.5.4-2      An interactive high-level object-o
ii  python-dbus                 0.83.0-1     simple interprocess messaging syst
ii  python-glade2               2.16.0-1     GTK+ bindings: Glade support
ii  python-gtk2                 2.16.0-1     Python bindings for the GTK+ widge
ii  python-support              1.0.4        automated rebuilding support for P
ii  python-urwid                0.9.8.4-1    curses-based UI/widget library for
ii  wireless-tools              29-2         Tools for manipulating Linux Wirel
ii  wpasupplicant               0.6.9-3      client support for WPA and WPA2 (I

Versions of packages wicd recommends:
ii  gksu                          2.0.2-2+b1 graphical frontend to su
ii  python-notify                 0.1.1-2+b1 Python bindings for libnotify
ii  sudo                          1.7.2p1-1  Provide limited super user privile

Versions of packages wicd suggests:
ii  pm-utils                      1.2.6.1-1  utilities and scripts for power ma

-- debconf information excluded

Message #10 received at 557156@bugs.debian.org (full text, mbox, reply):

From: Yves-Alexis Perez <corsac@debian.org>

To: 557156@bugs.debian.org, David Paleino <dapal@debian.org>

Cc: Vincent Lefevre <vincent@vinc17.net>

Subject: Same behavior

Date: Fri, 04 Mar 2011 12:02:56 +0100

I get the same behavior, even with statically configured address. 

I use wicd because it's usually not messing with my setup so that means
I can use it to connect to wireless network easily, but still do stuff
on my own when I need it (configure a static address, only use ipv6,
connect manually to an hidden network or whatever). 

It'd be nice if wicd could not flush the configuration when the link is
lost, especially if it didn't do the configuration initially.

Regards,
-- 
Yves-Alexis

Message #15 received at 557156@bugs.debian.org (full text, mbox, reply):

From: Vincent Lefevre <vincent@vinc17.net>

To: Yves-Alexis Perez <corsac@debian.org>

Cc: 557156@bugs.debian.org, David Paleino <dapal@debian.org>

Subject: Re: Same behavior

Date: Wed, 9 Mar 2011 02:53:11 +0100

found 557156 1.7.0+ds1-6
thanks

On 2011-03-04 12:02:56 +0100, Yves-Alexis Perez wrote:
> I get the same behavior, even with statically configured address. 

Perhaps this wasn't clear, but I also use a statically configured
address (in /etc/network/interfaces, thus outside of wicd). One
problem is that wicd doesn't care and starts dhclient anyway.

I haven't looked closely since my bug report, but the deconfigured
eth0 still occurs after suspend.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)

Message #22 received at 557156@bugs.debian.org (full text, mbox, reply):

From: Vincent Lefevre <vincent@vinc17.net>

To: 557156@bugs.debian.org

Subject: Re: wicd deconfigures the wired (eth0) interface at suspend or cable unplugged

Date: Fri, 6 Jan 2012 10:57:02 +0100

found 557156 1.7.1~b3-3
thanks

This still occurs, at least when the Ethernet cable is unplugged.
In the wicd logs:

[...]
2012/01/06 10:24:34 :: ifconfig eth0 up
2012/01/06 10:24:36 :: Executing /etc/network/if-down.d/avahi-autoipd with params 
2012/01/06 10:24:36 :: /etc/network/if-down.d/avahi-autoipd returned 0
2012/01/06 10:24:36 :: Executing /etc/network/if-down.d/bind9 with params 
2012/01/06 10:24:36 :: /etc/network/if-down.d/bind9 returned 0
2012/01/06 10:24:36 :: Executing /etc/network/if-down.d/postfix with params 
2012/01/06 10:24:36 :: /etc/network/if-down.d/postfix returned 0
2012/01/06 10:24:36 :: Executing /etc/network/if-down.d/wpasupplicant with params 
2012/01/06 10:24:36 :: /etc/network/if-down.d/wpasupplicant returned 0
2012/01/06 10:24:36 :: attempting to set hostname with dhclient
2012/01/06 10:24:36 :: using dhcpcd or another supported client may work better
2012/01/06 10:24:36 :: /sbin/dhclient -v -r eth0
2012/01/06 10:24:37 :: ifconfig eth0 0.0.0.0 
2012/01/06 10:24:37 :: /sbin/ip route flush dev eth0
2012/01/06 10:24:37 :: ifconfig eth0 down
2012/01/06 10:24:37 :: ifconfig eth0 up
[...]

My config has changed a bit, and I now use netplug, but wicd also
confuses netplug, meaning that I lose the network connection.

Note: in the wicd preferences, "Always switch to a wired connection
when available" is unticked. So, wicd should never attempt to modify
the eth0 settings.

As a workaround, one can leave the wired interface blank in the
preferences.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)

Message #27 received at 557156@bugs.debian.org (full text, mbox, reply):

From: David Paleino <dapal@debian.org>

To: 557156@bugs.debian.org

Cc: Vincent Lefevre <vincent@vinc17.net>

Subject: Re: Bug#557156: wicd deconfigures the wired (eth0) interface at suspend or cable unplugged

Date: Fri, 6 Jan 2012 11:37:31 +0100

[Message part 1 (text/plain, inline)]

Hello Vincent,
I thought I at least replied to your other mails. Shame on me, I'm very
sorry. :(

Let me reply also to your 2009 mail -- a bit late though :)

On Thu, 19 Nov 2009 23:41:10 +0100, Vincent Lefevre wrote:

> When I suspend my laptop or unplug the Ethernet cable, wicd
> deconfigures the wired (eth0) interface, even though I wasn't
> connected via wicd. I don't know whether wicd does that directly
> or whether this is done by dhclient (the logs show that dhclient
> is started at this time, and it is started by wicd, because if I
> stop the wicd daemon, this no longer happens). In any case, wicd
> is the culprit, because starting dhclient when I suspend my laptop
> or unplug the Ethernet cable makes no sense!

Ok, I need to check this. I don't connect via cable since some time, so I
could've easily missed this bug.

> [..]
> I don't use wicd for eth0 because it is too limited: depending on the
> environment (remote router), I sometimes need a static IP address and
> sometimes need to use DHCP (this is possible with ifup + guessnet, but not
> with wicd).

There are "wired profiles" you can use for that -- each profile has its own
settings, and you can switch them basing on the network you're trying to
connect to. I guess that "guessnet" automatically understand which network
you're on: if it is true, then this is the only thing missing to wicd. :)


On Fri, 6 Jan 2012 10:57:02 +0100, Vincent Lefevre wrote:

> This still occurs, at least when the Ethernet cable is unplugged.

So the "suspend bug" is gone?

> In the wicd logs:
> 
> [...]
> 2012/01/06 10:24:34 :: ifconfig eth0 up
> 2012/01/06 10:24:36 :: [..]
> 2012/01/06 10:24:36 :: attempting to set hostname with dhclient
> 2012/01/06 10:24:36 :: using dhcpcd or another supported client may work
> better
> 2012/01/06 10:24:36 :: /sbin/dhclient -v -r eth0
> 2012/01/06 10:24:37 :: ifconfig eth0 0.0.0.0 
> 2012/01/06 10:24:37 :: /sbin/ip route flush dev eth0
> 2012/01/06 10:24:37 :: ifconfig eth0 down
> 2012/01/06 10:24:37 :: ifconfig eth0 up
> [...]

In this log, I don't understand when you unplug your cable. Could you please
re-take it so that it is a bit clearer? I'd suggest doing:

  $ tail -f /var/log/wicd/wicd.log

  // send some newlines
  // write something "I'm unplugging the cable", and some more newlines
  // unplug the cable
  // copy-paste

> My config has changed a bit, and I now use netplug, but wicd also
> confuses netplug, meaning that I lose the network connection.

(btw, I've had some requests to use NETLINK in wicd too :))

> Note: in the wicd preferences, "Always switch to a wired connection
> when available" is unticked. So, wicd should never attempt to modify
> the eth0 settings.
> 
> As a workaround, one can leave the wired interface blank in the
> preferences.

If you don't want wicd to mess with eth0 at all then yes, that's the way of
doing it.

Obviously, if you have that box unticked, wicd shouldn't attempt a connection
on plug, nor a disconnection on unplug (unless the connection was started by
itself).

I can't remember if originally it didn't touch interfaces listed
in /etc/network/interfaces -- but it would be nice to support that too.
However I'm quite busy releasing 1.7.1, so this "feature" might come with 1.7.2
or later :)

Thanks, and sorry for not replying for so long,
David

-- 
 . ''`.   Debian developer | http://wiki.debian.org/DavidPaleino
 : :'  : Linuxer #334216 --|-- http://www.hanskalabs.net/
 `. `'`  GPG: 1392B174 ----|---- http://deb.li/dapal
   `-   2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174

[signature.asc (application/pgp-signature, attachment)]

Message #32 received at 557156@bugs.debian.org (full text, mbox, reply):

From: Vincent Lefevre <vincent@vinc17.net>

To: David Paleino <dapal@debian.org>

Cc: 557156@bugs.debian.org

Subject: Re: Bug#557156: wicd deconfigures the wired (eth0) interface at suspend or cable unplugged

Date: Fri, 6 Jan 2012 12:12:39 +0100

Hi David,

On 2012-01-06 11:37:31 +0100, David Paleino wrote:
> On Thu, 19 Nov 2009 23:41:10 +0100, Vincent Lefevre wrote:
> > [..]
> > I don't use wicd for eth0 because it is too limited: depending on the
> > environment (remote router), I sometimes need a static IP address and
> > sometimes need to use DHCP (this is possible with ifup + guessnet, but not
> > with wicd).
> 
> There are "wired profiles" you can use for that -- each profile has its own
> settings, and you can switch them basing on the network you're trying to
> connect to. I guess that "guessnet" automatically understand which network
> you're on: if it is true, then this is the only thing missing to wicd. :)

Yes, guessnet allows one to do various tests. In particular,
I test the MAC address of 192.168.0.1, and I have a special
config for that.

> On Fri, 6 Jan 2012 10:57:02 +0100, Vincent Lefevre wrote:
> > This still occurs, at least when the Ethernet cable is unplugged.
> 
> So the "suspend bug" is gone?

I'm not sure, or it doesn't have always an effect (due to a bug
in the current video driver, I think, the screen remains off, so
that I almost no longer suspend the machine -- anyway I'll have
to do tests for a bug report concerning the video driver problem,
which is a regression).

> > In the wicd logs:
> > 
> > [...]
> > 2012/01/06 10:24:34 :: ifconfig eth0 up
> > 2012/01/06 10:24:36 :: [..]
> > 2012/01/06 10:24:36 :: attempting to set hostname with dhclient
> > 2012/01/06 10:24:36 :: using dhcpcd or another supported client may work
> > better
> > 2012/01/06 10:24:36 :: /sbin/dhclient -v -r eth0
> > 2012/01/06 10:24:37 :: ifconfig eth0 0.0.0.0 
> > 2012/01/06 10:24:37 :: /sbin/ip route flush dev eth0
> > 2012/01/06 10:24:37 :: ifconfig eth0 down
> > 2012/01/06 10:24:37 :: ifconfig eth0 up
> > [...]
> 
> In this log, I don't understand when you unplug your cable. Could
> you please re-take it so that it is a bit clearer?

It was done a few seconds before. In /var/log/syslog:

Jan  6 10:24:31 xvii kernel: [26255.600180] e1000e: eth0 NIC Link is Down
Jan  6 10:24:31 xvii netplugd[16325]: /etc/netplug/netplug eth0 out -> pid 16325
Jan  6 10:24:32 xvii logger: /sbin/ifdown -v eth0

(the ifdown was done by netplug, as expected).

> > As a workaround, one can leave the wired interface blank in the
> > preferences.
> 
> If you don't want wicd to mess with eth0 at all then yes, that's the
> way of doing it.

But it would be nice to be able to see the status.

> Obviously, if you have that box unticked, wicd shouldn't attempt a
> connection on plug, nor a disconnection on unplug (unless the
> connection was started by itself).
> 
> I can't remember if originally it didn't touch interfaces listed
> in /etc/network/interfaces -- but it would be nice to support that too.

Don't forget things like:

mapping eth0
  script guessnet-ifupdown
  map default: eth0-dhcp
  map debug: true
  map timeout: 10

(i.e. with "mapping" instead of "iface").

> However I'm quite busy releasing 1.7.1, so this "feature" might come
> with 1.7.2 or later :)

OK, thanks.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)

Message #37 received at 557156@bugs.debian.org (full text, mbox, reply):

From: Javier Fernández-Sanguino Peña <jfs@debian.org>

To: Debian Bug Tracking System <557156@bugs.debian.org>

Subject: Re: wicd deconfigures the wired (eth0) interface at suspend or cable unplugged

Date: Mon, 21 May 2012 19:14:08 +0200

[Message part 1 (text/plain, inline)]

Package: wicd-daemon
Version: 1.7.2.3-1
Followup-For: Bug #557156

I can confirm that this bug is still present and it completely breaks my
network setup when resuming from suspend. In my case, I have a 
desktop system that uses 'eth1' as its wired interface:

- this interface is configured through /etc/network/interfaces (since Woody, or even
  earlier)

- I have not configured wicd at all, it was just pulled in as a dependency because 
  GNOME's NetworkManager depends on it

- there is no way to disable the suspend script (I have filed a separate bug on this)

When resuming from suspend the following happens:

- /usr/lib/pm-utils/sleep.d/55wicd is run
- the script calls /usr/share/wicd/daemon/autoconnect.py
- this script calls dhclient
- the interface is auto reconfigured to use a dynamic (instead of static IP address)

Please see the attached file generated using 'script' (wicd-test-resume.log)
that shows the behaviour. The /var/log/wicd/wicd.log file (attached is an extract) 
shows that seems to be the behaviour when resuming from suspend.

I'm attaching also my current  /etc/wicd/wired-settings.conf configuration file for review.

As I cannot disable the /usr/lib/pm-utils/sleep.d/55wicd script I've introduced another
script in /etc/pm/sleep.d/00_restart_network that stops dhclient and
reconfigures the interface. Writting this script was a little bit tricky as
there is a race condition in how the power management scripts are run (as wicd
dettachs to a background process). It seems to work well in my system and
prevents this bug. I'm attaching it also here for the benefit of those affected
by this bug.

Please feel free to ask for additional information.

By the way: this bug is pretty serious, in my opinion it makes this package
unsuitable for release. 

Regards

Javier



-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages wicd-daemon depends on:
ii  adduser                         3.113+nmu1
ii  dbus                            1.5.12-1
ii  debconf                         1.5.42
ii  ethtool                         1:3.1-1
ii  iproute                         20120319-1
ii  iputils-ping                    3:20101006-1+b1
ii  isc-dhcp-client [dhcp3-client]  4.2.2.dfsg.1-4
ii  lsb-base                        4.1+Debian2
ii  net-tools                       1.60-24.1
ii  psmisc                          22.16-1
ii  python                          2.7.2-10
ii  python-dbus                     0.84.0-3
ii  python-gobject                  3.2.0-3
ii  python-wicd                     1.7.2.3-1
ii  wireless-tools                  30~pre9-8
ii  wpasupplicant                   0.7.3-6

Versions of packages wicd-daemon recommends:
ii  wicd-gtk [wicd-client]  1.7.2.3-1

Versions of packages wicd-daemon suggests:
ii  pm-utils  1.4.1-9

Versions of packages wicd depends on:
ii  wicd-gtk [wicd-client]  1.7.2.3-1

Versions of packages wicd-gtk depends on:
ii  python         2.7.2-10
ii  python-glade2  2.24.0-3
ii  python-gtk2    2.24.0-3

Versions of packages wicd-gtk recommends:
ii  gksu           2.0.2-6
ii  python-notify  0.1.1-3

Versions of packages python-wicd depends on:
ii  python     2.7.2-10
ii  python2.6  2.6.7-4
ii  python2.7  2.7.3~rc2-2.1

-- debconf information:
* wicd/users: jfs

[wired-settings.conf (text/plain, attachment)]

[wicd-test-resume.log (text/plain, attachment)]

[wicd.log (text/plain, attachment)]

[00_restart_network (text/x-shellscript, attachment)]

Message #42 received at 557156@bugs.debian.org (full text, mbox, reply):

From: Javier Fernández-Sanguino Peña <jfs@debian.org>

To: Debian Bug Tracking System <557156@bugs.debian.org>

Subject: Re: wicd deconfigures the wired (eth0) interface at suspend or cable unplugged

Date: Wed, 23 May 2012 02:14:03 +0200

[Message part 1 (text/plain, inline)]

On Mon, May 21, 2012 at 07:14:08PM +0200, Javier Fernández-Sanguino Peña wrote:
> - I have not configured wicd at all, it was just pulled in as a dependency because 
>   GNOME's NetworkManager depends on it

A mistake here: wicd was pulled in because I installed the xfce-desktop
task, not because of Network Manager.

Still, I've always managed my interfaces using /etc/network/interfaces and
have *never* configured them using wicd.

> As I cannot disable the /usr/lib/pm-utils/sleep.d/55wicd script I've introduced another
> script in /etc/pm/sleep.d/00_restart_network that stops dhclient and
(...)

Please take note that it took me quite a lot of debugging of the pm-suspend
scripts until I found out that the reason why my interfaces were reconfigured
was because of wicd. 

Once the culprit has been found, a much simpler way to prevent this bug would
be using apt-get or dpkg, I could remove wicd since it is only Recommended:
by xfce-desktop.  For me it probably an option, but a regular user that
steps into this bug will find that this will make more "friendly" package management
frontends, such as aptitude, to *always* try to remove the xfce-desktop task
(unless configured to ignore Recommends).


Regards

Javier

[signature.asc (application/pgp-signature, inline)]

Message #47 received at 557156@bugs.debian.org (full text, mbox, reply):

From: Vincent Lefevre <vincent@vinc17.net>

To: Debian Bug Tracking System <557156@bugs.debian.org>

Subject: Re: Bug#557156: wicd deconfigures the wired (eth0) interface at suspend or cable unplugged

Date: Wed, 23 May 2012 02:30:27 +0200

On 2012-05-23 02:14:03 +0200, Javier Fernández-Sanguino Peña wrote:
> Once the culprit has been found, a much simpler way to prevent this bug would
> be using apt-get or dpkg, I could remove wicd since it is only Recommended:
> by xfce-desktop.

I think that by default, the wicd daemon shouldn't modify anything at
all, as it can be installed via a dependency. Fixing this bug would
go in that way, but one may wonder whether there are other default
operations that would have an influence on the network connection...

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Message #52 received at 557156@bugs.debian.org (full text, mbox, reply):

From: Martin Renold <martinxyz@gmx.ch>

To: Debian Bug Tracking System <557156@bugs.debian.org>

Subject: Re: wicd deconfigures the wired (eth0) interface at suspend or cable unplugged

Date: Sun, 30 Sep 2012 19:46:38 +0200

[Message part 1 (text/plain, inline)]

I also ran into this one.

On Wed, May 23, 2012 at 02:14:03AM +0200, Javier Fernández-Sanguino Peña wrote:
> 
> A mistake here: wicd was pulled in because I installed the xfce-desktop
> task, not because of Network Manager.

I think that's how I installed wicd, too. I have never configured wicd and
don't use it (my PC doesn't have wireless connections at all).

> Still, I've always managed my interfaces using /etc/network/interfaces and
> have *never* configured them using wicd.

Similar story: I have two wired interfaces: eth0 for my internet provider
and eth1 with a static IP, configured via /etc/network/interfaces.  I run a
DHCP server on eth1 where I connect my laptop for internet access.

What happened:

Whenever I disconnected my laptop, wicd did run dhclient on eth1. Probably
as a result, the static IP on eth1 was un-configured.  Dhclient did exit
again, realizing that the interface was down.

Sometimes the local dhcp server even decided to answer the local dhcp
client's request, giving itself a new IP from its own pool, and a new
default route to the internet which did not work.  I had to kill the extra
dhcp client started by wicd to fix this situation (not realizing how it
happened, of course).

> Please take note that it took me quite a lot of debugging of the pm-suspend
> scripts until I found out that the reason why my interfaces were reconfigured
> was because of wicd. 

Indeed, it took me quite some time to figure this out. After blaming several
other components (like NetworkManager), I finally traced it to wicd when I replaced
/sbin/dhclient with a script that prints the PID of the parent process. 

Solved now with 'apt-get remove wicd-daemon'.

-- 
Martin Renold

[signature.asc (application/pgp-signature, inline)]

Message #71 received at 557156@bugs.debian.org (full text, mbox, reply):

From: Vincent Lefevre <vincent@vinc17.net>

To: 557156@bugs.debian.org

Subject: Re: wicd deconfigures the wired (eth0) interface at suspend or cable unplugged

Date: Wed, 11 May 2016 23:17:07 +0200

[Message part 1 (text/plain, inline)]

Control: retitle -1 wired_connect_mode behavior doesn't match the wicd-manager-settings.conf(5) man page
Control: tags -1 patch

On 2009-11-19 23:41:10 +0100, Vincent Lefevre wrote:
> Note: in manager-settings.conf, I have "wired_connect_mode = 1",
> in order not to connect automatically. [...]

I wanted to see where the problem came from. In the
wicd-manager-settings.conf(5) man page:

       wired_connect_mode = <0|1>
              0 = connect to wired interface automatically
              1 = do not connect to wired interface automatically

which corresponds to what I expected, but in
/usr/share/wicd/daemon/wicd-daemon.py, one has:

    def SetWiredAutoConnectMethod(self, method):
        """ Sets which method to use to autoconnect to wired networks. """
        # 1 = default profile
        # 2 = show list
        # 3 = last used profile
        self.config.set("Settings", "wired_connect_mode", int(method),
                        write=True)
        self.wired_connect_mode = int(method)
        self.wired_bus.connect_mode = int(method)

This doesn't seem to be the same range of values!
This is confirmed here:

    def GetWiredAutoConnectMethod(self):
        """ Returns the wired autoconnect method. """
        return int(self.wired_connect_mode)
[...]
    def _wired_autoconnect(self, fresh=True):
        """ Attempts to autoconnect to a wired network. """
        wiredb = self.wired_bus
        if self.GetWiredAutoConnectMethod() == 3 and \
           not self.GetNeedWiredProfileChooser():
            # attempt to smartly connect to a wired network
            # by using various wireless networks detected
            # and by using plugged in USB devices
            print self.LastScan
        if self.GetWiredAutoConnectMethod() == 2 and \
           not self.GetNeedWiredProfileChooser():
            self.LaunchChooser()
            return True

        # Default Profile.
        elif self.GetWiredAutoConnectMethod() == 1:
            network = wiredb.GetDefaultWiredNetwork()
            if not network:
                print "Couldn't find a default wired connection," + \
                      " wired autoconnect failed."
                self.wireless_bus._wireless_autoconnect(fresh)
                return

        # Last-Used.
        else:
            network = wiredb.GetLastUsedWiredNetwork()
            if not network:
                print "no previous wired profile available, wired " + \
                      "autoconnect failed."
                self.wireless_bus._wireless_autoconnect(fresh)
                return

Actually wired_connect_mode corresponds to the 3 radio buttons of
"Wired automatic connection" in the preferences.

So, I suppose that the real problem is wrong documentation, and the
real solution to ignore the wired interface is to set

  wired_interface = None

i.e. make sure that the "Wired interface" box in the preferences is
blank.

Assuming that this is a documentation bug, I've attached a patch.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

[wicd-man.patch (text/plain, attachment)]

Message #84 received at 557156-close@bugs.debian.org (full text, mbox, reply):

From: Axel Beckert <abe@debian.org>

To: 557156-close@bugs.debian.org

Subject: Bug#557156: fixed in wicd 1.7.4+tb2-3

Date: Sun, 22 Jan 2017 17:19:54 +0000

Source: wicd
Source-Version: 1.7.4+tb2-3

We believe that the bug you reported is fixed in the latest version of
wicd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 557156@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Axel Beckert <abe@debian.org> (supplier of updated wicd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sun, 22 Jan 2017 17:16:07 +0100
Source: wicd
Binary: wicd wicd-daemon wicd-gtk wicd-curses wicd-cli python-wicd
Architecture: source all
Version: 1.7.4+tb2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian WICD Packaging Team <pkg-wicd-maint@lists.alioth.debian.org>
Changed-By: Axel Beckert <abe@debian.org>
Description:
 python-wicd - wired and wireless network manager - Python module
 wicd       - wired and wireless network manager - metapackage
 wicd-cli   - wired and wireless network manager - scriptable console client
 wicd-curses - wired and wireless network manager - Curses client
 wicd-daemon - wired and wireless network manager - daemon
 wicd-gtk   - wired and wireless network manager - GTK+ client
Closes: 557156 758737 759785 773809 783272 801253 831805
Changes:
 wicd (1.7.4+tb2-3) unstable; urgency=medium
 .
   [ Axel Beckert ]
   * Now maintained by the Debian WICD Packaging Team. (Closes: #801253)
     + Change Vcs-* URLs to …/pkg-wicd/wicd.git
     + Update Maintainers field and add Uploaders field.
   * Add NEWS.Debian entry for changes between Jessie and Stretch
     wrt. /etc/wicd/dhclient.conf.template and the possible need to update
     the file manually.
   * Update dependency on dhcpcd to dhcpcd5. (Closes: #783272) Thanks
     Konrad Zimmermann!
   * Fix typo MSCHAPv2 vs MSCHAPV2 for more pedantic wpa_supplicant 2.6.
     (LP: #1656061) Thanks to Piotr Karbowski for the upstream bug report
     and suggested fix!
   * Add WPA*-PEAP templates without domain. (Closes: #831805, #759785, LP:
     #1591489)
   * Add patch to fix documentation wrt. to which dhclient.conf wicd
     (re)generates. Also update mention path in an older NEWS.Debian item
     to avoid confusion. (Closes: #773809)
 .
   [ Giáp Trần ]
   * Remove $DAEMON_OPTIONS from reload function.
 .
   [ John C. Peterson ]
   * wicd-gtk: Add patch to initialize state of Wifi On/Off button
     properly. (Closes: #758737, LP: #1232521)
 .
   [ Vincent Lefevre ]
   * Add patch to fix wicd-manager-settings.conf(5) man page
     wrt. wired_connect_mode. (Closes: #557156)
Checksums-Sha1:
 fd13c70021c1b3d1b796256726c8c3595b4e939c 2261 wicd_1.7.4+tb2-3.dsc
 dbc378f12708ff878c96991dd950649da9c60ef9 26968 wicd_1.7.4+tb2-3.debian.tar.xz
 7efac454ccc173f98d1f34ef46e9e9486edc1990 54852 python-wicd_1.7.4+tb2-3_all.deb
 ec0c208022eedbe367235061dab22a79847bbf95 27508 wicd-cli_1.7.4+tb2-3_all.deb
 5c540780a719a0959dd07cc5546f17d3ca89b33b 52004 wicd-curses_1.7.4+tb2-3_all.deb
 e553ea4a98d3f7f411b58419bc3b8d97e835992f 162020 wicd-daemon_1.7.4+tb2-3_all.deb
 d65aee6e7dec44b6a3b5a28af61b22855468f45e 155002 wicd-gtk_1.7.4+tb2-3_all.deb
 ce9e9e08dacb11be2e9960c0e5e060971aaa7878 24168 wicd_1.7.4+tb2-3_all.deb
 9899ba188644f93dbcf2da1eed8de53478167bf6 6597 wicd_1.7.4+tb2-3_amd64.buildinfo
Checksums-Sha256:
 8ec30453dae952764e189c9883f57192b4d9a972b6c001a23f5f2ee1ddbee601 2261 wicd_1.7.4+tb2-3.dsc
 f8bf1d2378085e2138b02dc9b01129e73939193aff1cdd5bdd964b845e4b6e16 26968 wicd_1.7.4+tb2-3.debian.tar.xz
 11fc0ac2e50acd75c543f304227ec795e5bbdbfffcc83ab7662db13d1d8a267f 54852 python-wicd_1.7.4+tb2-3_all.deb
 1d09d6815ff4b77d7b9b5e08dcb499910439a012b5bc485d4ca8956d8e7b8828 27508 wicd-cli_1.7.4+tb2-3_all.deb
 a4a42e6255ff9b75f8ae24247e9dfd3faf11a711a0d6a9690dbdbb2e5dfecf60 52004 wicd-curses_1.7.4+tb2-3_all.deb
 f3a0cd44f24f1c98e331d464387fd40fea73022e873f79d4f5cb47a1f7b3993e 162020 wicd-daemon_1.7.4+tb2-3_all.deb
 e8a19dbe5832043e5746e8cab7a140066db623fa36803e0a66c6898e1f13eeda 155002 wicd-gtk_1.7.4+tb2-3_all.deb
 a613489e17806b0c4b6dd293b01a4c248f08360989045c2e781440ccb3274490 24168 wicd_1.7.4+tb2-3_all.deb
 c614d2390b6d64b4994dd19bebd36673aef172bde007940420b6cbc0c67ba161 6597 wicd_1.7.4+tb2-3_amd64.buildinfo
Files:
 7d342806758f6d6f805c2842feba8039 2261 net optional wicd_1.7.4+tb2-3.dsc
 3566f8094cd7cec481456cb8207f163b 26968 net optional wicd_1.7.4+tb2-3.debian.tar.xz
 0286ecdee68c9c2597c4f8fe419d61d1 54852 python optional python-wicd_1.7.4+tb2-3_all.deb
 a7a8e1243557fdf32eb7dc0f6743aee1 27508 net optional wicd-cli_1.7.4+tb2-3_all.deb
 03d579930caa4b88adb9379a71b526bc 52004 net optional wicd-curses_1.7.4+tb2-3_all.deb
 430140f30d2d19a73cac54a3796d261d 162020 net optional wicd-daemon_1.7.4+tb2-3_all.deb
 a94253aefad2f66561755b87e5f11bcb 155002 net optional wicd-gtk_1.7.4+tb2-3_all.deb
 0ecc288a414032f9f8a10e7fd859dbf7 24168 net optional wicd_1.7.4+tb2-3_all.deb
 1b8c59b3a280c9d9813a22d3b14fff7b 6597 net optional wicd_1.7.4+tb2-3_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEERoyJeTtCmBnp12Ema+Zjx1o1yXUFAliE2xQACgkQa+Zjx1o1
yXVflRAAlAYTKSO4v171V7+UifCX/uhBe+lETQFHv1PpXFwGP8/AE01d5lOnCqmo
jaI4QFKIikCb9cvlQinyeXWlvcw6ZOOet9UvaDg/oRBoNZIdvwZb8Xcet4U6Fy/r
MTP0nEOPxWQlWLJg3cm0oZLImdKv5xAN0cUZcmV/SJMOL2X31tjl45JKiRhuwQoa
YgaU6WJjavfB5pHADshWuVoNnFd7D9ZyuZ7AghFBBGWthMsb/eBeom42kRkG8RbN
g4dpRP/kkA/usWnHdDA637eiAhCaG65pA5rCfvje169e80LGd3RFIxHX29baVbnv
r87RvM7Jzut59uoG0GCtjv780UucnI975djV7kgFBMUqtJAGWqHhmRkJtLAk13Pf
cE6c+Yl5zw0GcuDYSxKrRRSLrSefDjY9aVgf75xrf66/eTDn731214cPgwwXf3ow
s/GOgUcztX8oTO71f/n1XeQPVicRw1jSB5d7EEHfDq3q7ZcsuO/Dz9iW8PiDnfp9
sx7UOuPPiiEDzAytNR74je74Usu3fNIC5RolgV98Cdbra3VASaNiMpBuHGrcCjWN
CnzrM+HMI4fzmyyOBNw6vNHRRyBuQYERKYetdDO9HW3jeC5jJImmtNqYRv7CW5N7
rPtU5IQLLiUadGGCBMJQCDYhhuxkmWHj5yB0xH3btRkd9IeARG8=
=iwNg
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.