Your message dated Sun, 16 Oct 2011 10:58:45 +0200
with message-id <[email protected]>
and subject line Re: [Pkg-utopia-maintainers] Bug#645483: network-manager:
doesn't bring up networking during boot
has caused the Debian Bug report #645483,
regarding network-manager: doesn't bring up networking during boot
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
645483: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645483
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: network-manager
Version: 0.9.0-2
Severity: important
NetworkManager was just installed as a Gnome dependency and it didn't
correctly migrate settings from /etc/network/interfaces. The file before
the package was installed:
auto lo eth0
iface lo inet loopback
iface eth0 inet dhcp
And after:
auto lo eth0
iface lo inet loopback
#NetworkManager#iface eth0 inet dhcp
The problem is that now networking is not available during booting which
is required for NFS-mounted home directories and LDAP user accounts.
Logging in as root on the console, removing the #NetworkManager# comment
and rebooting seems to fix things.
Is this the correct approach (I've seen NetworkManager tell applications
that they should be operating in offline mode in the past)? Is there a
way to prevent NetworkManager from doing this before it's installed (I'd
hate to go round all systems in our network to manually fix each and
every one)?
Thanks.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (x86_64)
Kernel: Linux 3.0.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages network-manager depends on:
ii adduser 3.113
ii dbus 1.4.16-1
ii isc-dhcp-client 4.2.2-1
ii libc6 2.13-21
ii libdbus-1-3 1.4.16-1
ii libdbus-glib-1-2 0.98-1
ii libgcrypt11 1.5.0-3
ii libglib2.0-0 2.28.6-4
ii libgnutls26 2.12.11-1
ii libgudev-1.0-0 172-1
ii libnl1 1.1-7
ii libnm-glib4 0.9.0-2
ii libnm-util2 0.9.0-2
ii libpolkit-gobject-1-0 0.102-1
ii libuuid1 2.19.1-5
ii lsb-base 3.2-28
ii udev 172-1
ii wpasupplicant 0.7.3-5
Versions of packages network-manager recommends:
ii dnsmasq-base 2.58-3
ii iptables 1.4.12-1
ii modemmanager 0.5-1
ii policykit-1 0.102-1
ii ppp 2.4.5-5
Versions of packages network-manager suggests:
pn avahi-autoipd <none>
--
-- arthur - [email protected] - http://people.debian.org/~adejong --
signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
On Sun, 2011-10-16 at 10:11 +0200, Michael Biebl wrote:
> Maybe your bug title is just misleading: Was the network not brought up at all
> or simply too late?
It didn't bring up networking at all but I've found it was the result of
some left-overs from a previous run-in with NetworkManager that I had. I
had put exit 0 in /etc/default/NetworkManager. Everything seems to be
working now.
Thanks for your quick response and sorry for the noise.
--
-- arthur - [email protected] - http://people.debian.org/~adejong --
signature.asc
Description: This is a digitally signed message part
--- End Message ---
