On Mon, Sep 19, 2011 at 04:49:35PM -0700, David Thiel wrote:
> Hello,
>
> I noticed that the new Chromium actually fails to build if you have the
> protobuf port installed, as it tries to use the older installed version
> instead of the one that's bundled with Chromium. I confess I know very
>
On Wed, Dec 14, 2011 at 01:05:04AM +0100, Piotr Kubaj wrote:
> Hi. I can't upgrade chromium to version 16. I use FreeBSD 9.0-RC3, but
> the same error happens also on other computer with 9.0-PRERELEASE
> (which isn't suprising, considering
> that they are actually the same now), make showconfig giv
On Wed, Jun 06, 2012 at 07:34:05PM -0400, David P. Caldwell wrote:
> I built the latest Chromium 19 by building against the 9.0-RELEASE
> *packages*. I did not want to update all my ports and incur the
> various library problems that resulted the last time I tried that. I
> may try it next.
>
> I
Hi,
I keep having an annoying error message when upgrading chromium:
[226/226] Upgrading chromium from 27.0.1453.81 to 27.0.1453.110...Error in file
"/usr/local/share/applications/chromium-browser.desktop":
"/x-scheme-handler/https" is an invalid MIME type ("/x-scheme-handler/https"
contains an in
On Mon, Sep 09, 2013 at 08:57:49AM -0400, Adam McDougall wrote:
> On 09/09/13 08:31, Lapo Luchini wrote:
> > Hi!
> >
> > I'm wondering why the chrome process has the habit of crashing when I do
> > "pkg upgrade" (last time, it was a signal 11).
> >
> > I certainly expect something like this durin
On Fri, Sep 13, 2013 at 05:08:47PM -0400, Jung-uk Kim wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I thought r327048 would fix the build on HEAD but it didn't. So, I
> had to make a patch to fix various build problems with libc++. Please
> review/test the attached patch. It is a
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
On Sat, Jul 09, 2016 at 11:36:22AM -0700, Matthew Macy wrote:
>
> How much of Chromium's sandboxing code actually works on FreeBSD? On Linux it
> relies in part on user namespaces which appear to be a much more modular
> equivalent of jails usable by unprivileged processes.
People working on ch
Hello,
I might have been missing the obvious, but for me it seems all the chromium
related ports are wearing a useless USE_LDCONFIG, I can't find a reason why
it would be useful, I removed it from my system and everything seems to work
as expected.
I think it would be safe if you remove it from a
On Mon 03 Jun 02:05, Mario Marietto wrote:
> Hello.
>
> I'm trying to compile Chromium from the ports on my system (14.0 p6 with
> latest packages),but I found a bug.
Hello, the bug isn't in chromium, but in the way you are building it.
for some reasons you decided to build on your own with a p
Hello,
Before making the move, I prefer sending a mail here to check if someone is
working on a fix.
The iridium browser we do have in the ports is 201805 which is more than a year
old. meaning it is more than certainly full of security issues (not tracked as
such by the way).
As such I do plan
On Mon, Apr 12, 2021 at 07:54:53AM +1200, Jonathan Chen wrote:
> Hi,
>
> I recently updated to chromium-89.0.4389.114_1, and it now appears
> that the browser sync sign-in feature is not available anymore? Or did
> I miss something?
>
https://blog.chromium.org/2021/01/limiting-private-api-availa
Hello everyone,
chromium in FreeBSD is build without wayland support, however, I figure on linux
it supports both x11 and wayland, would it be possible to add
ozone_platform_wayland = true in build/config/ozone.gni
so on freebsd it can support both ?
Best regards,
Bapt
For sure I can test!
Best regards,
Bapt
24 sept. 2021 17:41:01 Matthias Wolf :
> Hi,
>
> On Fr., Sep 24 2021 at 09:38:28 +0200, Baptiste Daroussin
> wrote:
>> chromium in FreeBSD is build without wayland support, however, I figure on
>> linux
>> it supports bot
14 matches
Mail list logo