After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 412018 - must report static connection status
must report static connection status
Status: RESOLVED NOTABUG
Product: NetworkManager
Classification: Platform
Component: general
0.6.6
Other Linux
: Normal major
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2007-02-25 20:36 UTC by Jean-François Fortin Tam
Modified: 2007-02-26 12:32 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jean-François Fortin Tam 2007-02-25 20:36:46 UTC 
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 ;)
Comment 1 Dan Williams 2007-02-26 00:47:41 UTC 
This is actually expected behavior.  NM is not supposed to respect the setup of distro-specific tools.  On Ubuntu specifically, they have patched NM so that NM ignores already configured devices, which you have done with g-s-t.  Therefore, this is an Ubuntu bug, not an NM bug.
Comment 2 Jean-François Fortin Tam 2007-02-26 00:54:06 UTC 
You mean that the upstream behavior is to ignore completely /etc/network/interfaces (or whatever holds static configuration)? I did not know ubuntu did such scary patches :)
Comment 3 Dan Williams 2007-02-26 12:32:29 UTC 
NM actually has some support for static IP settings already, but the distro specific backend has to support it.  Fedora, SUSE, and Debian support it.  But Ubuntu decided to make NM ignore _any_ interface that you have already configured in /etc/network/interfaces.  Therefore, to NM that interface doesn't exist, and you'll get the behavior your see.