I experience the same issue.
Some additional info:
- I don't have NetworkManager installed at all.
- My proxy is configured via standard env-variables.
- If started on the commandline, it spits out the following on stderr:
[4251:4259:2272690513:ERROR:object_proxy.cc(239)] Failed to call method:
org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.NetworkManager was not provided by any .service files
- If manually entering any URL, chrome apparently resolves *everything* to
127.0.0.1.
- DNS works perfectly with *everything* else.
So: PLEASE don't rely on NetworkManager - I now it's kind of cute - but not
for us nerds with multi-homed machines or otherwise fancy setups. If It
can't connect to the DBUS service, assume *online* state, or better make
the whole beast configurable so that we can disable it.
Comment #3 on issue 117973 by mme...@chromium.org: Chrome does not detect
internet connection that established without NetworkManager
http://code.google.com/p/chromium/issues/detail?id=117973
Not at all familiar with NetworkChangeNotifier on Linux, but looks like we
are indeed using NetworkManager if it's available:
// This implementation of NetworkChangeNotifier's offline state detection
// depends on D-Bus and NetworkManager, and is known to work on at least
// GNOME version 2.30. If D-Bus or NetworkManager are unavailable, this
// implementation will always behave as if it is online.
Comment was added by adamk.