[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#613053: marked as done (Network-manager: device not managed)

Your message dated Fri, 22 Jul 2011 17:36:24 +0200
with message-id <CAP9ODKqTWGhqGzcXJ6skErmH_CQrbhqOmKmKG5w7fcEe083QMA@mail.gmail.com>
and subject line Not a bug
has caused the Debian Bug report #613053,
regarding Network-manager: device not managed
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 owner@bugs.debian.org

613053: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613053
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: network-manager
Version: 0.8.1-6
Severity: important

With the live-cd the network interfaces were managed correctly, but after the
install network-manager is not working correctly on 3 different machines. (so
this is a bug)

The Network-manager dose not see any connection, but the NIC is working fine.
This can be bad if one wishes to use network-manager to connect to vpn for

On the one machine there are two Intel NICs, after starting the second one from
the BIOS it gets managed as eth1 by Network-Manager eth0 is till up (it is a
PCI NIC) and still connected but Network-Manager dose not manage it.

-- System Information:
Debian Release: 6.0
  APT prefers squeeze-updates
  APT policy: (500, 'squeeze-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages network-manager depends on:
ii  adduser                 3.112+nmu2       add and remove users and groups
ii  dbus                    1.2.24-4         simple interprocess messaging syst
ii  isc-dhcp-client         4.1.1-P1-15      ISC DHCP client
ii  libc6                   2.11.2-10        Embedded GNU C Library: Shared lib
ii  libdbus-1-3             1.2.24-4         simple interprocess messaging syst
ii  libdbus-glib-1-2        0.88-2.1         simple interprocess messaging syst
ii  libgcrypt11             1.4.5-2          LGPL Crypto library - runtime libr
ii  libglib2.0-0            2.24.2-1         The GLib library of C routines
ii  libgnutls26             2.8.6-1          the GNU TLS library - runtime libr
ii  libgudev-1.0-0          164-3            GObject-based wrapper library for 
ii  libnl1                  1.1-6            library for dealing with netlink s
ii  libnm-glib2             0.8.1-6          network management framework (GLib
ii  libnm-util1             0.8.1-6          network management framework (shar
ii  libpolkit-gobject-1-0   0.96-4           PolicyKit Authorization API
ii  libuuid1                2.17.2-9         Universally Unique ID library
ii  lsb-base                3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip
ii  udev                    164-3            /dev/ and hotplug management daemo
ii  wpasupplicant           0.6.10-2.1       client support for WPA and WPA2 (I

Versions of packages network-manager recommends:
ii  dnsmas 2.55-2                            A small caching DNS proxy and DHCP
ii  iptabl 1.4.8-3                           administration tools for packet fi
ii  modemm 0.4+git.20100624t180933.6e79d15-2 D-Bus service for managing modems
ii  policy 0.96-4                            framework for managing administrat
ii  ppp    2.4.5-4                           Point-to-Point Protocol (PPP) - da

Versions of packages network-manager suggests:
ii  avahi-autoipd                 0.6.27-2   Avahi IPv4LL network address confi

-- Configuration Files:
/etc/NetworkManager/NetworkManager.conf changed:

-- no debconf information

--- End Message ---
--- Begin Message ---

The behavior is right and it does the most sensible thing by default.
Live Installer doesn't change any network setting and basically the
system is respecting the network setup the user has put into

In case user wants to have it fully managed after installation it is
just a matter of skipping network setup so it will end with a minimal
interfaces file.

Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

--- End Message ---

Reply to: