On Wednesday, October 10, 2012 21:18:52, Don Armstrong wrote: > On Fri, 05 Oct 2012, Don Armstrong wrote: > > From what I understand, nm and wicd are not capable of > > co-existing.[1] Furthermore, nm does not always catch that other > > systems (such as ifupdown) are configuring the interfaces, and may > > lead to broken behavior on upgrade (such as #656584 and #688355, > > just glancing at it). > > Assuming that > > 1) we decide that failures of NM to detect basic ifupdown > configurations and avoid overriding them are bugs, possibly of RC > severity > > 2) given the gnome maintainer's desire to have NM installed by default > from the gnome metapackage > > allowing gnome to Depends: nm | wicd; would deal with the most > concerning form of breakage for me. > > Does this work for anyone else?
I think this would work assuming that wicd is a usable replacement for n-m within Gnome, which it might or might not be depending on the particular user's needs. I've been testing for a couple of days with wicd installed but n-m removed by installing a minimally modified gnome metapackge, so I'll report what I've found so far. wicd-gtk doesn't integrate into the top bar in a "Gnome" login, but it does (automatically) in a "Gnome Compatability" login. In a "Gnome" login, running 'wicd-gtk' manually via a terminal works, except that the icon that normally gives visual status of connectivity isn't shown anywhere. Under either login type, opening System Settings -> Network shows the message "The system network services are not compatible with this version." -- Chris -- Chris Knadle chris.kna...@coredump.us -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org