From owner-freebsd-chromium@FreeBSD.ORG Sat Mar 2 13:43:08 2013 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 703F9449 for ; Sat, 2 Mar 2013 13:43:08 +0000 (UTC) (envelope-from fbsd@opal.com) Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) by mx1.freebsd.org (Postfix) with ESMTP id 16A94B07 for ; Sat, 2 Mar 2013 13:43:07 +0000 (UTC) Received: from pool-141-154-241-44.bos.east.verizon.net ([141.154.241.44] helo=homobox.opal.com) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1UBmiL-0007aT-Jd; Sat, 02 Mar 2013 13:43:01 +0000 Received: from shibato (shibato.opal.com [IPv6:2001:470:8cb8:4:221:63ff:fe5a:c9a7]) (authenticated bits=0) by homobox.opal.com (8.14.4/8.14.4) with ESMTP id r22Dguim029719 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sat, 2 Mar 2013 08:42:57 -0500 (EST) (envelope-from fbsd@opal.com) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 141.154.241.44 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1/Yutz8bXzEOeuSr7q2d5A/ Date: Sat, 2 Mar 2013 08:42:56 -0500 From: "J.R. Oldroyd" To: "Lawrence K. Chen, P.Eng." Subject: Re: chromium v25.0.1364.97 problems Message-ID: <20130302084256.33869737@shibato> In-Reply-To: <985459515.20213713.1361920260108.JavaMail.root@k-state.edu> References: <135007687.20087195.1361905506071.JavaMail.root@k-state.edu> <985459515.20213713.1361920260108.JavaMail.root@k-state.edu> X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.6; amd64-portbld-freebsd9.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (homobox.opal.com [IPv6:2001:470:8cb8:4::1]); Sat, 02 Mar 2013 08:42:59 -0500 (EST) X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, RP_MATCHES_RCVD shortcircuit=no autolearn=ham version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on homobox.opal.com Cc: chromium@freebsd.org X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Mar 2013 13:43:08 -0000 On Tue, 26 Feb 2013 18:11:00 -0500 (EST) "Lawrence K. Chen, P.Eng." wrote: > > Also Currently seems to no longer be able to figure out my location anymore. > > Anybody else seeing this? > Yes. I took a look at the wifi geolocation code, and it is still there and looks like it's still compiling in. So this must be another example of some other C++ class masking out the FreeBSD wifi provider class. You can run with "chrome -v 1" from the console and go to any geoloc web page. If it's working, you'll see messages showing the wifi access points it is using to determine your location. But it is not showing those messages, which means that the FreeBSD wifi class is not being executed. Someone with more C++ knowledge please look at this. The code is in content/browser/geolocation/wifi_data_provider_freebsd.cc for the FreeBSD-specific stuff, as well as wifi_data_provider_common, network_location_provider, empty_device_data_provider, etc in the same directory. -jr