On Wed, 21 Nov 2012 16:58:31 +0000, David Edmondson wrote: > On Wed, Nov 21 2012, David Paleino wrote: > > Besides that, I don't consider this to be a bug. Rather, I consider it a > > feature -- being able to replace/restart/... wicd while still keeping a > > connection alive. > > Whilst not deeply passionate about it, I disagree. Stopping the daemon > should revert the system to the state it was in before starting, else > the originally described scenario is difficult to avoid. How does an > upgrade of the wicd daemon avoid this problem?
The described scenario is that NM *thinks* there is no network, when there actually is. When WICD upgrades, it's able to detect that a network link is alive, so this problem doesn't exist at all. Last time (years ago) I installed wicd while using NM, it detected the connection status fine (yes, it wasn't able to properly manage it, because it was started by NM). Honestly, I don't know whether this is still the case. > And, if you don't believe that this is a bug, shouldn't it be closed as > such rather than simply downgraded in severity? Because _I_ don't consider it a bug, but I understand it's questionable. As I said, this bug isn't release-critical to me. I already prepared a commit, and I'm currently testing it -- this will certainly be in the next upstream release (1.7.3). Kindly, 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
Description: PGP signature
