Hi Michael, I've tried it, and it fixes the hostname issue (nm does no change the hostname).
I had to set "managed=true" in /etc/NetworkManager/nm-system-settings.conf, nm-applet said "interface not managed", then the wired interface works perfectly with nm-applet, but the wireless interface is still in "not ready" status. If I put the wpa-conf stuff in /etc/network/interfaces and run "ifup eth1" the interface works as expected. Regards, Roberto Lumbreras On Thu, Jan 28, 2010 at 3:25 AM, Michael Biebl <[email protected]> wrote: > On 27.12.2009 19:17, Roberto Lumbreras wrote: > > Package: network-manager > > Version: 0.7.2-2 > > Severity: critical > > Justification: breaks unrelated software > > > > After installing network-manager in an updated testing system (but > without > > network-manager) it happened the following: > > > > -wireless network interface eth1 was taken down (it is "allow-hotplug" > > but it was set up manually), breaking several running applications that > > were using the network > > -hostname was set to `localhost' (not what it is in /etc/hostname), > > breaking all running X applications, as they could no longer access to > the > > Xserver. Why the hell a program should change the hostname of a running > > system??? > > -network was left down, and nm-applet says wireless device is not ready > > > > Hi Roberto, > > could you try the packages from [1] and see if they fix your problem. > See also the relevant upstream commit [2]. > > Cheers, > Michael > > [1] http://debs.michaelbiebl.de/network-manager/ > [2] > > http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=72f936db31f7b6e973d54b82410ce95fdaa6ceed > -- > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? > >
