Your message dated Wed, 14 Jan 2009 09:02:29 +0000
with message-id <[email protected]>
and subject line Bug#491826: fixed in network-manager 0.6.6-3
has caused the Debian Bug report #491826,
regarding better handling of situations where network-manager does not manage 
all interfaces
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.)


-- 
491826: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=491826
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: network-manager
Version: 0.6.6-2
Severity: normal

If Network Manager does not handle all interfaces currently it reports
offline for network status when none of the interfaces it manages is
online.

This is just plain incorrect. Currently Network Manager does not seem to
have a clue whether interfaces that are not managed by it are on- or
offline. So it shouldn't pretend to know whether the network in itself
is on- or offline in this case. If it doesn't know it should tell so and
let applications decide what to make of it.

Or it should - at users option maybe - make an educated guess. If a
default route and DNS servers are configured, Network Manager IMHO can
assume that the network is online. At least if the user tells it to use
that approximation.

This problem gets more and more serious, the more application rely
solely on Network Manager regarding network status information (which
IMHO is a bug in itself). I filed a bug report for Iceweasel 3.0.1
already:

http://bugs.debian.org/491822

There are several related bugs:

- http://bugs.debian.org/436181, http://bugs.debian.org/431427,
http://bugs.debian.org/415891, http://bugs.debian.org/408292: network
manager and static configurations

- http://bugs.debian.org/355478: Conflicts with other packages 
which manage the network

In the related Firefox 3 bug report Dan Williams proposes an
all-or-nothing scenario for network manager:

- https://bugzilla.mozilla.org/show_bug.cgi?id=424626#c6
- https://bugzilla.mozilla.org/show_bug.cgi?id=424626#c41

I dare to disagree on that at least as long as I can not be convinced
that Network Manager is the perfect tool for all my network needs.

I currently still prefer to use guessnet and ifplugd on eth0, partly
cause I did not yet setup a DHCP server on my ASUS WL-500g Premium
Debian based DSL router. But I like to use Network Manager with WLAN.
guessnet detects my routers IP and MAC address and then eth0 is
configured statically. Yes, once I setup dnsmasq this would no longer be
required.

But then there are people who use connections that are unsupported by
Network Manager like UMTS and special PPP configuration or what not.

I think if Network Manager finds that it does not manage all interfaces
it should at least report "unknown" as network status. Or the semantic
of that report should be "the interfaces *I* manage are offline" and it
would be up to the application to handle this.

Especially with Firefox 3 thats currently really annoying. I do not like
software patronizing me that way cause I like to decide how I setup my
network. I would like to use Network Manager but as long as using it
causes me more problems than it solves I may just leave it disabled
usually.

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing'), (400, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.25.10-tp42-toi-3.0-rc7 (PREEMPT)
Locale: lang=de...@euro, lc_ctype=de...@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash

Versions of packages network-manager depends on:
ii  adduser                       3.108      add and remove users and groups
ii  dbus                          1.2.1-2    simple interprocess messaging syst
ii  dhcdbd                        3.0-4      D-Bus interface to the ISC DHCP cl
ii  hal                           0.5.11-2   Hardware Abstraction Layer
ii  ifupdown                      0.6.8+nmu1 high level tools to configure netw
ii  iproute                       20080417-1 networking and traffic control too
ii  libc6                         2.7-10     GNU C Library: Shared libraries
ii  libdbus-1-3                   1.2.1-2    simple interprocess messaging syst
ii  libdbus-glib-1-2              0.76-1     simple interprocess messaging syst
ii  libgcrypt11                   1.4.1-1    LGPL Crypto library - runtime libr
ii  libglib2.0-0                  2.16.3-2   The GLib library of C routines
ii  libgpg-error0                 1.4-2      library for common error values an
ii  libhal1                       0.5.11-2   Hardware Abstraction Layer - share
ii  libiw29                       29-1       Wireless tools - library
ii  libnl1                        1.1-2      library for dealing with netlink s
ii  libnm-util0                   0.6.6-2    network management framework (shar
ii  lsb-base                      3.2-12     Linux Standard Base 3.2 init scrip
ii  wpasupplicant                 0.6.3-2    Client support for WPA and WPA2 (I

Versions of packages network-manager recommends:
ii  network-manager-kde           1:0.2.2-1  KDE systray applet for controlling

-- no debconf information



--- End Message ---
--- Begin Message ---
Source: network-manager
Source-Version: 0.6.6-3

We believe that the bug you reported is fixed in the latest version of
network-manager, which is due to be installed in the Debian FTP archive:

libnm-glib-dev_0.6.6-3_i386.deb
  to pool/main/n/network-manager/libnm-glib-dev_0.6.6-3_i386.deb
libnm-glib0_0.6.6-3_i386.deb
  to pool/main/n/network-manager/libnm-glib0_0.6.6-3_i386.deb
libnm-util-dev_0.6.6-3_i386.deb
  to pool/main/n/network-manager/libnm-util-dev_0.6.6-3_i386.deb
libnm-util0_0.6.6-3_i386.deb
  to pool/main/n/network-manager/libnm-util0_0.6.6-3_i386.deb
network-manager-dev_0.6.6-3_i386.deb
  to pool/main/n/network-manager/network-manager-dev_0.6.6-3_i386.deb
network-manager_0.6.6-3.diff.gz
  to pool/main/n/network-manager/network-manager_0.6.6-3.diff.gz
network-manager_0.6.6-3.dsc
  to pool/main/n/network-manager/network-manager_0.6.6-3.dsc
network-manager_0.6.6-3_i386.deb
  to pool/main/n/network-manager/network-manager_0.6.6-3_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Biebl <[email protected]> (supplier of updated network-manager package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Wed, 14 Jan 2009 09:29:03 +0100
Source: network-manager
Binary: network-manager network-manager-dev libnm-glib0 libnm-glib-dev 
libnm-util0 libnm-util-dev
Architecture: source i386
Version: 0.6.6-3
Distribution: unstable
Urgency: low
Maintainer: Utopia Maintenance Team 
<[email protected]>
Changed-By: Michael Biebl <[email protected]>
Description: 
 libnm-glib-dev - network management framework (GLib interface)
 libnm-glib0 - network management framework (GLib shared library)
 libnm-util-dev - network management framework (development files)
 libnm-util0 - network management framework (shared library)
 network-manager - network management framework daemon
 network-manager-dev - network management framework (development files)
Closes: 491826 500085 502371 509006 509829 511712
Changes: 
 network-manager (0.6.6-3) unstable; urgency=low
 .
   * debian/network-manager.network-manager-dispatcher.init
     - NetworkManagerDispatcher uses the D-Bus system bus. Update the LSB
       header accordingly to avoid breakages with insserv based systems.
       (Closes: #500085)
   * debian/patches/20-manual_means_always_online.patch
     - manual-means-online: If there are interfaces that are not managed by
       NetworkManager because they have custom configuration in
       /etc/network/interfaces, we assume to be online. This is obviously not
       always correct. But reporting offline state for unmanaged devices is
       causing major hassles as more and more apps rely on NM and go into
       offline mode otherwise, even if there is a connection (established via
       ifupdown). (Closes: #491826, #502371, #509006, #509829, #511712)
Checksums-Sha1: 
 42aabd551949a500555e67867cac6e6d4a2e116c 1709 network-manager_0.6.6-3.dsc
 db25682b3e6a4e8ad3758c52d41125a7bac645b6 23152 network-manager_0.6.6-3.diff.gz
 b0a813d7425863571704b0086539feb2c87271f9 370862 
network-manager_0.6.6-3_i386.deb
 082e13e4d620dff17440b9a3c39476a05c3ad2c1 124396 
network-manager-dev_0.6.6-3_i386.deb
 35fd41d0198ec533f8c6b164e203811f26c622ad 129938 libnm-glib0_0.6.6-3_i386.deb
 7ca751c6e60fd2b5a8a820a2879a54f055a0e0d2 129674 libnm-glib-dev_0.6.6-3_i386.deb
 f8c74d411909028d988a9c0e665f396ef5c54413 135550 libnm-util0_0.6.6-3_i386.deb
 21464eea8d128b26918c0f6d4f293c22de703f69 138732 libnm-util-dev_0.6.6-3_i386.deb
Checksums-Sha256: 
 11646d4334e909f5e7a4abcdb12550c74773ebd5b14bf14dd3e1bf283a4ac528 1709 
network-manager_0.6.6-3.dsc
 7f833100483997dffb8486c350dc5a7df5204d016b3631592c7d0cbc928a2164 23152 
network-manager_0.6.6-3.diff.gz
 d358f80629aff0a435b54afb009991d3317ba0d16d35c0d160b6cccf72bdc445 370862 
network-manager_0.6.6-3_i386.deb
 4c06a6f93d2b8cbbadbd6864353e42b6e2c66c06f0d475429dadc2ad13270e32 124396 
network-manager-dev_0.6.6-3_i386.deb
 c3d25a8a8dde0375b782921b13eeb2eec1a2345960e0d682cacc112e0810b5cf 129938 
libnm-glib0_0.6.6-3_i386.deb
 a478b956eea0dbf8f10243fa4326c48810024f1b2573e6d3cd6adc1a8e7801c9 129674 
libnm-glib-dev_0.6.6-3_i386.deb
 1ff09aa2fd4efce0422ae1333fa4d0dbc769609a0b2000e7d9089f57d8fc9447 135550 
libnm-util0_0.6.6-3_i386.deb
 d0529a7e6289085b71c13eb5eed4b7cd699feea30988ae3a353026e509bca055 138732 
libnm-util-dev_0.6.6-3_i386.deb
Files: 
 38f714ba7a4d7ffcbd574881e40fa550 1709 net optional network-manager_0.6.6-3.dsc
 3e174fff1f0e8fe0c457d8ba61e25ec0 23152 net optional 
network-manager_0.6.6-3.diff.gz
 766f1560f60b85ec7136f162adb24615 370862 net optional 
network-manager_0.6.6-3_i386.deb
 4955acf2db1fe0b3e0bcd506bcfba9c5 124396 devel optional 
network-manager-dev_0.6.6-3_i386.deb
 4f51f2f38f5e35458e9a438c72ba873a 129938 libs optional 
libnm-glib0_0.6.6-3_i386.deb
 a484dee046bb0a7471ea69d5e24eb9ed 129674 libdevel optional 
libnm-glib-dev_0.6.6-3_i386.deb
 2d74ec10272d731ebae005ff672823ab 135550 libs optional 
libnm-util0_0.6.6-3_i386.deb
 68f90720087dc15b8ec4f1f1deab3491 138732 libdevel optional 
libnm-util-dev_0.6.6-3_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkltpYUACgkQh7PER70FhVS9OACgyl2Q+NtugS/+FAoyskRO1+8U
uYwAn0vmrCmfhz1xtL+oiDYt6aB/wyij
=fVPM
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to