From owner-freebsd-chromium@FreeBSD.ORG Mon May 23 07:07:38 2011 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 069B41065672 for ; Mon, 23 May 2011 07:07:38 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id B68EA8FC0A for ; Mon, 23 May 2011 07:07:37 +0000 (UTC) Received: by qwc9 with SMTP id 9so3599672qwc.13 for ; Mon, 23 May 2011 00:07:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=qpZ1r88uL/j3O6/XMru9JFAX0ySgQd2n2DiaFIFjVvY=; b=KEcwTRx9XyjKJY2QimgzZtM3pvTQrzhYji5MJF1t2utWlB6QCMB4u2QW/iXmChmWSC ybX6kciXQcFcpEv2b5EAYMjhayk6jAFb0tEOyDeyRAvuglYmIolzOeyBcDtJWmdL18UR 2y7XsR4DaDNu4/vmE4gAp9l6IMDRuYEoqeE7Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=Xex6NhKQFcciN38PXe9P4jxNiYLXVbs8Ziz7QnP4nSerqLFvIMqRvWpBymLx3lkCPA b4jXM4R9JpljdrDEcw94f77j4L9nvALJonsrW0X56YxfPlyBfh8fhdjUrphaSR3c19uX ZjHD78nUZDO1jOSH55E9Yfps2X7VB/5ZU9zAU= MIME-Version: 1.0 Received: by 10.229.61.7 with SMTP id r7mr1493642qch.20.1306134456870; Mon, 23 May 2011 00:07:36 -0700 (PDT) Received: by 10.229.247.203 with HTTP; Mon, 23 May 2011 00:07:36 -0700 (PDT) Date: Mon, 23 May 2011 09:07:36 +0200 Message-ID: From: =?ISO-8859-1?Q?Ren=E9_Ladan?= To: chromium@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Subject: Chromium on FreeBSD presentation X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2011 07:07:38 -0000 Hi list, I gave a presentation during BSDCan about Chromium, the sheets are available here: ftp://rene-ladan.nl/pub/chromium-bsdcan.pdf Ren=E9 From owner-freebsd-chromium@FreeBSD.ORG Mon May 23 11:06:30 2011 Return-Path: Delivered-To: chromium@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AD2701065670 for ; Mon, 23 May 2011 11:06:30 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 843D38FC0C for ; Mon, 23 May 2011 11:06:30 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p4NB6UBY051261 for ; Mon, 23 May 2011 11:06:30 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p4NB6THD051259 for chromium@FreeBSD.org; Mon, 23 May 2011 11:06:29 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 23 May 2011 11:06:29 GMT Message-Id: <201105231106.p4NB6THD051259@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 Cc: Subject: Current problem reports assigned to chromium@FreeBSD.org X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2011 11:06:30 -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/157237 chromium [PATCH] fix build of www/chromium with perl 5.14 1 problem total. From owner-freebsd-chromium@FreeBSD.ORG Mon May 23 15:40:17 2011 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7769106564A for ; Mon, 23 May 2011 15:40:17 +0000 (UTC) (envelope-from evanm@google.com) Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by mx1.freebsd.org (Postfix) with ESMTP id 6B6ED8FC15 for ; Mon, 23 May 2011 15:40:16 +0000 (UTC) Received: from kpbe17.cbf.corp.google.com (kpbe17.cbf.corp.google.com [172.25.105.81]) by smtp-out.google.com with ESMTP id p4NFeF7a031477 for ; Mon, 23 May 2011 08:40:15 -0700 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1306165216; bh=D3MjWpG7hq7xv5+ZQWatsBvaDK4=; h=MIME-Version:Sender:In-Reply-To:References:Date:Message-ID: Subject:From:To:Cc:Content-Type:Content-Transfer-Encoding; b=RYud6MlN9mVbovVy/13MOvYnUvcfDvN7aTIKQ54Fq5K9NitbrkpDIeBKSsVcSbqQk 2PgMEqzV2q3H+T1JLSYEg== Received: from gyg8 (gyg8.prod.google.com [10.243.50.136]) by kpbe17.cbf.corp.google.com with ESMTP id p4NFdLj8024126 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for ; Mon, 23 May 2011 08:40:14 -0700 Received: by gyg8 with SMTP id 8so2173367gyg.10 for ; Mon, 23 May 2011 08:40:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=2NGMO+mImxzSvPT6vhE9oJj4retDxY4xTWIZcHjvR58=; b=kNDsFx1lAUPKo3zU61UOGGckm40XkK5kjR1RlpP/8LAHTW1pHpVpPOhFdEcTjq+vY1 6ALBT2GzTv4FW7J3DqEw== DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=JDQd88fIzXj2vV/CrgkGvTRWOr7rBfCR3iQnSB1VIJ6IFnPfo92mkyu2h+w0SS/5Lv X37NTxfV6V/zE1pXC1CA== MIME-Version: 1.0 Received: by 10.101.175.1 with SMTP id c1mr4304006anp.99.1306165213860; Mon, 23 May 2011 08:40:13 -0700 (PDT) Sender: evanm@google.com Received: by 10.101.1.17 with HTTP; Mon, 23 May 2011 08:40:13 -0700 (PDT) In-Reply-To: References: Date: Mon, 23 May 2011 08:40:13 -0700 X-Google-Sender-Auth: 2Xrog2geB_z87o-xPdytuGLuEd8 Message-ID: From: Evan Martin To: =?ISO-8859-1?Q?Ren=E9_Ladan?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-System-Of-Record: true Cc: chromium@freebsd.org Subject: Re: Chromium on FreeBSD presentation X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2011 15:40:18 -0000 On Mon, May 23, 2011 at 12:07 AM, Ren=E9 Ladan wrote: > I gave a presentation during BSDCan about Chromium, the sheets are > available here: > ftp://rene-ladan.nl/pub/chromium-bsdcan.pdf For what it's worth, we take privacy seriously and our bad reputation is not deserved. It is frustating to see you call out "spy code" in the header of a slide. Features you mention on that slide, like geolocation, require the user to explicitly grant that information to the site that requests it (geolocation uses an infobar, sync you must first enable through the preferences, etc.). The malware/phishing blocking code goes to great effort to avoid sending information about the URLs you're visiting. Features like that, where there is a utility/privacy tradeoff, are clearly grouped together under a "privacy" heading in the preferences. Here's more about privacy in Chrome: http://www.google.com/intl/en/landing/chrome/google-chrome-privacy-whitep= aper.pdf If you ever find any code that does something you find problematic from a privacy standpoint, I would love to hear about it. From owner-freebsd-chromium@FreeBSD.ORG Mon May 23 19:12:50 2011 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6C952106566C for ; Mon, 23 May 2011 19:12:50 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id EC9168FC1D for ; Mon, 23 May 2011 19:12:49 +0000 (UTC) Received: by eyg7 with SMTP id 7so2689121eyg.13 for ; Mon, 23 May 2011 12:12:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=pYbPCpPFu/2jEu/Uzzah2ZI9WpE7fh0mU4yjOCDydv0=; b=B1NwRTkErf8yy4UVZqw5xMH+k81zWn0FhVUtBrwwsyMM5UjPOGQlQ4q04ZiqaGf8yT URgq32624R/6A9K09/9HkrFvAxOMKMggt8D/dTb6vf4rIfIy3+XOuyX7PkPZdyAIlyk1 DuNHSmBD+qDSUAn+tjxoII6ZcRkFAwjWHSqL4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=HoQSCXZPuZz4Jc8eU4IXH7Duk4oEJskMkKTdp4yrs9t7mipLU+ZDSKckOAj3qp2kll Sb6gy8I6VVKopXUQxfErhI8pamlRV4uF8AT+/iYjzm1+19IaPmNSI2cdiIJQIZPizi7p 1UTc2t4P6agXDFRrmdho2x8KO3x0cBBH3PvpA= Received: by 10.14.2.27 with SMTP id 27mr913273eee.9.1306177968600; Mon, 23 May 2011 12:12:48 -0700 (PDT) Received: from [192.168.1.14] (ip18-43-209-87.adsl2.static.versatel.nl [87.209.43.18]) by mx.google.com with ESMTPS id 34sm4835365eee.15.2011.05.23.12.12.47 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 23 May 2011 12:12:47 -0700 (PDT) Message-ID: <4DDAB1AD.6070502@gmail.com> Date: Mon, 23 May 2011 21:12:45 +0200 From: Rene Ladan User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; nl-NL; rv:1.9.2.17) Gecko/20110430 Thunderbird/3.1.10 MIME-Version: 1.0 To: Evan Martin References: In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: chromium@freebsd.org Subject: Re: Chromium on FreeBSD presentation X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2011 19:12:50 -0000 Op 23-05-2011 17:40, Evan Martin schreef: > On Mon, May 23, 2011 at 12:07 AM, René Ladan wrote: >> I gave a presentation during BSDCan about Chromium, the sheets are >> available here: >> ftp://rene-ladan.nl/pub/chromium-bsdcan.pdf > > For what it's worth, we take privacy seriously and our bad reputation > is not deserved. > It seems like I upset you, which was not at all what I intended. I use Chromium as my day-to-day browser both at work and at home. > It is frustating to see you call out "spy code" in > the header of a slide. Too quickly chosen wording on my side. I think we can safely assume that the audience, which were mostly BSD developers and BSD affiliates, understands that the "spy" code is not related to that as found in malware. > Features you mention on that slide, like > geolocation, require the user to explicitly grant that information to > the site that requests it (geolocation uses an infobar, sync you must > first enable through the preferences, etc.). True. > The malware/phishing > blocking code goes to great effort to avoid sending information about > the URLs you're visiting. Features like that, where there is a > utility/privacy tradeoff, are clearly grouped together under a > "privacy" heading in the preferences. > > Here's more about privacy in Chrome: > http://www.google.com/intl/en/landing/chrome/google-chrome-privacy-whitepaper.pdf > > If you ever find any code that does something you find problematic > from a privacy standpoint, I would love to hear about it. > I have removed the problematic sheet from the presentation. René From owner-freebsd-chromium@FreeBSD.ORG Mon May 23 19:57:50 2011 Return-Path: Delivered-To: chromium@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C93AC1065782; Mon, 23 May 2011 19:57:50 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A301D8FC08; Mon, 23 May 2011 19:57:50 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p4NJvo5o040319; Mon, 23 May 2011 19:57:50 GMT (envelope-from rene@freefall.freebsd.org) Received: (from rene@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p4NJvoFS040315; Mon, 23 May 2011 19:57:50 GMT (envelope-from rene) Date: Mon, 23 May 2011 19:57:50 GMT Message-Id: <201105231957.p4NJvoFS040315@freefall.freebsd.org> To: cmt@burggraben.net, rene@FreeBSD.org, chromium@FreeBSD.org From: rene@FreeBSD.org Cc: Subject: Re: ports/157237: [PATCH] fix build of www/chromium with perl 5.14 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2011 19:57:50 -0000 Synopsis: [PATCH] fix build of www/chromium with perl 5.14 State-Changed-From-To: open->closed State-Changed-By: rene State-Changed-When: Mon May 23 19:57:31 UTC 2011 State-Changed-Why: Committed, thanks http://www.freebsd.org/cgi/query-pr.cgi?pr=157237 From owner-freebsd-chromium@FreeBSD.ORG Mon May 23 20:40:12 2011 Return-Path: Delivered-To: chromium@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8A8CF106564A for ; Mon, 23 May 2011 20:40:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 7C59A8FC12 for ; Mon, 23 May 2011 20:40:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p4NKeCu6079270 for ; Mon, 23 May 2011 20:40:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p4NKeCot079269; Mon, 23 May 2011 20:40:12 GMT (envelope-from gnats) Date: Mon, 23 May 2011 20:40:12 GMT Message-Id: <201105232040.p4NKeCot079269@freefall.freebsd.org> To: chromium@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: ports/157237: commit references a PR X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2011 20:40:12 -0000 The following reply was made to PR ports/157237; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: ports/157237: commit references a PR Date: Mon, 23 May 2011 20:36:09 +0000 (UTC) rene 2011-05-23 20:35:55 UTC FreeBSD ports repository Modified files: www/chromium Makefile Log: Forced commit to note: PR: ports/157237 Revision Changes Path 1.28 +0 -0 ports/www/chromium/Makefile _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org" From owner-freebsd-chromium@FreeBSD.ORG Mon May 23 20:53:09 2011 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7B0E6106566B for ; Mon, 23 May 2011 20:53:09 +0000 (UTC) (envelope-from evanm@google.com) Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by mx1.freebsd.org (Postfix) with ESMTP id D25268FC0A for ; Mon, 23 May 2011 20:53:08 +0000 (UTC) Received: from hpaq2.eem.corp.google.com (hpaq2.eem.corp.google.com [172.25.149.2]) by smtp-out.google.com with ESMTP id p4NKr7Ck003093 for ; Mon, 23 May 2011 13:53:07 -0700 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1306183987; bh=aznfpMdnRhKWmxGak7WlewyJCnw=; h=MIME-Version:Sender:In-Reply-To:References:Date:Message-ID: Subject:From:To:Cc:Content-Type:Content-Transfer-Encoding; b=TcggKSD5ZtB2a3GXoFVAFIH4j0BGFJI16fXSDma05is1ipn7VZfTaBaXOFl/BysYk p/aGAZEGREYVCRekiXz8g== Received: from yxp4 (yxp4.prod.google.com [10.190.4.196]) by hpaq2.eem.corp.google.com with ESMTP id p4NKqd6U004601 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for ; Mon, 23 May 2011 13:53:06 -0700 Received: by yxp4 with SMTP id 4so3031598yxp.24 for ; Mon, 23 May 2011 13:53:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=b8feADcBQdw2ElP2mEruNM5CArsCTb3hbojlvvKv3Rw=; b=nzwMc66eudDhwo3mtFuxq0JJB30NNoWYKc1wsKQOVkR+9cNf4SPej9GRNg8D8w7Lt1 WSxL5HXptsrrwPR+D6WA== DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=D/6pzSgXKapF5Xbug8HSVzQpQ7gFcGVAi9gdUxIDfiea4+u2uD8NuwAY4XL6qRijoD SqYMeSSR1HXD1M+hG6aA== MIME-Version: 1.0 Received: by 10.101.167.37 with SMTP id u37mr4616802ano.33.1306183985273; Mon, 23 May 2011 13:53:05 -0700 (PDT) Sender: evanm@google.com Received: by 10.101.1.17 with HTTP; Mon, 23 May 2011 13:53:05 -0700 (PDT) In-Reply-To: <4DDAB1AD.6070502@gmail.com> References: <4DDAB1AD.6070502@gmail.com> Date: Mon, 23 May 2011 13:53:05 -0700 X-Google-Sender-Auth: zpFruGhtU-kgO07_xZ1t4M-_OMY Message-ID: From: Evan Martin To: Rene Ladan Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-System-Of-Record: true Cc: chromium@freebsd.org Subject: Re: Chromium on FreeBSD presentation X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2011 20:53:09 -0000 On Mon, May 23, 2011 at 12:12 PM, Rene Ladan wrote: > Op 23-05-2011 17:40, Evan Martin schreef: >> On Mon, May 23, 2011 at 12:07 AM, Ren=E9 Ladan wro= te: >>> I gave a presentation during BSDCan about Chromium, the sheets are >>> available here: >>> ftp://rene-ladan.nl/pub/chromium-bsdcan.pdf >> >> For what it's worth, we take privacy seriously and our bad reputation >> is not deserved. >> > It seems like I upset you, which was not at all what I intended. Ah, that's good to hear. Sorry for getting upset. I read too much into it= . :) From owner-freebsd-chromium@FreeBSD.ORG Wed May 25 20:11:00 2011 Return-Path: Delivered-To: chromium@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 780691065677 for ; Wed, 25 May 2011 20:11:00 +0000 (UTC) (envelope-from gtodd-1306353132.73393@iciti.ca) Received: from mailout.easydns.com (mailout.easydns.com [64.68.200.141]) by mx1.freebsd.org (Postfix) with ESMTP id 38BFF8FC28 for ; Wed, 25 May 2011 20:10:59 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mailout.easydns.com (Postfix) with ESMTP id 387025811 for ; Wed, 25 May 2011 15:53:05 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at mailout.easydns.com Received: from mailout.easydns.com ([127.0.0.1]) by localhost (mailout.easydns.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4MMXWUYjdTff for ; Wed, 25 May 2011 15:53:04 -0400 (EDT) Received: from wawanesa.iciti.ca (CPE0080c8f208a5-CM001371173cf8.cpe.net.cable.rogers.com [99.246.61.82]) by mailout.easydns.com (Postfix) with ESMTPA id 12E2456D3 for ; Wed, 25 May 2011 15:53:04 -0400 (EDT) Received: (qmail 73394 invoked by uid 1001); 25 May 2011 15:52:02 -0400 Date: 25 May 2011 19:52:02 -0000 Message-ID: <20110525195202.73393.qmail@wawanesa.iciti.ca> From: gtodd@iciti.ca To: chromium@FreeBSD.org X-Mailer: 822mess.c qmail-injected by hand babyee! X-Mailer: Composition by my friend ed(1) X-Mailer: Follow me using e-mail messages. Cc: Subject: Any attempt to print with chromium causes sigsev X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 May 2011 20:11:00 -0000 Hi, I think this is a well known bug? Should I file a PR on the port? The main chromium development platform seems to be Windows (and some Linux) where the bug does not manifest. Upstream they'd like bug reports with backtraces and patches! I am attempting to build a debug version of trunk to see if this has been resolved and get a meaningful trace on the crash with our latest version. These are non-trivial operations at this site ;-) Since this seems difficult to patch/fix for FreeBSD should the crash be mentioned in UPDATING or pkg-message? Regards, GRT From owner-freebsd-chromium@FreeBSD.ORG Thu May 26 07:45:50 2011 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B5D1D106566B for ; Thu, 26 May 2011 07:45:50 +0000 (UTC) (envelope-from geo.liaskos@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 746AC8FC0C for ; Thu, 26 May 2011 07:45:50 +0000 (UTC) Received: by yxl31 with SMTP id 31so229951yxl.13 for ; Thu, 26 May 2011 00:45:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=p7tPxRe0/1CQI9HDOiMlhonncizZLvHKv0zIlCgecAw=; b=tSWsmGFJbMHOtOgrx0mFUT/GE/forlDVmf2vRNee8fuhHXm1E5OX6YEsDLNeAgYGE9 aRSOs0FYfaRGmQuLvgSF/COfYv8Kto4cFW2lBiDRfxI0WJ7Xvb2jQUI1NrVJcl7cmfFM Nw1G9cRFRODp/by7grdd/H6HdZz7Q71X08PD8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=bECSjoPj3r9uREel6jbLBCW7bWG3ux8tmZr0AZRb24S8Nxi17esKHCeDn6e+9L8mAf Qk/2qKHPU81csFccjkRgrkop9SBnfR5mHCzFFasl0B4mf3MW2igTomnYvtCLWxz+WVv+ 0MBnw1G3aFxf5qjCIDEYXog4pBQSjHxlVG2KQ= MIME-Version: 1.0 Received: by 10.100.255.2 with SMTP id c2mr377603ani.41.1306395949584; Thu, 26 May 2011 00:45:49 -0700 (PDT) Received: by 10.100.32.14 with HTTP; Thu, 26 May 2011 00:45:49 -0700 (PDT) In-Reply-To: <20110525195202.73393.qmail@wawanesa.iciti.ca> References: <20110525195202.73393.qmail@wawanesa.iciti.ca> Date: Thu, 26 May 2011 10:45:49 +0300 Message-ID: From: George Liaskos To: gtodd@iciti.ca Content-Type: text/plain; charset=UTF-8 Cc: chromium@freebsd.org Subject: Re: Any attempt to print with chromium causes sigsev X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 May 2011 07:45:50 -0000 On Wed, May 25, 2011 at 10:52 PM, wrote: > Hi, I think this is a well known bug? Should I file a PR on > the port? > > The main chromium development platform seems to be Windows (and > some Linux) where the bug does not manifest. Upstream they'd like > bug reports with backtraces and patches! I am attempting to build > a debug version of trunk to see if this has been resolved and get > a meaningful trace on the crash with our latest version. > > These are non-trivial operations at this site ;-) > > Since this seems difficult to patch/fix for FreeBSD should the crash > be mentioned in UPDATING or pkg-message? > > Regards, > > GRT >From chrome/browser/browser_main_posix.cc: 23 #if defined(OS_LINUX) && !defined(OS_CHROMEOS) 24 #include "chrome/browser/printing/print_dialog_gtk.h" 25 #endif this seems to be a good starting point. It is in my todo list for some time now :p I will take a look at it. Regards, George From owner-freebsd-chromium@FreeBSD.ORG Thu May 26 19:34:32 2011 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1FD821065675 for ; Thu, 26 May 2011 19:34:32 +0000 (UTC) (envelope-from geo.liaskos@gmail.com) Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by mx1.freebsd.org (Postfix) with ESMTP id C5C8B8FC1C for ; Thu, 26 May 2011 19:34:31 +0000 (UTC) Received: by yie12 with SMTP id 12so558345yie.13 for ; Thu, 26 May 2011 12:34:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=OXUNR5WTD9NBhNUYoyMr4Ls3vkRmyYf1KMqCr12pRCQ=; b=EEkAqVT+dvdWx4j6tO84WeP0hC1h3+G7u3nmF6IyadmjoSxvdrMDpBFbimNDT9sath rg0QN4lKL9kppLlXspsUJhl/6yMJgV5GY5UPXtf9PQcE1jfHiHurxKyEr4GtbhzO+N/6 LOYJjEMRNky71OmkVTwwR0sb54PpRkFvUDZ3w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=e+2NbT6Y+MKBgkDn3EHlUD40LH2A+JtIs4DhdzVd0+A9vj62DcgUx+CuBZq8EGQ6v9 yWEDNklKm98x1crWEU87iz7bOlEOWrl17ELpbtkVq+P/glQMNQj+AMogYED8ySZkgX6E /DvqhJl85kJQGcY63LL7cZplSGM8C4kKNQ6So= MIME-Version: 1.0 Received: by 10.101.46.19 with SMTP id y19mr940540anj.19.1306438470871; Thu, 26 May 2011 12:34:30 -0700 (PDT) Received: by 10.100.32.14 with HTTP; Thu, 26 May 2011 12:34:30 -0700 (PDT) In-Reply-To: References: <20110525195202.73393.qmail@wawanesa.iciti.ca> Date: Thu, 26 May 2011 22:34:30 +0300 Message-ID: From: George Liaskos To: gtodd@iciti.ca Content-Type: text/plain; charset=UTF-8 Cc: chromium@freebsd.org Subject: Re: Any attempt to print with chromium causes sigsev X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 May 2011 19:34:32 -0000 Ok , this is the backtrace #0 0x000000080582f27a in getframeaddr () from /usr/local/lib/libexecinfo.so.1 #1 0x0000000805828e3f in backtrace () from /usr/local/lib/libexecinfo.so.1 #2 0x00000000012c67e1 in base::debug::StackTrace::StackTrace (this=0x7fffffff8e20) at base/debug/stack_trace_posix.cc:161 #3 0x00000000012dbfdd in logging::LogMessage::~LogMessage (this=0x7fffffff9570, __in_chrg=) at base/logging.cc:551 #4 0x0000000000689cf7 in (anonymous namespace)::GLibLogHandler (log_domain=0x806843ea3 "Gtk", log_level=G_LOG_LEVEL_CRITICAL, message=0x8153f8f00 "IA__gtk_printer_is_accepting_jobs: assertion `GTK_IS_PRINTER (printer)' failed", userdata=0x0) at chrome/browser/browser_main.cc:886 #5 0x000000080981ab21 in g_logv () from /usr/local/lib/libglib-2.0.so.0 #6 0x000000080981ae13 in g_log () from /usr/local/lib/libglib-2.0.so.0 #7 0x0000000806741de3 in IA__gtk_printer_is_accepting_jobs (printer=0x0) at gtkprinter.c:720 #8 0x000000080674d72d in selected_printer_changed (selection=0x815479500, dialog=0x815432420) at gtkprintunixdialog.c:1889 #9 0x000000080918f54f in g_closure_invoke () from /usr/local/lib/libgobject-2.0.so.0 #10 0x00000008091a6531 in ?? () from /usr/local/lib/libgobject-2.0.so.0 #11 0x00000008091a83d0 in g_signal_emit_valist () from /usr/local/lib/libgobject-2.0.so.0 #12 0x00000008091a8698 in g_signal_emit_by_name () from /usr/local/lib/libgobject-2.0.so.0 #13 0x0000000806681e37 in gtk_tree_view_row_deleted (model=0x81545cb80, path=0x815404110, data=0x81543e420) at gtktreeview.c:8669 #14 0x000000080918f54f in g_closure_invoke () from /usr/local/lib/libgobject-2.0.so.0 #15 0x00000008091a6531 in ?? () from /usr/local/lib/libgobject-2.0.so.0 #16 0x00000008091a83d0 in g_signal_emit_valist () from /usr/local/lib/libgobject-2.0.so.0 #17 0x00000008091a87d3 in g_signal_emit () from /usr/local/lib/libgobject-2.0.so.0 #18 0x0000000806653b29 in IA__gtk_tree_model_row_deleted (tree_model=0x81545cb80, path=0x815404110) at gtktreemodel.c:1566 #19 0x0000000806656ade in gtk_tree_model_filter_remove_node (filter=0x81545cb80, iter=0x7fffffffa990) at gtktreemodelfilter.c:1042 #20 0x0000000806657232 in gtk_tree_model_filter_row_changed (c_model=0x81346de00, c_path=0x815456480, c_iter=0x7fffffffaac0, data=0x81545cb80) at gtktreemodelfilter.c:1280 #21 0x000000080665c86d in gtk_tree_model_filter_refilter_helper (model=0x81346de00, path=0x815456480, iter=0x7fffffffaac0, data=0x81545cb80) at gtktreemodelfilter.c:3457 #22 0x0000000806653c52 in gtk_tree_model_foreach_helper (model=0x81346de00, iter=0x7fffffffaac0, path=0x815456480, func=0x80665c840 , user_data=0x81545cb80) at gtktreemodel.c:1607 #23 0x0000000806653dd5 in IA__gtk_tree_model_foreach (model=0x81346de00, func=0x80665c840 , user_data=0x81545cb80) at gtktreemodel.c:1653 #24 0x000000080665c921 in IA__gtk_tree_model_filter_refilter (filter=0x81545cb80) at gtktreemodelfilter.c:3477 #25 0x000000080674c871 in update_dialog_from_capabilities (dialog=0x815432420) at gtkprintunixdialog.c:1474 #26 0x0000000806754f41 in IA__gtk_print_unix_dialog_set_manual_capabilities (dialog=0x815432420, capabilities=47) at gtkprintunixdialog.c:4215 #27 0x00000000008378e9 in PrintDialogGtk::PrintDialogGtk (this=0x81513c960, callback=0x815460980, context=0x81434c5a0) at chrome/browser/printing/print_dialog_gtk.cc:80 #28 0x0000000000837a11 in PrintDialogGtk::CreatePrintDialog (callback=0x815460980, context=0x81434c5a0) at chrome/browser/printing/print_dialog_gtk.cc:29 #29 0x0000000001202abb in printing::PrintingContextCairo::AskUserForSettings (this=0x81434c5a0, parent_view=0xda19f542cfbefaf2, max_pages=1, has_selection=false, callback=0x815460980) at printing/printing_context_cairo.cc:87 #30 0x0000000000dae78d in printing::PrintJobWorker::GetSettingsWithUI (this=0x814c06000, parent_view=0xda19f542cfbefaf2, document_page_count=1, has_selection=false) at chrome/browser/printing/print_job_worker.cc:164 #31 0x0000000000dafae2 in DispatchToMethod (obj=0x814c06000, method= (void (printing::PrintJobWorker::*)(printing::PrintJobWorker *, printing::PrintingContext::NativeView, int, bool)) 0xdae680 , arg=...) at ./base/tuple.h:564 #32 0x0000000000dafb2a in RunnableMethod >::Run (this=0x814ba1a50) at ./base/task.h:331 #33 0x00000000012de6b6 in MessageLoop::RunTask (this=0x8112b4540, task=0x814ba1a50) at base/message_loop.cc:367 #34 0x00000000012de88e in MessageLoop::DeferOrRunPendingTask (this=0x8112b4540, pending_task=...) at base/message_loop.cc:376 #35 0x00000000012df086 in MessageLoop::DoWork (this=0x8112b4540) at base/message_loop.cc:569 #36 0x000000000134b4ae in base::MessagePumpForUI::RunWithDispatcher (this=0x8112698a0, delegate=0x8112b4540, dispatcher=0x0) at base/message_pump_glib.cc:214 #37 0x000000000134ad6d in base::MessagePumpForUI::Run (this=0x8112698a0, delegate=0x8112b4540) at base/message_pump_glib.cc:318 #38 0x00000000012df3e2 in MessageLoop::RunInternal (this=0x8112b4540) at base/message_loop.cc:342 #39 0x00000000012df405 in MessageLoop::RunHandler (this=0x8112b4540) at base/message_loop.cc:315 #40 0x00000000012df449 in MessageLoopForUI::Run (this=0x8112b4540, dispatcher=0x0) at base/message_loop.cc:690 #41 0x000000000068a5b8 in (anonymous namespace)::RunUIMessageLoop (browser_process=0x81156f000) at chrome/browser/browser_main.cc:558 #42 0x000000000068dadf in BrowserMain (parameters=...) at chrome/browser/browser_main.cc:1797 #43 0x000000000055831a in (anonymous namespace)::RunNamedProcessTypeMain (process_type=..., main_function_params=...) at chrome/app/chrome_main.cc:449 #44 0x000000000055946b in ChromeMain (argc=1, argv=0x7fffffffd430) at chrome/app/chrome_main.cc:749 #45 0x0000000000559cca in main (argc=1, argv=0x7fffffffd430) at chrome/app/chrome_exe_main_gtk.cc:51 printer is NULL at frame 7, there's an open issue which seems relevant http://code.google.com/p/chromium/issues/detail?id=79394 From owner-freebsd-chromium@FreeBSD.ORG Thu May 26 22:06:50 2011 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CF67F106566C for ; Thu, 26 May 2011 22:06:50 +0000 (UTC) (envelope-from robert@openbsd.org) Received: from x2100.humppa.hu (x2100.humppa.hu [84.2.34.134]) by mx1.freebsd.org (Postfix) with ESMTP id 4D2628FC16 for ; Thu, 26 May 2011 22:06:50 +0000 (UTC) Received: from x2100.humppa.hu (robert@localhost [127.0.0.1]) by x2100.humppa.hu (8.14.3/8.14.3) with ESMTP id p4QLigZ8024413 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Thu, 26 May 2011 23:44:43 +0200 (CEST) Received: (from robert@localhost) by x2100.humppa.hu (8.14.3/8.14.3/Submit) id p4QLigMN025092; Thu, 26 May 2011 23:44:42 +0200 (CEST) X-Authentication-Warning: x2100.humppa.hu: robert set sender to robert@openbsd.org using -f Date: Thu, 26 May 2011 23:44:42 +0200 From: Robert Nagy To: George Liaskos Message-ID: <20110526214442.GA20235@bsd.hu> References: <20110525195202.73393.qmail@wawanesa.iciti.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: chromium@freebsd.org, gtodd@iciti.ca Subject: Re: Any attempt to print with chromium causes sigsev X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 May 2011 22:06:50 -0000 Hey You will need the following patches to be used on FreeBSD too for printing: http://marc.info/?l=openbsd-ports-cvs&m=130641001611270&w=2 You can get them at http://www.openbsd.org/cgi-bin/cvsweb/ports/www/chromium/patches/ Note that chrome only supports printing to PDF files therefore you won't be able to print to lpd. Only CUPS is supported, so you will also need to have the gtk cups module to be installed. From owner-freebsd-chromium@FreeBSD.ORG Thu May 26 23:01:01 2011 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 01A01106564A for ; Thu, 26 May 2011 23:01:01 +0000 (UTC) (envelope-from gtodd@iciti.ca) Received: from mailout.easydns.com (mailout.easydns.com [64.68.200.141]) by mx1.freebsd.org (Postfix) with ESMTP id A6F6F8FC08 for ; Thu, 26 May 2011 23:01:00 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mailout.easydns.com (Postfix) with ESMTP id 125EE582D for ; Thu, 26 May 2011 18:43:24 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at mailout.easydns.com Received: from mailout.easydns.com ([127.0.0.1]) by localhost (mailout.easydns.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GLOsD3JpDIAB for ; Thu, 26 May 2011 18:43:23 -0400 (EDT) Received: from wawanesa.iciti.ca (CPE0080c8f208a5-CM001371173cf8.cpe.net.cable.rogers.com [99.246.61.82]) by mailout.easydns.com (Postfix) with ESMTPA id 599EE58BD for ; Thu, 26 May 2011 18:43:22 -0400 (EDT) Received: (qmail 11175 invoked from network); 26 May 2011 18:42:19 -0400 Received: from unknown (HELO wawanesa.iciti.ca) (192.168.2.4) by wawanesa.iciti.ca with ESMTP; 26 May 2011 18:42:19 -0400 Message-ID: <4DDED74B.10600@iciti.ca> Date: Thu, 26 May 2011 18:42:19 -0400 From: Graham Todd User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.13) Gecko/20110118 Thunderbird/3.1.7 MIME-Version: 1.0 To: Robert Nagy References: <20110525195202.73393.qmail@wawanesa.iciti.ca> <20110526214442.GA20235@bsd.hu> In-Reply-To: <20110526214442.GA20235@bsd.hu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: chromium@freebsd.org Subject: Re: Any attempt to print with chromium causes sigsev X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 May 2011 23:01:01 -0000 On 05/26/2011 17:44, Robert Nagy wrote: > Hey > > You will need the following patches to be used on FreeBSD too for printing: > > http://marc.info/?l=openbsd-ports-cvs&m=130641001611270&w=2 > > You can get them at http://www.openbsd.org/cgi-bin/cvsweb/ports/www/chromium/patches/ > > Note that chrome only supports printing to PDF files therefore you won't be > able to print to lpd. Only CUPS is supported, so you will also need to have the gtk cups > module to be installed. Excellent! I just noticed printing does not crash chromium on openbsd. Not sure why I didn't think to compare. PDF printing is great ... even a no-op is fine. It's just a pain when chromium crashes just as you click to save/print your boarding pass :-D Anyway, I will leave to FreeBSD port maintainer to apply as they see fit :) These patches seem small enough to be reviewable (i.e. not like the BSD "monster patch" I was told about in #chromium). Are they being gradually accepted upstream. The patch review process seems fairly serious so I wonder if there's someway to accept a large set of patches and "catch up". From owner-freebsd-chromium@FreeBSD.ORG Fri May 27 06:05:59 2011 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37FD2106564A for ; Fri, 27 May 2011 06:05:59 +0000 (UTC) (envelope-from robert@openbsd.org) Received: from x2100.humppa.hu (x2100.humppa.hu [84.2.34.134]) by mx1.freebsd.org (Postfix) with ESMTP id BA0958FC0A for ; Fri, 27 May 2011 06:05:58 +0000 (UTC) Received: from x2100.humppa.hu (robert@localhost [127.0.0.1]) by x2100.humppa.hu (8.14.3/8.14.3) with ESMTP id p4R65uC0028854 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Fri, 27 May 2011 08:05:56 +0200 (CEST) Received: (from robert@localhost) by x2100.humppa.hu (8.14.3/8.14.3/Submit) id p4R65uuW012370; Fri, 27 May 2011 08:05:56 +0200 (CEST) X-Authentication-Warning: x2100.humppa.hu: robert set sender to robert@openbsd.org using -f Date: Fri, 27 May 2011 08:05:56 +0200 From: Robert Nagy To: Graham Todd Message-ID: <20110527060556.GA21496@bsd.hu> References: <20110525195202.73393.qmail@wawanesa.iciti.ca> <20110526214442.GA20235@bsd.hu> <4DDED74B.10600@iciti.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4DDED74B.10600@iciti.ca> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: chromium@freebsd.org Subject: Re: Any attempt to print with chromium causes sigsev X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 May 2011 06:05:59 -0000 On (2011-05-26 18:42), Graham Todd wrote: > On 05/26/2011 17:44, Robert Nagy wrote: > >Hey > > > >You will need the following patches to be used on FreeBSD too for printing: > > > >http://marc.info/?l=openbsd-ports-cvs&m=130641001611270&w=2 > > > >You can get them at http://www.openbsd.org/cgi-bin/cvsweb/ports/www/chromium/patches/ > > > >Note that chrome only supports printing to PDF files therefore you won't be > >able to print to lpd. Only CUPS is supported, so you will also need to have the gtk cups > >module to be installed. > > Excellent! I just noticed printing does not crash chromium on > openbsd. Not sure why I didn't think to compare. > > PDF printing is great ... even a no-op is fine. It's just a pain > when chromium crashes just as you click to save/print your boarding > pass :-D Anyway, I will leave to FreeBSD port maintainer to apply as > they see fit :) > > These patches seem small enough to be reviewable (i.e. not like the > BSD "monster patch" I was told about in #chromium). Are they being > gradually accepted upstream. The patch review process seems fairly > serious so I wonder if there's someway to accept a large set of > patches and "catch up". > > I have some friends at Google and they are trying to get the patches in. From owner-freebsd-chromium@FreeBSD.ORG Fri May 27 09:06:06 2011 Return-Path: Delivered-To: chromium@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ACB9C106564A for ; Fri, 27 May 2011 09:06:06 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from dirg.bris.ac.uk (dirg.bris.ac.uk [137.222.10.102]) by mx1.freebsd.org (Postfix) with ESMTP id 6C0E88FC14 for ; Fri, 27 May 2011 09:06:06 +0000 (UTC) Received: from ncsc.bris.ac.uk ([137.222.10.41]) by dirg.bris.ac.uk with esmtp (Exim 4.72) (envelope-from ) id 1QPsjU-0005rh-PC for chromium@FreeBSD.org; Fri, 27 May 2011 09:49:24 +0100 Received: from mech-cluster241.men.bris.ac.uk ([137.222.187.241]) by ncsc.bris.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1QPsjU-0006xe-Kk for chromium@FreeBSD.org; Fri, 27 May 2011 09:49:24 +0100 Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.4/8.14.4) with ESMTP id p4R8nOR1053368 for ; Fri, 27 May 2011 09:49:24 +0100 (BST) (envelope-from mexas@bristol.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.4/8.14.4/Submit) id p4R8nOxC053367 for chromium@FreeBSD.org; Fri, 27 May 2011 09:49:24 +0100 (BST) (envelope-from mexas@bristol.ac.uk) X-Authentication-Warning: mech-cluster241.men.bris.ac.uk: mexas set sender to mexas@bristol.ac.uk using -f Date: Fri, 27 May 2011 09:49:24 +0100 From: Anton Shterenlikht To: chromium@FreeBSD.org Message-ID: <20110527084924.GA52295@mech-cluster241.men.bris.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: Subject: configure fails on ia64 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 May 2011 09:06:06 -0000 I know it's not supposed to be built on ia64, but perhaps this can help you debug chromium on supported arches. Many thanks Anton On FreeBSD 9.0-CURRENT #3 r221488 ia64 # make showconfig ===> The following configuration options are available for chromium-11.0.696.71: CODECS=off "Compile and enable patented codecs like H.264" GCONF=on "Use GConf2 for preferences" VPX=on "Use system libvpx for VP8 codec" ===> Use 'make config' to modify these settings # Script started on Fri May 27 09:47:05 2011 make configure ===> chromium-11.0.696.71 depends on file: /usr/local/bin/flex - found ===> chromium-11.0.696.71 depends on file: /usr/local/bin/gperf - found ===> chromium-11.0.696.71 depends on executable: bash - found ===> chromium-11.0.696.71 depends on executable: yasm - found ===> chromium-11.0.696.71 depends on package: nss>=3.12 - found ===> chromium-11.0.696.71 depends on file: /usr/local/bin/python2.7 - found ===> chromium-11.0.696.71 depends on executable: gmake - found ===> chromium-11.0.696.71 depends on executable: bison - found ===> chromium-11.0.696.71 depends on file: /usr/local/libdata/pkgconfig/scrnsaverproto.pc - found ===> chromium-11.0.696.71 depends on file: /usr/local/libdata/pkgconfig/x11.pc - found ===> chromium-11.0.696.71 depends on file: /usr/local/libdata/pkgconfig/xproto.pc - found ===> chromium-11.0.696.71 depends on file: /usr/local/libdata/pkgconfig/xscrnsaver.pc - found ===> chromium-11.0.696.71 depends on file: /usr/local/libdata/pkgconfig/xtst.pc - found ===> chromium-11.0.696.71 depends on file: /usr/local/bin/perl5.12.3 - found ===> chromium-11.0.696.71 depends on file: /usr/local/bin/intltool-extract - found ===> chromium-11.0.696.71 depends on executable: pkg-config - found ===> chromium-11.0.696.71 depends on shared library: execinfo.1 - found ===> chromium-11.0.696.71 depends on shared library: cairo.2 - found ===> chromium-11.0.696.71 depends on shared library: dbus-1.3 - found ===> chromium-11.0.696.71 depends on shared library: dbus-glib-1.2 - found ===> chromium-11.0.696.71 depends on shared library: asound.2 - found ===> chromium-11.0.696.71 depends on shared library: freetype.9 - found ===> chromium-11.0.696.71 depends on shared library: nss3.1 - found ===> chromium-11.0.696.71 depends on shared library: gnome-keyring.0 - found ===> chromium-11.0.696.71 depends on shared library: ibus.2 - found ===> chromium-11.0.696.71 depends on shared library: vpx - found ===> chromium-11.0.696.71 depends on shared library: atk-1.0.0 - found ===> chromium-11.0.696.71 depends on shared library: gconf-2.4 - found ===> chromium-11.0.696.71 depends on shared library: glib-2.0.0 - found ===> chromium-11.0.696.71 depends on shared library: gtk-x11-2.0.0 - found ===> chromium-11.0.696.71 depends on shared library: IDL-2.0 - found ===> chromium-11.0.696.71 depends on shared library: xml2.5 - found ===> chromium-11.0.696.71 depends on shared library: xslt.2 - found ===> chromium-11.0.696.71 depends on shared library: ORBit-2.0 - found ===> chromium-11.0.696.71 depends on shared library: pango-1.0.0 - found ===> chromium-11.0.696.71 depends on shared library: dconf.0 - found ===> Configuring for chromium-11.0.696.71 cd /usr/ports/www/chromium/work/chromium-courgette-redacted-11.0.696.71 && GYP_DEFINES="use_system_libxml=1 use_system_ffmpeg=0 use_system_yasm=1 python_ver=2.7 ffmpeg_branding=Chromium use_proprietary_codecs=0 disable_sse2=1 use_system_vpx=1" /usr/local/bin/python2.7 ./build/gyp_chromium chrome/chrome.gyp --depth . Updating projects from gyp files... Traceback (most recent call last): File "./build/gyp_chromium", line 143, in sys.exit(gyp.main(args)) File "./tools/gyp/pylib/gyp/__init__.py", line 446, in main options.circular_check) File "./tools/gyp/pylib/gyp/__init__.py", line 84, in Load depth, generator_input_info, check, circular_check) File "./tools/gyp/pylib/gyp/input.py", line 2174, in Load depth, check) File "./tools/gyp/pylib/gyp/input.py", line 379, in LoadTargetBuildFile build_file_path) File "./tools/gyp/pylib/gyp/input.py", line 888, in ProcessVariablesAndConditionsInDict variables, build_file, 'variables') File "./tools/gyp/pylib/gyp/input.py", line 940, in ProcessVariablesAndConditionsInDict ProcessConditionsInDict(the_dict, is_late, variables, build_file) File "./tools/gyp/pylib/gyp/input.py", line 817, in ProcessConditionsInDict variables, build_file) File "./tools/gyp/pylib/gyp/input.py", line 895, in ProcessVariablesAndConditionsInDict expanded = ExpandVariables(value, is_late, variables, build_file) File "./tools/gyp/pylib/gyp/input.py", line 652, in ExpandVariables (contents, p.returncode)) Exception: Call to '../build/linux/python_arch.sh /usr/local/lib/libpython2.7.so.1' returned exit status 1. while trying to load chrome/chrome.gyp *** Error code 1 Stop in /usr/ports/www/chromium. *** Error code 1 Stop in /usr/ports/www/chromium. Script done on Fri May 27 09:47:10 2011 -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 From owner-freebsd-chromium@FreeBSD.ORG Fri May 27 16:36:07 2011 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7B132106564A for ; Fri, 27 May 2011 16:36:07 +0000 (UTC) (envelope-from evanm@google.com) Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by mx1.freebsd.org (Postfix) with ESMTP id EDFFB8FC1A for ; Fri, 27 May 2011 16:36:06 +0000 (UTC) Received: from wpaz13.hot.corp.google.com (wpaz13.hot.corp.google.com [172.24.198.77]) by smtp-out.google.com with ESMTP id p4RGa5DW006191 for ; Fri, 27 May 2011 09:36:05 -0700 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1306514165; bh=BLE4MvcCjZl5fvo09wrIsHdNs6E=; h=MIME-Version:Sender:In-Reply-To:References:Date:Message-ID: Subject:From:To:Cc:Content-Type; b=xlsu7c4Msi+GXSxA1FoqnXFgi58Z16BrLSMm1H/oDlYhjlR+JFsq3zhdjcHMiepS8 RsvnSIgGcACsJHl1cWXTg== Received: from yxt33 (yxt33.prod.google.com [10.190.5.225]) by wpaz13.hot.corp.google.com with ESMTP id p4RGa3mQ022653 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for ; Fri, 27 May 2011 09:36:03 -0700 Received: by yxt33 with SMTP id 33so792158yxt.28 for ; Fri, 27 May 2011 09:36:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=BoE4DsgyZAeuQI1giil28dOLZ30T4QcYg1Mz5SmanGw=; b=gqKg0tLa3e6sHX34cpj5x8bUh1625bb4Wj6XCJ5Yrr9G3AEH1KGLGYujanbUh2Rz1v v1InlAFfVjH+mfCRaTXw== DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=bltusHWfLl17NvNwdZCX8Gzv53tDjNFcSHYmhZanPz484N8NdkB9ToRnjvpnPknXqi zDy72pq1todB8buRa4bA== MIME-Version: 1.0 Received: by 10.101.6.14 with SMTP id j14mr1599497ani.55.1306514163491; Fri, 27 May 2011 09:36:03 -0700 (PDT) Sender: evanm@google.com Received: by 10.101.1.17 with HTTP; Fri, 27 May 2011 09:36:03 -0700 (PDT) In-Reply-To: <20110527084924.GA52295@mech-cluster241.men.bris.ac.uk> References: <20110527084924.GA52295@mech-cluster241.men.bris.ac.uk> Date: Fri, 27 May 2011 09:36:03 -0700 X-Google-Sender-Auth: JvHarNgMcwHEpX_ujmKNR5ZL4bY Message-ID: From: Evan Martin To: Anton Shterenlikht Content-Type: text/plain; charset=ISO-8859-1 X-System-Of-Record: true Cc: chromium@freebsd.org Subject: Re: configure fails on ia64 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 May 2011 16:36:07 -0000 On Fri, May 27, 2011 at 1:49 AM, Anton Shterenlikht wrote: > I know it's not supposed to be built on ia64, > but perhaps this can help you debug chromium > on supported arches. FWIW, the v8 JavaScript engine only supports x86, x64, and ARM. From owner-freebsd-chromium@FreeBSD.ORG Fri May 27 18:58:14 2011 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B3BC410656A9 for ; Fri, 27 May 2011 18:58:14 +0000 (UTC) (envelope-from geo.liaskos@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 63DF98FC08 for ; Fri, 27 May 2011 18:58:14 +0000 (UTC) Received: by gxk28 with SMTP id 28so1070591gxk.13 for ; Fri, 27 May 2011 11:58:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=JzfYXRA89/nCugWnGn3ZnUFOZh51HRAuc9senkuMYW4=; b=vsW+Paf72i6olIjigIN2ZqVacI+Q9yyrdiEPzRo6hlyoa1fYTj0cVsGpVeskU5qxp+ dzIzbnhxRqgCV1PTDnLx3dwnLmaxruR7zH2k5VIaKdKHDBlDzEijgVGrd6EvVjhQyt+f s6VKmT6eADY0beAWyrNv77xRNwQBaUz4H6ATs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=fThMzV+xXbTPl0cTKw97TntSA8Zkp7vmpHwFoZCyxC6KSffAH3/IROcgvbdIBBNH9l Yp49j9l/z+I8hgwc70LaLqMhHHOeoP5UcstvUZTss/nq1vAvDNdx7tfGCq2oXrxdVZLP YdW48PJU87v4qxKB9vheg0omzErQVva0lwWgs= MIME-Version: 1.0 Received: by 10.101.46.19 with SMTP id y19mr1771515anj.19.1306522693574; Fri, 27 May 2011 11:58:13 -0700 (PDT) Received: by 10.100.32.14 with HTTP; Fri, 27 May 2011 11:58:13 -0700 (PDT) In-Reply-To: <20110526214442.GA20235@bsd.hu> References: <20110525195202.73393.qmail@wawanesa.iciti.ca> <20110526214442.GA20235@bsd.hu> Date: Fri, 27 May 2011 21:58:13 +0300 Message-ID: From: George Liaskos To: Robert Nagy Content-Type: text/plain; charset=UTF-8 Cc: chromium@freebsd.org, gtodd@iciti.ca Subject: Re: Any attempt to print with chromium causes sigsev X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 May 2011 18:58:14 -0000 Hello everyone There must be two different issues. In my main box i have gtk-2.24.4 / gtk-3.0.10 / glib-2.28.7 (testing gnome3) installed and i got this bug with the NULL printer object. A simple #ifdef change in browser_main_posix.cc, as i mention in my second email, is all we need to make print work under normal circumstances. I will commit it shortly. So, this must be a bug in gtk. I also found this : http://git.gnome.org/browse/gtk+/tree/NEWS?id=3.1.4 Bug: 647152 Assertion `GTK_IS_PRINTER (printer)' failed Robert thank you for the pointers, my next todo item is file_path_watcher. Chrome now uses a kqueue implementation for mac so we can use it almost unchanged, give it a try when you have time. Regards, George From owner-freebsd-chromium@FreeBSD.ORG Fri May 27 19:22:17 2011 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EE967106566B for ; Fri, 27 May 2011 19:22:17 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from mail-ew0-f54.google.com (mail-ew0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 701B78FC1B for ; Fri, 27 May 2011 19:22:17 +0000 (UTC) Received: by ewy1 with SMTP id 1so958921ewy.13 for ; Fri, 27 May 2011 12:22:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:message-id:date:from:organization :user-agent:mime-version:to:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=WbUEHGcOjJOBObAbYwIBYFAjXE/ZCpxepd7iKRdLnnM=; b=C/1KqzLCVynsOA5dqchk/GgOgB90UfggBZCwvHCFRx+2z8L4oPzK1lFlldqmLq8cvM 0d6hRrtGVfWFWVsw2pQ5D6JrXW2ybGJfvf40tVyJSof0QsJPXphBdj6kRI6kZgSeqs7L 1+CBw8lkdWLgAcPzGbzIKCCi7ron1vkJGuF1s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=nukWtYP3qusjsy3DMXVyiFrhBwswpRxS8nq6PiDowHGdFluSRacYGffVpCdiJUvUpj 87WPYFMTrFwkr6o9QJ7r0uaBB8lmNY7Yv1ZrbAqlwl9FwLjzdpx/hfnaK0XB2hRI5d/H tsJTAXU2FXOdcUNCee/W9ovQkMlqQ17lX9tJY= Received: by 10.213.4.196 with SMTP id 4mr19153ebs.88.1306524135941; Fri, 27 May 2011 12:22:15 -0700 (PDT) Received: from [192.168.1.14] (ip18-43-209-87.adsl2.static.versatel.nl [87.209.43.18]) by mx.google.com with ESMTPS id x46sm1454512eea.10.2011.05.27.12.22.13 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 27 May 2011 12:22:14 -0700 (PDT) Sender: =?UTF-8?Q?Ren=C3=A9_Ladan?= Message-ID: <4DDFF9E4.9000207@freebsd.org> Date: Fri, 27 May 2011 21:22:12 +0200 From: Rene Ladan Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; nl-NL; rv:1.9.2.17) Gecko/20110430 Thunderbird/3.1.10 MIME-Version: 1.0 To: freebsd-chromium@freebsd.org References: <20110527084924.GA52295@mech-cluster241.men.bris.ac.uk> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: configure fails on ia64 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 May 2011 19:22:18 -0000 Op 27-05-2011 18:36, Evan Martin schreef: > On Fri, May 27, 2011 at 1:49 AM, Anton Shterenlikht wrote: >> I know it's not supposed to be built on ia64, >> but perhaps this can help you debug chromium >> on supported arches. > > FWIW, the v8 JavaScript engine only supports x86, x64, and ARM. > Sounds like the port could use an ONLY_FOR_ARCH= line :/ René -- http://www.rene-ladan.nl:8080/ GPG fingerprint = ADBC ECCD EB5F A6B4 549F 600D 8C9E 647A E564 2BFC (subkeys.pgp.net)