| 2007-02-26 01:28:47 |
Jeff Fortin Tam |
description |
Binary package hint: network-manager
taken from http://bugzilla.gnome.org/show_bug.cgi?id=412018 (rejected by upstream as they say it is an ubuntu patch)
I have a static IP set using gnome's network-admin tool, but network-manager is
installed (some metapackage depends on it).
All the applications that are networkmanager-aware (specto, epiphany,
xchat-gnome, etc) will incorrectly believe there is no network connection
available (because networkmanager is not managing the static connection) and
you will not be able to refresh watches, load webpages, join channels, etc.
Marking as major because it is a regression for those who have static IP setups
and will see their apps break when they dist-upgrade their ubuntu boxes ;)
Reply from upstream: "This is actually expected behavior. NM is not supposed to respect the setup of distro-specific tools." |
Binary package hint: network-manager
taken from http://bugzilla.gnome.org/show_bug.cgi?id=412018 (rejected by upstream as they say it is an ubuntu patch)
I have a static IP set using gnome's network-admin tool, but network-manager is installed (some metapackage depends on it).
All the applications that are networkmanager-aware (specto, epiphany, xchat-gnome, etc) will incorrectly believe there is no network connection available (because networkmanager is not managing the static connection) and you will not be able to refresh watches, load webpages, join channels, etc.
I would mark this bug as *major* because it is a regression for those who have static IP setups and will see their apps break when they dist-upgrade their ubuntu boxes. Their webpages will refuse loading, and they will have no idea why, as their network seems to "behave normally" (for all networkmanager-unaware applications).
Reply from upstream: "This is actually expected behavior. NM is not supposed to respect the setup of distro-specific tools." |
|
