On Wednesday, February 27, 2013 07:39:44, Michael Biebl wrote: > On 27.02.2013 00:50, Chris Knadle wrote: > > When this was brought up in the bug report, the response was > > "network-manager can be installed, then disabled", but how to do that > > wasn't documented anywhere in the network-manager package. Instead the > > next suggestion was documenting this issue in the Wheey errata , but > > I don't see network- manager or wicd mentioned there, nor mentioned in > > the Installation Guide  for Wheezy. > > > > Suggestions? > > I will try to add a section to README.Debian which should be re-usable > for the release notes / errata. It's been a couple of weeks, so I did some minimal testing and wrote up some initial text for this purpose based on the behavior I observed. -- Chris -- Chris Knadle Chris.Knadle@coredump.us
conflicts with other networking manager daemons ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Gnome upstream chose to couple NetworkManager tightly with the Gnome Shell in order to provide connectivity awareness for both the Shell and Gnome3 applications. For this reason the Gnome3 maintainers in Debian decided to follow upstream and upgrade the Recommends on the network-manager stack to a Depends. It is known that a small number of Squeeze installations have Gnome installed but not NetworkManager, and this Dependency will cause NetowrkManager to be installed upon a distribution upgrade to Wheezy. At present, NetworkManager can detect if an interface is managed by ifupdown to avoid conflicts with it, but does not detect other networking manager programs such as wicd-daemon. Problems and unexpected behavior can ensue if two network manager daemons are managing the same interface when attempting to make a networking connection. This issue was discussed by the Debian Technical Committee in #681834 and #688772. If wicd-daemon and NetworkManager are both running, a wicd client will fail to make a connection with the counterintuitive message: "Connection Failed: bad password" Trying a NetworkManager client may sometimes result in the message (even when NetworkManager is running): "NetworkManager is not running. Please start it." Or a NetworkManager client may work as expected. Or some other unexpected behavior may occur. If continuing to use another networking manager is desired, the NetworkManager daemon may remain installed but be permanently disabled (which is persistant through upgrades) with: 'update-rc.d network-manager disable' You will also need to recreate /etc/resolv.conf, as the contents of this file are replaced when the network-manager package is installed.
Description: This is a digitally signed message part.