Received: by 10.68.227.166 with SMTP id sb6mr16797209pbc.4.1332226352354;
        Mon, 19 Mar 2012 23:52:32 -0700 (PDT)
X-BeenThere: chromium-b...@chromium.org
Received: by 10.68.216.164 with SMTP id or4ls716181pbc.2.gmail; Mon, 19 Mar
 2012 23:52:30 -0700 (PDT)
Received: by 10.68.228.69 with SMTP id sg5mr47294464pbc.91.1332226350798;
        Mon, 19 Mar 2012 23:52:30 -0700 (PDT)
Received: by 10.68.228.69 with SMTP id sg5mr47294462pbc.91.1332226350787;
        Mon, 19 Mar 2012 23:52:30 -0700 (PDT)
Return-Path: <3LiloTwgODaEDISPNJVNHPPHMFDPEF.DPNDISPNJVN-CVHTDISPNJVN....@codesite.bounces.google.com>
Received: from mail-pb0-f75.google.com (mail-pb0-f75.google.com [209.85.160.75])
        by mx.google.com with ESMTPS id d3si826328pbh.237.2012.03.19.23.52.30
        (version=TLSv1/SSLv3 cipher=OTHER);
        Mon, 19 Mar 2012 23:52:30 -0700 (PDT)
Received-SPF: pass (google.com: domain of 3LiloTwgODaEDISPNJVNHPPHMFDPEF.DPNDISPNJVN-CVHTDISPNJVN....@codesite.bounces.google.com designates 209.85.160.75 as permitted sender) client-ip=209.85.160.75;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of 3LiloTwgODaEDISPNJVNHPPHMFDPEF.DPNDISPNJVN-CVHTDISPNJVN....@codesite.bounces.google.com designates 209.85.160.75 as permitted sender) smtp.mail=3LiloTwgODaEDISPNJVNHPPHMFDPEF.DPNDISPNJVN-CVHTDISPNJVN....@codesite.bounces.google.com
Received: by pbbrq13 with SMTP id rq13so58220pbb.0
        for <chromium-b...@chromium.org>; Mon, 19 Mar 2012 23:52:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.74.201 with SMTP id w9mr16796309pbv.0.1332226350636; Mon,
 19 Mar 2012 23:52:30 -0700 (PDT)
Reply-To: codesite-nore...@google.com
X-Generated-By: Google Code
X-GoogleCode-Project: chromium
X-GoogleCode-Issue-Id: 117973
References: <0-1824057202445553401-1435130818340389395-chromium=googlecode.com@googlecode.com>
In-Reply-To: <0-1824057202445553401-1435130818340389395-chromium=googlecode.com@googlecode.com>
Message-ID: <1-1824057202445553401-1435130818340389395-chromium=googlecode.com@googlecode.com>
Date: Tue, 20 Mar 2012 06:52:30 +0000
Subject: Re: Issue 117973 in chromium: Chrome does not detect internet
 connection that established without NetworkManager
From: chrom...@googlecode.com
To: chromium-b...@chromium.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes


Comment #1 on issue 117973 by felf...@gmail.com: Chrome does not detect  
internet connection that established without NetworkManager
http://code.google.com/p/chromium/issues/detail?id=117973

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.