From owner-freebsd-chromium@FreeBSD.ORG  Mon Feb  2 02:33:40 2015
Return-Path: <owner-freebsd-chromium@FreeBSD.ORG>
Delivered-To: chromium@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 92818D52;
 Mon,  2 Feb 2015 02:33:40 +0000 (UTC)
Received: from mail-oi0-x233.google.com (mail-oi0-x233.google.com
 [IPv6:2607:f8b0:4003:c06::233])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 54607889;
 Mon,  2 Feb 2015 02:33:40 +0000 (UTC)
Received: by mail-oi0-f51.google.com with SMTP id x69so42331296oia.10;
 Sun, 01 Feb 2015 18:33:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:from:date:message-id:subject:to
 :cc:content-type;
 bh=O+40LS4gW57ImJJsRe1rszLsBpFuixzbD51F26GnOho=;
 b=YcuJEUiAHpKd+pfgHCGiIKDX3d8KxBse1V0Q+Rx/nK/pysxbfCR9JUpEGyT7U+vyHs
 8duhhgOvrvUWoGEcFyFQp4gNeGEff09Xz3WJPMT3fW0iyQ9pNpwIMmab0OQWXKaubeEF
 mSAZIbMTVRZVLaWrBfxrf6bSMzRevM9i6fpVPIpey80iZb30AOn1KJXE/SzRmpvDqWzl
 qOKWp3mPtiPigPQhPXmdDtqYxSfQLLztI248p9pdcoiPws6d9jZc5YZ1AkYgSj0qqqJr
 5IzmNwt2PTw/YcOMOweP3EP3L6y+Rwlds00t33Gxo6fexhIbHeWzvb+FqH3pIeE4L9dl
 EeuA==
X-Received: by 10.202.102.207 with SMTP id m76mr10147654oik.127.1422844419652; 
 Sun, 01 Feb 2015 18:33:39 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.3.166 with HTTP; Sun, 1 Feb 2015 18:33:18 -0800 (PST)
In-Reply-To: <20150120223841.GF13897@ivaldir.etoilebsd.net>
References: <20150119113424.GQ67556@e-new.0x20.net>
 <20150120183031.GW67556@e-new.0x20.net>
 <20150120223841.GF13897@ivaldir.etoilebsd.net>
From: Fervent Dissent <walkerindarkness@gmail.com>
Date: Mon, 2 Feb 2015 10:33:18 +0800
Message-ID: <CALpPS7NirwK186VPX7nu2ZwMWiBAYUEBfZWgHNjGhS--B3nr_A@mail.gmail.com>
Subject: Re: libpdf.so not working
To: Baptiste Daroussin <bapt@freebsd.org>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1
Cc: chromium@freebsd.org
X-BeenThere: freebsd-chromium@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: FreeBSD-specific Chromium issues <freebsd-chromium.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-chromium>, 
 <mailto:freebsd-chromium-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-chromium/>
List-Post: <mailto:freebsd-chromium@freebsd.org>
List-Help: <mailto:freebsd-chromium-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-chromium>, 
 <mailto:freebsd-chromium-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Feb 2015 02:33:40 -0000

I'm not a programmer, but I have support this effort in the past. Would you
consider continuing if paid? I'm not rich, but I bought 2 subscriptions
years ago when chromium was first ported to FreeBSD.

On Wed, Jan 21, 2015 at 6:38 AM, Baptiste Daroussin <bapt@freebsd.org>
wrote:

> On Tue, Jan 20, 2015 at 07:30:31PM +0100, Lars Engels wrote:
> > On Mon, Jan 19, 2015 at 12:34:24PM +0100, Lars Engels wrote:
> > > Since the last update libpdf.so is included in the build. The plugin is
> > > displayed in chrome://plugins, but when I open a PDF file I only see a
> > > white page. Is there something to configure?
> > >
> > > I'm running FreeBSD HEAD amd64 with yesterday's port version.
> >
> > Nevermind. I reset all settings in chrome://flags and it's working now.
> >
> > Woohoo, PDF in chromium! At last! :)
> >
> Profit because it seems this chromium version will be one of the last,
> noone
> seems to be working on version 40 of chromium (I would love to be wrong
> here)
>
> Best regards,
> Bapt
>