From owner-freebsd-chromium@FreeBSD.ORG Mon Dec 3 11:06:22 2012 Return-Path: Delivered-To: chromium@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 667D0F2D for ; Mon, 3 Dec 2012 11:06:22 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 4B5BF8FC1A for ; Mon, 3 Dec 2012 11:06:22 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id qB3B6Ms8027077 for ; Mon, 3 Dec 2012 11:06:22 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qB3B6LkK027075 for chromium@FreeBSD.org; Mon, 3 Dec 2012 11:06:21 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 3 Dec 2012 11:06:21 GMT Message-Id: <201212031106.qB3B6LkK027075@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: chromium@FreeBSD.org Subject: Current problem reports assigned to 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: Mon, 03 Dec 2012 11:06:22 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/165637 chromium www/chromium: 17.0.963.56 fails to find some ns plugin o ports/165635 chromium www/chromium: 17.0.963.56: proxy isn't read by chrome f ports/165634 chromium www/chromium : 17.0.963.56 doesn't show physical print 3 problems total. From owner-freebsd-chromium@FreeBSD.ORG Mon Dec 3 11:06:41 2012 Return-Path: Delivered-To: freebsd-chromium@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E1285F98 for ; Mon, 3 Dec 2012 11:06:41 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id C1DE38FC1B for ; Mon, 3 Dec 2012 11:06:41 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id qB3B6fiJ027493 for ; Mon, 3 Dec 2012 11:06:41 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id qB3B6f74027491 for freebsd-chromium@FreeBSD.org; Mon, 3 Dec 2012 11:06:41 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 3 Dec 2012 11:06:41 GMT Message-Id: <201212031106.qB3B6f74027491@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-chromium@FreeBSD.org Subject: Current problem reports assigned to freebsd-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: Mon, 03 Dec 2012 11:06:41 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/173583 chromium www/chromium reproducibly crashes when trying do downl 1 problem total. From owner-freebsd-chromium@FreeBSD.ORG Tue Dec 4 01:31:42 2012 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 031F3D4F for ; Tue, 4 Dec 2012 01:31:42 +0000 (UTC) (envelope-from prvs=1685a61a7f=evendas@krazer.com.br) Received: from krazer.com.br (usaimport.com.br [74.208.147.131]) by mx1.freebsd.org (Postfix) with ESMTP id E28308FC1A for ; Tue, 4 Dec 2012 01:31:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=krazer.com.br; s=MDaemon; t=1354583456; x=1355188256; q=dns/txt; h=DomainKey-Signature: Received:From:To:Subject:Date:MIME-Version:Content-Type: Message-ID; bh=/AGF6JRzB/J7iTsWt8UkF/2jJ0/KNRujXWNnXTa6qHA=; b=Q 6KmoKvEz8LbmK8A2aNXcRPP6FuNFUpIPFdte/D+yy6raBdzGXXDDJmd91vM1lj1E KK/K0X0b94PwQALiyO59EnQZcE0iL4Xw0dhp61gpFc2qV41QdMayHi9vmN1PlWfK TospGkBYA7J9wraw1aI76xQZ6HkSXRLWhnTgQKWq90= DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=krazer.com.br; c=simple; q=dns; h=from:message-id; b=Fhq1cvGaWB1K8yLSE7GSykJiP4uoEzoaNk89oeZPS1WNpOtpDq9QxjNhRhe6 sLjnzXi1ixwjmt+wB22jfzErMqKQF285Ttm7IqGm5cbVMOCIzkWP8lFiz Xn+JVbH2i6d+9mYvfEjKPFBJTsmf06WPvDZ8ddtX8stjVwstKL2Uyw=; X-MDAV-Processed: allearth.com.br, Mon, 03 Dec 2012 23:10:56 -0200 Received: from krazer by allearth.com.br (MDaemon PRO v11.0.0) with ESMTP id md50003170642.msg for ; Mon, 03 Dec 2012 23:10:54 -0200 X-Spam-Processed: allearth.com.br, Mon, 03 Dec 2012 23:10:54 -0200 (not processed: message from trusted or authenticated source) X-Authenticated-Sender: evendas@krazer.com.br X-MDRemoteIP: 74.208.167.75 X-Return-Path: prvs=1685a61a7f=evendas@krazer.com.br X-Envelope-From: evendas@krazer.com.br X-MDaemon-Deliver-To: freebsd-chromium@freebsd.org From: "Vendas Krazer Technologies" To: Subject: =?utf-8?B?Tm92YSBDUEUgS3JhemVyIFNreSBTdGF0aW9uIDVHSHo=?= =?utf-8?B?IE4gLSBDUEUgQW50ZW5hIEludGVncmFkYSBkZSAxOGRCaQ==?= =?utf-8?B?IGUgQ29tIFNhw61kYSBwYXJhIEFudGVuYSBFeHRlcm5h?= Date: Mon, 03 Dec 2012 22:08:15 -0200 MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=45652905_3502_4801_0078_850943129657" Message-ID: X-Mailer: Clientes Krazer X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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: Tue, 04 Dec 2012 01:31:42 -0000 This is a multi-part message in MIME format. ------=45652905_3502_4801_0078_850943129657 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Lan=C3=A7amento CPE Krazer Sky Station 5GHz N Voc=C3=AA cliente pediu que a Krazer fizesse uma nova CPE num formato mais = estiloso, pequena, de menor tamanho e que tivesse novas funcionabilidade, m= ais especificamente acesso f=C3=A1cil ao bot=C3=A3o de reset, prote=C3=A7= =C3=A3o contra queima e a t=C3=A3o desejada SA=C3=8DDA PARA ANTENA EXTERNA!= !! R$ 179.90 Antena Integrada de 18dBi 60=C2=BA Duas Portas de Rede Lan e Wan PA Real de 630mW e LNA Ultra Ganho PoE Passivo com Prote=C3=A7=C3=A3o Dupla de 12 a 24V Fonte Chaveada 12V Full Range 110 a 220V Exclusiva Sa=C3=ADda para Antena Externa Homologa=C3=A7=C3=A3o Anatel 0269-11-5280 Instala=C3=A7=C3=A3o R=C3=A1pida e Simples. Software Amigavel e em Portugu=C3=AAs! Suporte a PPPoE Wisp Cliente! Controle de Banda! Excelente sinal de recep=C3=A7=C3=A3o! Longa Dist=C3=A2ncia! Fa=C3=A7a um teste em sua rede e compare com os concorrentes, muito mais si= nal que UBNT, muito mais dados, transmiss=C3=A3o de quase 90Mbps TCP/IP con= tinuamente! Lat=C3=AAncia de rede de 1 a 5 ms com carga completa! Contate-nos Val Campos // Carla Maria // Eder Roberto Email / MSN: vendas@allearth.com.br Vendas / SAC (19) 3256-5557 (19) 3245-0708 www.krazer.com.br Envio de Email n=C3=A3o autorizado =C3=A9 crime, n=C3=A3o seja o vil=C3=A3o= da hist=C3=B3ria! Email =C3=A9 protegido sobre sigilo fiscal e federal. Le= i Federal Brasil. ------=45652905_3502_4801_0078_850943129657-- From owner-freebsd-chromium@FreeBSD.ORG Tue Dec 4 13:42:54 2012 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BC4BA1F4 for ; Tue, 4 Dec 2012 13:42:54 +0000 (UTC) (envelope-from ottolebeda@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 4BB4D8FC15 for ; Tue, 4 Dec 2012 13:42:54 +0000 (UTC) Received: by mail-bk0-f54.google.com with SMTP id je9so1889372bkc.13 for ; Tue, 04 Dec 2012 05:42:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=; b=VypuOXEQKn6wAATg5kzY0RkZLV5x9SedLfefKGeRcnbHeH8w6EmNMX/2ZXy+LGmwx0 jc0W1EBOeWMFoWQF9HYZBz9xm4AFgdXo+rAZkx2W/jLFpTl8GhqgjYiqQcwI4f8mccG2 sWWYJyYF1ZUyfDNvuOIH92/XI/7g735Vbml4WZZN/zbiWGRESXX6ZJfYi2DaKTvA0xqB Vr6wmbrF/I5sbrEK24B8r9PQZfpsGUnrDjEVpDUNRphmGFYoi00v00erODKctCc6zB7D Ns0mLpavQxtzke1mnx5CMzUZRpC2kq1Glk28blzP+2OT1HJc1xbd/zzU2Du+BSuoN2lX AIiA== MIME-Version: 1.0 Received: by 10.204.5.141 with SMTP id 13mr3988353bkv.35.1354627232571; Tue, 04 Dec 2012 05:20:32 -0800 (PST) Received: by 10.204.34.212 with HTTP; Tue, 4 Dec 2012 05:20:32 -0800 (PST) Date: Tue, 4 Dec 2012 05:20:32 -0800 Message-ID: Subject: From: Otto LEBEDA To: freebsd-chromium@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 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: Tue, 04 Dec 2012 13:42:54 -0000 From owner-freebsd-chromium@FreeBSD.ORG Thu Dec 6 06:05:05 2012 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0C4E91A6D for ; Thu, 6 Dec 2012 06:05:05 +0000 (UTC) (envelope-from fbsd@opal.com) Received: from mho-02-ewr.mailhop.org (mho-04-ewr.mailhop.org [204.13.248.74]) by mx1.freebsd.org (Postfix) with ESMTP id AD7668FC08 for ; Thu, 6 Dec 2012 06:05:04 +0000 (UTC) Received: from pool-151-203-201-84.bos.east.verizon.net ([151.203.201.84] helo=homobox.opal.com) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1TgULE-0002FO-Mt for freebsd-chromium@freebsd.org; Thu, 06 Dec 2012 05:49:48 +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 qB65njrN048030 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Thu, 6 Dec 2012 00:49:46 -0500 (EST) (envelope-from fbsd@opal.com) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 151.203.201.84 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX18qNj9LKsWVEKtenBA5jeRU Date: Thu, 6 Dec 2012 00:49:45 -0500 From: "J.R. Oldroyd" To: freebsd-chromium@freebsd.org Subject: WIP: Wi-fi Geolocation Provider Message-ID: <20121206004945.7ec2a1f1@shibato> X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.6; amd64-portbld-freebsd8.2) 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]); Thu, 06 Dec 2012 00:49:46 -0500 (EST) X-Spam-Status: No, score=-2.6 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 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: Thu, 06 Dec 2012 06:05:05 -0000 It seems that Google's Geolocation Service lookups done using an IPv6 address results in a location that is far, far, far away from where you really are, and even lookups using IPv4 addresses are often several km off. Since I am increasingly running into web pages that want to "help me better" based on my location, it seems a more accurate lookup is needed. So... I have knocked together a wifi_data_provider_freebsd.cc that gets your list of wi-fi APs so that the geolocation lookup can be done using the wi-fi AP information. The wi-fi AP code was tested and works as a stand-alone program. Now, I am not really a C++ guy and I am far from up-to-speed on chromium's object methods and how to hook this in so the browser actually finds and uses it. I could use some help with that. I've put what I have so far, and some additional details, here: http://opal.com/jr/freebsd/ports/www/chromium/files/ Anyone who cares to help integrate this into chromium, feel free to grab the files from that page, and figure out what I've missed with getting this properly hooked in. Please email me with any improvements you can offer. -jr From owner-freebsd-chromium@FreeBSD.ORG Thu Dec 6 20:51:11 2012 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 78D2EA05 for ; Thu, 6 Dec 2012 20:51:11 +0000 (UTC) (envelope-from evanm@google.com) Received: from mail-wg0-f52.google.com (mail-wg0-f52.google.com [74.125.82.52]) by mx1.freebsd.org (Postfix) with ESMTP id E10D68FC0C for ; Thu, 6 Dec 2012 20:51:10 +0000 (UTC) Received: by mail-wg0-f52.google.com with SMTP id 12so4000958wgh.31 for ; Thu, 06 Dec 2012 12:51:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=1tpsGnlH+zOvsYWXi7J8GR7N52lt8LSgGhDOeyHl2Pw=; b=oASInODdy1a6DR5AzVOtN0u+No0BBKyfRSsOwifafLBwCjxVDXSzTjkhYFpv0RHXK1 vG0rtDWXqMbDV+tF30W3SM6HkCXxI54bRZqtEuiVH/V3ARgbnqYq8Xh627NSt+EBzfcC ijYDfQM20b9/6JWaJ2LLm/2vMCFfnolALl59KgOVpPs+keY2f13HWhr/3T0OhiIcloOM y3UB7Isht4BDsMEKfPGF1HPmcY/m0LLiSWKHCza9ug2mnyhn7qcW87KHecPXN8aXkRkL ebhPZXS7br6X/6pyDgLEI0ZAOxjDsd3SLP2gOtTztywafSE8RGNpUogTKPGXtPcuQZTq DpxQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=1tpsGnlH+zOvsYWXi7J8GR7N52lt8LSgGhDOeyHl2Pw=; b=RRv5nw994Wf7A2ZnndHnUYkKcsGfDXcZN8BRZ23+fr129K+75Kq63sNefDihsgDu9t /lNpOAHeRu5D+DjCp48hYQ1dqDKPDgAWayU7TyRIN7aONSPhpnKR3AFXcrAGLQvZFiuc h7JHmXT7Mcc2TH8kEWARzvnH4Q8TCSgKI8czc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :x-gm-message-state; bh=1tpsGnlH+zOvsYWXi7J8GR7N52lt8LSgGhDOeyHl2Pw=; b=VjZw/KrkF/ThbgGyQnRBnkYHsiiLQbLeNL09c/91xB8KinLqed1sjAyiODak88/oz+ su2gWzGG3ZY0QEjgV4xZpG3Ly5K8wfe0wXQ92tZCjkPcoQJEAfwNYGIR7yuAIiFGqXn7 sVnLcIO3wrDXXvxS/4EFDu6+5kPsxHfqDWPsazzH9ZU2XW3rTc2urhEQ8WALl1hEuTuE IBvYiS7oiLBCnbc9bBHRLqCOVbJfRO0PNmwwJsDeag4ptr32S06pyP2tF4xXxmGUVBQO jec91vWbB2pfxZ3slU/FmSqZpiUfGLFqWr5Z9T1OFA4fLQ2hJsgUMzMvAKl4a8KZP5eg 2iSw== MIME-Version: 1.0 Received: by 10.180.8.133 with SMTP id r5mr4619975wia.7.1354827069533; Thu, 06 Dec 2012 12:51:09 -0800 (PST) Sender: evanm@google.com Received: by 10.216.151.35 with HTTP; Thu, 6 Dec 2012 12:51:09 -0800 (PST) In-Reply-To: <20121206004945.7ec2a1f1@shibato> References: <20121206004945.7ec2a1f1@shibato> Date: Thu, 6 Dec 2012 12:51:09 -0800 X-Google-Sender-Auth: n5ce3f_4-enE1P0vqH-vcKkFFcU Message-ID: Subject: Re: WIP: Wi-fi Geolocation Provider From: Evan Martin To: "J.R. Oldroyd" X-Gm-Message-State: ALoCoQnOd5lC3qCtYEthO4ljMBHD3gBIacpjspeHrRnjNiHQw5PnEb5S4yXLPfdtvUfxVeaaWF4Ya/96AiSqsYo2j1gao+4HBkSCZyv4a6V2BtGhETZd1i56p953WR/D7JsdzHJw8hWwEMAqIoVpBmZSP6+i4zqUpCsGfDBxh3BRBfrsspyG24Dykr6k/0CqFaf3SLxjfHSgUe1ekB+G9YqcVO7dUQDpzg== Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-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: Thu, 06 Dec 2012 20:51:11 -0000 (I used to work on Chrome, though not in this area. Your patch looks right enough to me. If you ever sent it upstream they'd want you to match the surrounding code style, stuff like two-space tabs and variable declarations where they're used instead of at the top of the functions.) To diagnose the problem: Does your DefaultFactoryFunction() implementation ever get called? Before your patch, what code was running when a page tried to geolocate? Your patch seems to be missing some minus lines where it removes the fallback code that was running for FreeBSD before. In particular, it looks like this file is providing some default empty implementation that you might need to disable (toggle some ifdefs): http://code.google.com/searchframe#OAMlx_jo-ck/src/content/browser/geolocation/empty_device_data_provider.cc It's not clear to me why your code even compiles with two implementations of this function, but this Chrome code seems overly tricky for what I'd naively think it needs to do so maybe there's some good reason. On Wed, Dec 5, 2012 at 9:49 PM, J.R. Oldroyd wrote: > It seems that Google's Geolocation Service lookups done using an > IPv6 address results in a location that is far, far, far away from > where you really are, and even lookups using IPv4 addresses are often > several km off. Since I am increasingly running into web pages that > want to "help me better" based on my location, it seems a more > accurate lookup is needed. > > So... I have knocked together a wifi_data_provider_freebsd.cc that > gets your list of wi-fi APs so that the geolocation lookup can be > done using the wi-fi AP information. > > The wi-fi AP code was tested and works as a stand-alone program. > > Now, I am not really a C++ guy and I am far from up-to-speed on > chromium's object methods and how to hook this in so the browser > actually finds and uses it. I could use some help with that. > > I've put what I have so far, and some additional details, here: > > http://opal.com/jr/freebsd/ports/www/chromium/files/ > > Anyone who cares to help integrate this into chromium, feel free to > grab the files from that page, and figure out what I've missed with > getting this properly hooked in. Please email me with any improvements > you can offer. > > -jr > _______________________________________________ > freebsd-chromium@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-chromium > To unsubscribe, send any mail to "freebsd-chromium-unsubscribe@freebsd.org > " > From owner-freebsd-chromium@FreeBSD.ORG Thu Dec 6 23:04:10 2012 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F1D5A1D9 for ; Thu, 6 Dec 2012 23:04:10 +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 B652A8FC0C for ; Thu, 6 Dec 2012 23:04:10 +0000 (UTC) Received: from pool-151-203-201-84.bos.east.verizon.net ([151.203.201.84] helo=homobox.opal.com) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1Tgk6b-00097y-74 for freebsd-chromium@freebsd.org; Thu, 06 Dec 2012 22:39:45 +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 qB6Mdhbf059109 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Thu, 6 Dec 2012 17:39:43 -0500 (EST) (envelope-from fbsd@opal.com) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 151.203.201.84 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX18i0oFeThIdIZqko5hv6YLX Date: Thu, 6 Dec 2012 17:39:42 -0500 From: "J.R. Oldroyd" To: freebsd-chromium@freebsd.org Subject: CFT: Wi-fi Geolocation Provider Message-ID: <20121206173942.2cd13b95@shibato> In-Reply-To: <20121206004945.7ec2a1f1@shibato> References: <20121206004945.7ec2a1f1@shibato> X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.6; amd64-portbld-freebsd8.2) 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]); Thu, 06 Dec 2012 17:39:43 -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 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: Thu, 06 Dec 2012 23:04:11 -0000 This is now working. Thanks to Evan Martin for looking over it and sending words of advice. A couple of additional changes were needed to other chromium files to remove stubs that were in use instead of this code, after which it worked. Please (re-)download the patches and try it out. There are now five new or changed port patch files. I'll give it a week or so for any feedback and then send it to the FreeBSD port maintainers. -jr From owner-freebsd-chromium@FreeBSD.ORG Fri Dec 7 02:10:13 2012 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ED11193B for ; Fri, 7 Dec 2012 02:10:13 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id D25D78FC0C for ; Fri, 7 Dec 2012 02:10:13 +0000 (UTC) Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id qB72A7CL021850; Thu, 6 Dec 2012 18:10:07 -0800 (PST) (envelope-from yuri@rawbw.com) Message-ID: <50C14FFE.9040909@rawbw.com> Date: Thu, 06 Dec 2012 18:10:06 -0800 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: "J.R. Oldroyd" Subject: Re: WIP: Wi-fi Geolocation Provider References: <20121206004945.7ec2a1f1@shibato> In-Reply-To: <20121206004945.7ec2a1f1@shibato> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-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: Fri, 07 Dec 2012 02:10:14 -0000 On 12/05/2012 21:49, J.R. Oldroyd wrote: > It seems that Google's Geolocation Service lookups done using an > IPv6 address results in a location that is far, far, far away from > where you really are, and even lookups using IPv4 addresses are often > several km off. Since I am increasingly running into web pages that > want to "help me better" based on my location, it seems a more > accurate lookup is needed. There is also the special blue tooth protocol that can be used in, ex, Android to connect to an external GPS provider. So that the nearby dedicated gps or the smartphone would be able to be the gps provider for the chrome running on the laptop. For example, open source "Bluetooth GPS for Android " app is doing this: https://sourceforge.net/p/bluegps4droid/git/ci/e67872ca05740d9b01a6ef14a3424ccafcb1a17c/tree/ Such blue tooth signal can also be used by chrome for geolocation service. Yuri From owner-freebsd-chromium@FreeBSD.ORG Fri Dec 7 09:58:14 2012 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 075E0E7C for ; Fri, 7 Dec 2012 09:58:14 +0000 (UTC) (envelope-from geo.liaskos@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 803BB8FC0C for ; Fri, 7 Dec 2012 09:58:13 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id u54so152462wey.13 for ; Fri, 07 Dec 2012 01:58:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Jco5fQ8ssqxhOrItP+vvU5+AvczSGq/HWKlV8wNFIIo=; b=MHj3q/1g3PX/Xg6nGwz3K6GS/3OQijr4oUnQINEd5QiOX7HPyWD3fhwEGW4OKoBt0z cida5CEfV9JHXJeSmdrSfgvT2RTqyc07j5NblMc+f77lTK8kXQrHrOaB/D8HatDUaMLk KK5qDi0t4fcPFYYPgQft9Wsx2N6JCeoWpkCMUykhwbHWu+JcD7PcvPTe/h7Wv9ShwhVS oK1X7LsXsqKeVjz+ReVR5ws6uAvSWP5RbBEdVVVS/ot1AY1rLeuF3hgRX2yNzFmryITc A40coF4RBMK7YAPSK/XhIw5V9pbeHjR1hp/bHYdvo4ZeSvAdCPWA6NNWwmRq3MwkNbG1 l8sg== MIME-Version: 1.0 Received: by 10.180.78.1 with SMTP id x1mr13789390wiw.17.1354874292231; Fri, 07 Dec 2012 01:58:12 -0800 (PST) Received: by 10.195.12.113 with HTTP; Fri, 7 Dec 2012 01:58:12 -0800 (PST) In-Reply-To: References: <20121206004945.7ec2a1f1@shibato> Date: Fri, 7 Dec 2012 11:58:12 +0200 Message-ID: Subject: Re: WIP: Wi-fi Geolocation Provider From: George Liaskos To: Evan Martin Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-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: Fri, 07 Dec 2012 09:58:14 -0000 Hello Martin, Sorry for hijacking the thread, what would be the best course of action to submit patches upstream? There are many local patches where we simply replace OS_OPENBSD with OS_BSD, anyone that i could assign for review? Regards, George On Thu, Dec 6, 2012 at 10:51 PM, Evan Martin wrote: > (I used to work on Chrome, though not in this area. Your patch looks right > enough to me. If you ever sent it upstream they'd want you to match the > surrounding code style, stuff like two-space tabs and variable declarations > where they're used instead of at the top of the functions.) > > To diagnose the problem: > Does your DefaultFactoryFunction() implementation ever get called? > Before your patch, what code was running when a page tried to geolocate? > Your patch seems to be missing some minus lines where it removes the > fallback code that was running for FreeBSD before. > > In particular, it looks like this file is providing some default empty > implementation that you might need to disable (toggle some ifdefs): > > http://code.google.com/searchframe#OAMlx_jo-ck/src/content/browser/geolocation/empty_device_data_provider.cc > It's not clear to me why your code even compiles with two implementations > of this function, but this Chrome code seems overly tricky for what I'd > naively think it needs to do so maybe there's some good reason. > > > > On Wed, Dec 5, 2012 at 9:49 PM, J.R. Oldroyd wrote: > > > It seems that Google's Geolocation Service lookups done using an > > IPv6 address results in a location that is far, far, far away from > > where you really are, and even lookups using IPv4 addresses are often > > several km off. Since I am increasingly running into web pages that > > want to "help me better" based on my location, it seems a more > > accurate lookup is needed. > > > > So... I have knocked together a wifi_data_provider_freebsd.cc that > > gets your list of wi-fi APs so that the geolocation lookup can be > > done using the wi-fi AP information. > > > > The wi-fi AP code was tested and works as a stand-alone program. > > > > Now, I am not really a C++ guy and I am far from up-to-speed on > > chromium's object methods and how to hook this in so the browser > > actually finds and uses it. I could use some help with that. > > > > I've put what I have so far, and some additional details, here: > > > > http://opal.com/jr/freebsd/ports/www/chromium/files/ > > > > Anyone who cares to help integrate this into chromium, feel free to > > grab the files from that page, and figure out what I've missed with > > getting this properly hooked in. Please email me with any improvements > > you can offer. > > > > -jr > > _______________________________________________ > > freebsd-chromium@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-chromium > > To unsubscribe, send any mail to " > freebsd-chromium-unsubscribe@freebsd.org > > " > > > _______________________________________________ > freebsd-chromium@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-chromium > To unsubscribe, send any mail to "freebsd-chromium-unsubscribe@freebsd.org > " >