Fwd: [Action Required] Update on Google API usage in Chromium

FYI, not sure what it means exactly. -- Forwarded message - Van: The Google Chrome Team Date: vr 15 jan. 2021 19:07 Subject: [Action Required] Update on Google API usage in Chromium To: [image: Google logo] As part of Google’s efforts to improve user data security, we are

Re: Deprecating iridium browser and mark as forbidden

On 11-06-2019 13:48, Baptiste Daroussin wrote: > Hello, > > Before making the move, I prefer sending a mail here to check if someone is > working on a fix. I just looked at the WWW site from its pkg-descr and it is dead (https://iridium-browser.de). > > The iridium browser we do have in the

Re: chromium 60.0.3112.101 breaks extensions

2017-08-25 11:36 GMT+02:00 Lars Engels : > On Fri, Aug 25, 2017 at 09:29:37AM +1200, Jonathan Chen wrote: > > Hi, > > > > Just a heads-up for those planning to install 60.0.3112.101, any > > extensions installed will not work correctly anymore. eg: Google Mail > > Checker. >

Re: Fw: latest www/chromium: no sound

2016-11-30 9:50 GMT+01:00 Emanuel Haupt : > Sounds reasonable to me. This would provide packages with ALSA enabled > and therefore fixing the sound issue for users using packages. > > Mind if I turn the option on? > Fine with me, our development repositories have some code to

Re: Fwd: [gliaskos/freebsd-chromium] Stable channel update (#57)

On 01-06-16 15:14, René Ladan wrote: > On 31-05-16 17:21, René Ladan wrote: >> Hi, >> >> Timothy Vaccarelli ("LeFroid") updated Chromium to version 51.0.2704.63, >> but it is not production ready yet. I made some changes on top of this >> commit in the g

Re: Fwd: [gliaskos/freebsd-chromium] Stable channel update (#57)

On 31-05-16 17:21, René Ladan wrote: > Hi, > > Timothy Vaccarelli ("LeFroid") updated Chromium to version 51.0.2704.63, > but it is not production ready yet. I made some changes on top of this > commit in the gliaskos/freebsd-chromium repository (mostly port side fix

Fwd: [gliaskos/freebsd-chromium] Stable channel update (#57)

Hi, Timothy Vaccarelli ("LeFroid") updated Chromium to version 51.0.2704.63, but it is not production ready yet. I made some changes on top of this commit in the gliaskos/freebsd-chromium repository (mostly port side fixes). René Forwarded Message From: Timothy Vaccarelli

Re: current chromium version in ports tree giving vulnerabilities warnings

Op 23 jan. 2016 00:39 schreef "Phil Eaton" : > > Hi, > > I just tried to update chromium but the build is failing with a number of > vulnerabilities. I understand that I can build and ignore these > vulnerabilities, but I wanted to report this anyway. Here is the result of

Re: [package - 93i386-quarterly][www/chromium] Failed for chromium-47.0.2526.106 in build

2015-12-22 21:53 GMT+01:00 Christoph Moench-Tegeder : > ## pkg-fall...@freebsd.org (pkg-fall...@freebsd.org): > > Subject: Re: [package - 93i386-quarterly][www/chromium] Failed for >> ./../third_party/libyuv/source/row_gcc.cc:1686:4: error: 'asm' operand has >> impossible

Re: [package - 93i386-quarterly][www/chromium] Failed for chromium-47.0.2526.73 in build

2015-12-08 8:53 GMT+01:00 : > You are receiving this mail as a port that you maintain > is failing to build on the FreeBSD package build server. > Please investigate the failure and submit a PR to fix > build. > > Maintainer: chrom...@freebsd.org > Last committer:

Re: Document new vulnerabilities in www/chromium < 45.0.2454.85

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 09/02/2015 12:21, Carlos J Puga Medina wrote: > Current www/chromium is marked as vulnerable on Google Chrome > website[0]. Committed, with a few line rewraps and addition of variants specific to PC-BSD. Thanks, René > > --- vuln.xml.orig

Re: Crash when right mouse button click on download file

On 07/06/2015 23:38, Yuri wrote: Crash is on 10.1 when some file is being downloaded (download tab in the bottom with progress indicator). Right mouse button click=SEGV. 43.0.2357.130 (64-bit) I can reproduce this with 43.0.2357.132 (64-bit, PCBSD-11-July) René

Re: gyp with BSD make?

2015-05-06 14:17 GMT+02:00 Marcin Cieslak sa...@saper.info: Hello, Has anybody tried or was there interest to modify gyp to generate BSDmakefiles that would automatically get our CC, CXX and other flags? That would be quite an endavour I think and make our Chromium less compatible with

Re: Cannot build latest Chromium

Hi, 2015-04-28 22:08 GMT+02:00 Torfinn Ingolfsen tin...@gmail.com: On Tue, Apr 28, 2015 at 8:16 PM, René Ladan r...@freebsd.org wrote: looking into this, you didn't seem to have removed files/patch-v8__src__debug.cc My fault, I just downloaded the raw files and applied them without

Re: Cannot build latest Chromium

2015-04-28 20:12 GMT+02:00 Torfinn Ingolfsen tin...@gmail.com: Hello, On Tue, Apr 28, 2015 at 7:56 PM, René Ladan r...@freebsd.org wrote: Hi, 2015-04-28 19:51 GMT+02:00 Torfinn Ingolfsen tin...@gmail.com: FWIW, the same problem seen on tingo@kg-core1$ uname -a FreeBSD kg-core1.kg4.no 9.3

Re: Cannot build latest Chromium

Hi, 2015-04-28 19:51 GMT+02:00 Torfinn Ingolfsen tin...@gmail.com: FWIW, the same problem seen on tingo@kg-core1$ uname -a FreeBSD kg-core1.kg4.no 9.3-STABLE FreeBSD 9.3-STABLE #0 r273918: Fri Oct 31 22:52:44 CET 2014 r...@kg-core1.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 can you try

Chromium 40 ...

Hi, I committed a bug fix update to www/chromium. However, if anyone is interested in getting chromium into the ports tree, it's best to start patching the beta release *now*. See my other email for why and how. Regards, René ___

backing down on Chromium ...

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello all, after already four years I decided to back down somewhat on Chromium. This is not an overnight decision, the feeling started creeping in several months ago. One reason is that maintaining Chromium all the way on FreeBSD would seriously

Re: Chrome 39.0.2171.65 starts with black screen

On 21-11-2014 06:55, Yuri wrote: Completely unusable. Previous version 38.0.2125.122 worked fine. System uses NVidia binary driver, if this matters. It runs fine here, also with the binary NVidia driver (version 340.24_1). What is your FreeBSD version/architecture? (here 10.0 amd64). One

Re: Still segfault at start

On 05-11-2014 12:47, Tomek wrote: Hi, 4 listopada 2014 15:18 - René Ladan r...@freebsd.org:: Hm, maybe a 32 vs 64 bit issue. I'll try conditionally zeroing out the result value in libexecinfo as you described, but I only have 32-bits VMs to test with (my physical CPU misses required VT-x

Re: Still segfault at start

On 03-11-2014 19:39, Tomek wrote: Hi, 2 listopada 2014 14:06 - René Ladan r...@freebsd.org:: On 02-11-2014 11:05, l...@lena.kiev.ua wrote: 8.4 i386, one more newer version 38.0.2125.111 from pkg.FreeBSD.org/freebsd:8:x86:32 - at start this time a window frame didn't appear, again segfault

Re: Still segfault at start

On 04-11-2014 15:08, Tomek wrote: Hi, Adding -fno-omit-frame-pointer to www/chromium/Makefile gives a build error in poudriere: ../../third_party/ffmpeg/libavcodec/x86/mpegaudiodsp.c:84:5: error: 'asm' operand has impossible constraints __asm__ volatile( ^ or did you add this flag to

Re: Still segfault at start

On 03-11-2014 19:39, Tomek wrote: Hi, 2 listopada 2014 14:06 - René Ladan r...@freebsd.org:: On 02-11-2014 11:05, l...@lena.kiev.ua wrote: 8.4 i386, one more newer version 38.0.2125.111 from pkg.FreeBSD.org/freebsd:8:x86:32 - at start this time a window frame didn't appear, again segfault

Re: Still segfault at start

On 02-11-2014 11:05, l...@lena.kiev.ua wrote: 8.4 i386, one more newer version 38.0.2125.111 from pkg.FreeBSD.org/freebsd:8:x86:32 - at start this time a window frame didn't appear, again segfault: (deleted ~/.config/chromium, ~/.cache/chromium, ~/.pki) ~ $

Re: [Bug 193725] chromium-37 Latin accent keys are not working

://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193725 That's also fine. Tanks to both, tomek for the patch and René for the continuous work on the chromium port! Miguel C. On October 17, 2014 9:09:42 PM WEST, René Ladan r.c.la...@gmail.com wrote: Op 17 okt. 2014 21:26 schreef Miguel Clara miguelmcl

Re: chromium 38 up for testing

2014-10-06 10:08 GMT+02:00 Tomek to...@apostata.org: Hello, I just committed a (seemingly) working version of chromium 38.0.2125.101 on to the github repository, so feel free to try it out. I still need to do a clean poudriere build test. Compiles and works Ok. It does seem to have

chromium 38 up for testing

Hi, I just committed a (seemingly) working version of chromium 38.0.2125.101 on to the github repository, so feel free to try it out. I still need to do a clean poudriere build test. See https://github.com/gliaskos/freebsd-chromium (beta branch) It does seem to have the double-windowbar bug

Re: chromium 37 up for testing (and polishing)

2014-08-26 15:36 GMT+02:00 Carlos Jacobo Puga Medina c...@fbsd.es: On Sun, 24 Aug 2014 13:25:15 +0200 Carlos Jacobo Puga Medina c...@fbsd.es wrote: On Sun, 24 Aug 2014 13:17:00 +0200 Carlos Jacobo Puga Medina c...@fbsd.es wrote: On Sun, 24 Aug 2014 11:56:56 +0200 Carlos Jacobo Puga

Re: chromium 36 almost there ...

2014-08-15 17:24 GMT+02:00 Shawn Webb latt...@gmail.com: On Aug 15, 2014 06:57 AM -0700, Cy Schubert wrote: In message 53e941e9.1030...@freebsd.org, =?UTF-8?B?UmVuw6kgTGFkYW4=?= writes: Hi, with some help from Pawe?? Hajdan, who ports Chromium to Gentoo, I managed to get Chromium

Re: chromium 36 on FreeBSD 9?

Op 15 aug. 2014 21:59 schreef Carlos Jacobo Puga Medina c...@fbsd.es: Hi, The latest update doesn't seem to build on 9.2 Last few lines of build log: Updating projects from gyp files... Package libusb-1.0 was not found in the pkg-config search path. Perhaps you should add the

Re: chromium 36 on FreeBSD 9?

2014-08-16 0:12 GMT+02:00 Gary Palmer gpal...@freebsd.org: On Fri, Aug 15, 2014 at 11:18:24PM +0200, Ren?? Ladan wrote: Op 15 aug. 2014 22:37 schreef Carlos Jacobo Puga Medina c...@fbsd.es: On Fri, 15 Aug 2014 22:25:24 +0200 Ren?? Ladan r.c.la...@gmail.com wrote: Op 15 aug.

Re: chromium 36 almost there ...

2014-08-13 0:56 GMT+02:00 René Ladan r...@freebsd.org: Quick FYI (almost 1 am here..), I'm typing this from Chromium 36 on FreeBSD :) Things left to do: - Fix staging Done - Fix build with clang 3.4 (e.g. in my 11i386 vm) Will look into, but this might be caused by having an unclean

chromium 36 almost there ...

Hi, with some help from Paweł Hajdan, who ports Chromium to Gentoo, I managed to get Chromium building except for some undefined symbols during the final link step which are likely due to FreeBSD being #ifdef'd out. I will look into that tomorrow. The good news is that the library collisions

Re: porting Chromium 36 to FreeBSD

2014-08-04 23:15 GMT+02:00 Carlos Jacobo Puga Medina c...@fbsd.es: Hi rené, Currently I'm building chromium-36.0.1985.125. I'll report back when I get good results. I hope we can get it ready to commit it pretty soon ;) It's not working yet, but anway I updated the github port based on

Re: building chromium with poudriere fails

2014-08-05 10:54 GMT+02:00 Wolfgang Riegler wolfgang.rieg...@gmx.de: Hi, building chromium with poudriere fails with: ImportError: This platform lacks a functioning sem_open implementation, therefore, the required synchronization primitives needed will not function, see issue 3770. Ah,

Re: Chromium 36 in progress

2014-07-19 10:58 GMT+02:00 René Ladan r...@freebsd.org: On 07/19/2014 00:30, Lawrence K. Chen, P.Eng. wrote: Of course digging deeper...I do see that the function does exist...and should exist. Keep typing png_read_... instead of png_set_... when I was grepping for some reason

Re: Chromium 36 in progress

2014-07-18 13:08 GMT+02:00 Carlos Jacobo Puga Medina c...@fbsd.es: Hi René, Can you show the build log? I've free time to test it and lend a helping hand. Yes, here it is (from a slightly older beta version on 10.0-amd64 with the FreeBSD png-1.5.18 package installed): [13/1486] LINK chrome

Re: Chromium 36 in progress

the png_set_strip_16() in the Chromium code gets confused with png_set_chop_16(), because the chrome binary does link to the external libpng? Regards, René On 07/18/14 06:34, René Ladan wrote: 2014-07-18 13:08 GMT+02:00 Carlos Jacobo Puga Medina c...@fbsd.es: Hi René, Can you show the build log? I've free

Fwd: Chromium Selenium webdriver

Hi, not much time for this myself currently, feel free... René Original Message

Re: Document new vulnerabilities in www/chromium 35.0.1916.153

2014-06-11 2:29 GMT+02:00 c...@fbsd.es c...@fbsd.es c...@fbsd.es: Current www/chromium is marked as vulnerable on Google Chrome website [1]. So I added a note to security/vuxml/vuln.xml Thanks for the write-up, I'll add it to the list (if nobody else is faster ;) ) Rene -- vuxml

Re: libffmpeg chromium crashes due to unaligned SSE accesses

Hi, you mean that the patch I made out of Dimitrys patch works fine? René On 05/20/2014 18:28, Adrian Chadd wrote: Hi, So whose arm should I twist to get this stuff committed to both the libffmpeg and chromium ports? -a On 12 May 2014 15:08, Dimitry Andric d...@freebsd.org wrote:

Re: Chromium 34.0.1847.132 Segmentation fault

On 05/16/2014 21:23, l...@lena.kiev.ua wrote: since I've updated Chromium to 34.0.1847.132, the program won't run anymore: Segmentation fault (core dumped). I run FreeBSD 9.3-PRERELEASE on amd64. Chromium has been compiled by gcc. Same on 8.4-RELEASE i386: 33.0.1750.152_1 works,

Re: libffmpeg chromium crashes due to unaligned SSE accesses

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 [continue top-posting ...] Can you try the attached patch (i.e. put in files/ and rebuild chromium) ? % patch files/patch-third_party__ffmpeg__chromium* % rm work/.configure_done* work/.build_done* work/.stage_done* % make The patch should be

Re: [REL - 84i386-default][www/chromium] Failed for chromium-34.0.1847.132 in build

On 05/12/2014 05:24, pkg-fallout-buil...@freebsd.org wrote: You are receiving this mail as a port that you maintain is failing to build on the FreeBSD package build server. Please investigate the failure and submit a PR to fix build. Maintainer: chrom...@freebsd.org Last committer:

Re: lost chromium - chromium core dumps on stable/9

On 05/11/2014 08:44, Luigi Rizzo wrote: hi, i recently attempted to upgrade chromium from 31.x to 34.x on my FreeBSD stable/9, through a svn update of the entire ports tree, followed by a portupgrade -Rf www/chromium After that it seems i am no longer able to run chrome on that machine,

Re: chromium 34.0.1847.116 gives SIGABRT at start

SHA256 (chromium-33-34.diff) = 3a1a1859cb776ece867f133c92c441da48aef60df6fa67c2769d311fd35b86b2 SIZE = 212616 René On 04/23/2014 15:54, René Ladan wrote: 2014-04-22 21:30 GMT+02:00 Robert Nagy rob...@openbsd.org mailto:rob...@openbsd.org: Hey, Try this: build/common.gypi

Re: chromium 34.0.1847.116 gives SIGABRT at start

if that gives a clue. René On (2014-04-22 21:21), René Ladan wrote: Hi, I ported chromium 34.0.1847.116 to FreeBSD (patches at [1]) but it currently gives a SIGABRT when starting it without any visible output. Building a debug version does not make a difference either

chromium 34.0.1847.116 gives SIGABRT at start

Hi, I ported chromium 34.0.1847.116 to FreeBSD (patches at [1]) but it currently gives a SIGABRT when starting it without any visible output. Building a debug version does not make a difference either. This is on FreeBSD 10.0-STABLE, GENERIC amd64 kernel. Does anyone see something obviously

Chromium 34

Hi, there is a patch for Chromium 34.0.1847.116 ready [1] and while it builds and packages fine it immediately dumps core when starting it. When ran directly from the ports work directory, it starts but extensions and tabs (randomly) crash. I'll try to finish the debug build tonight (laptop ran

Status report

Hi, attached is the status report for 2014Q1, already reviewed by some people. Regards, René ___ freebsd-chromium@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-chromium To unsubscribe, send any mail to

Re: Geolocation seems to have stopped working

2014-03-18 21:56 GMT+01:00 Lawrence K. Chen, P.Eng. lkc...@ksu.edu: Think it last worked in 33.0.1750.146_1. Still works for me on 33.0.1750.152 on FreeBSD 10.0-amd64 using this test site: http://html5demos.com/geo René ___

Re: Geolocation seems to have stopped working

Weird, nothing in the Chromium port changed between these two Chromium versions (like API keys or patches). René 2014-03-18 22:41 GMT+01:00 Lawrence K. Chen, P.Eng. lkc...@ksu.edu: Failing for me on 33.0.1750.152 on FreeBSD 9.2-amd64 On 03/18/14 16:24, René Ladan wrote: 2014-03-18 21:56

Re: Aura and Ash

2014-03-14 14:14 GMT+01:00 Bruno Lauzé brunola...@msn.com: I gave a try to compile Chromium 35 latest release with Aura. After a lot of patches, it compiles, still everything crash after... I expected it. The goal was to try to up to where we can go into the Aura part where Google announced

more thoughts on porting Chromium to FreeBSD

Hi, [this is an updated rewrite of an earlier private mail] some more thoughts and ideas I gathered while porting Chromium to FreeBSD: - FreeBSD seems to piggy-back on Linux too much because ninja will build *_linux files on FreeBSD which might or might not be useful. I guess that ideally there

Re: [chromium-packagers] more thoughts on porting Chromium to FreeBSD

On 03/10/2014 11:16, Torne (Richard Coles) wrote: On 10 March 2014 09:20, René Ladan r...@freebsd.org mailto:r...@freebsd.org wrote: Hi, [this is an updated rewrite of an earlier private mail] some more thoughts and ideas I gathered while porting Chromium to FreeBSD

Re: [chromium-packagers] more thoughts on porting Chromium to FreeBSD

On 03/10/2014 18:22, Lei Zhang wrote: On Mon, Mar 10, 2014 at 9:59 AM, Torne (Richard Coles) to...@chromium.org wrote: On 10 March 2014 16:13, René Ladan r...@freebsd.org wrote: Hm, there does not seem to be a hard rule here. Somehow having dedicated _freebsd files looks cleaner but that does

www/chromium vulnerable

Hi, I overlooked that www/chromium (currently 33.0.1750.117) is marked as vulnerable on Googles website [1] since Monday, and should be updated to 33.0.1750.146. If anyone can add a note to security/vuxml/vuln.xml before tonight (SSH blocked at office :( ), that would be nice. [1]

Re: ports/186352: www/chromium 32.0.1700.102 hangs and becomes unresponsive.

The following reply was made to PR ports/186352; it has been noted by GNATS. From: =?ISO-8859-1?Q?Ren=E9_Ladan?= r...@freebsd.org To: bug-follo...@freebsd.org, j...@alisa.org Cc: Subject: Re: ports/186352: www/chromium 32.0.1700.102 hangs and becomes unresponsive. Date: Tue, 25 Feb 2014

Re: Patch for Chromium settings crash

On 02/25/2014 04:10, John Carr wrote: If I select Settings then Exit from the menu at top right, chrome crashes every time. Same with History instead of Settings. I am running FreeBSD 10.0 on amd64, chromium package 32.0.1700.107. I started X with xinit, basically just starting a few

Re: ports/186082: www/chromium dumps core when closing settings page

The following reply was made to PR ports/186082; it has been noted by GNATS. From: =?ISO-8859-1?Q?Ren=E9_Ladan?= r...@freebsd.org To: bug-follo...@freebsd.org, marko.cu...@mimar.rs Cc: Subject: Re: ports/186082: www/chromium dumps core when closing settings page Date: Tue, 25 Feb 2014 20:22:50

Re: ports/186082: www/chromium dumps core when closing settings page

On 02/25/2014 21:38, Thomas Hoffmann wrote: On Tue, Feb 25, 2014 at 2:30 PM, René Ladan r...@freebsd.org mailto:r...@freebsd.org wrote: The following reply was made to PR ports/186082; it has been noted by GNATS. From: =?ISO-8859-1?Q?Ren=E9_Ladan?= r...@freebsd.org mailto:r

Re: Status of sandbox/Capsicum support in the Chromium FreeBSD port

2014-01-30 Khilan Gudka khilan.gu...@cl.cam.ac.uk: Dear Chromium port maintainer(s) I was wondering what the current status was with regards to sandboxing renderer processes. In particular, now that Capsicum comes as standard in FreeBSD, I'm interested in running Chromium with Capsicum

Re: FreeBSD Port: www/chromium

On 01/23/2014 20:54, Mike Jakubik wrote: Hello, I just updated to the latest version of chromium, now as soon as I attempt any operation chromium crashes with the following error. [77827:318843904:0123/145145:ERROR:form_data.cc(108)] Bad pickle of FormData, no version present

Re: chromium-32.0.1700.77 unusable on 8.4 i386

2014/1/18 l...@lena.kiev.ua: On 8.4-RELEASE i386, not pkgng: pkgng or pkg_* should not matter in this case ;) chromium-30.0.1599.101 built with gcc46 works OK even when significant part of memory (1467 MB RAM + 768 MB swap) is occupied with Firefox. Ok ... Build of both

Re: 32.0.1700.77 released

2014/1/15 René Ladan r...@freebsd.org: 2014/1/15 René Ladan r...@freebsd.org: Hi, A new stable version for chromium, 32.0.1700.77 , was released today. If But the distribution files are not yet downloadable from Google :( They now are: http://commondatastorage.googleapis.com/chromium

32.0.1700.77 released

Hi, A new stable version for chromium, 32.0.1700.77 , was released today. If anyone wants to update the vuxml, reroll the distribution file, and update the port (separately please) before tonight cet then feel free. Patches for the port are in George's repository at

Re: 32.0.1700.77 released

2014/1/15 René Ladan r...@freebsd.org: Hi, A new stable version for chromium, 32.0.1700.77 , was released today. If But the distribution files are not yet downloadable from Google :( anyone wants to update the vuxml, reroll the distribution file, and update the port (separately please

Re: 31

On 12/10/13 20:36, l...@lena.kiev.ua wrote: From: Ren? Ladan r...@freebsd.org On 10-12-2013 10:16, l...@lena.kiev.ua wrote: Mark Atkinson atkin...@gmail.com wrote: On 12/02/2013 22:50, Andrew Johnson dae...@optushome.com.au wrote: I made the mistake of allowing chromium to be updated to

Re: 31

On 10-12-2013 10:16, l...@lena.kiev.ua wrote: Mark Atkinson atkin...@gmail.com wrote: On 12/02/2013 22:50, Andrew Johnson dae...@optushome.com.au wrote: I made the mistake of allowing chromium to be updated to 31.0.1650.57_1 during a portupgrade... Has anyone yet betten the 'Aw snap' and

Re: Problem installing chromium-31.0.1650.57

2013/11/27 Владимир Тимофиев elimelech...@gmail.com: When installing chromium-31.0.1650.57 on Freebsd FreeBSD 8.4 (KDE 4.10.5) the following error pops up: CODE: SELECT ALL Can you tell me which architecture this is and which options you selected? What do you mean with CODE: SELECT ALL ? I

Re: ports/175369: www/chromium: Chromimum Desktop Integration doesn#39;t open URLs

The following reply was made to PR ports/175369; it has been noted by GNATS. From: =?ISO-8859-1?Q?Ren=E9_Ladan?= r...@freebsd.org To: bug-follo...@freebsd.org, beas...@tardisi.com, George Liaskos geo.lias...@gmail.com Cc: Subject: Re: ports/175369: www/chromium: Chromimum Desktop

Re: Chromium/FreeBSD 11, no content?

On 14-10-2013 04:34, Larry Rosenman wrote: and gcc built chrome segfaults immediately :( Some things to check: - What are the other options set to? - What is your architecture? - Do you have any plugins installed? - What happens if you move ~/.config/chromium and ~/.cache/chromium out of the

Re: chromium-30.0.1599.66 issue

Hm, I can play youtube videos with flash just fine with the default options in my 10.0-i386 virtual machine... This is with chromium 30.0.1599.69 (only CODECS, GCONF, and TEST on) and linux-f10-flashplugin 11.2r202.310 I only have system clang installed at version 3.3 (svn 183502) René

Re: chromium-28.0.1500.95 to 29.0.1547.57

On 30-08-2013 13:41, Владимир Тимофиев wrote: root@f3ja:/usr/ports/www/chromium # make reinstall clean === Building for chromium-29.0.1547.57 [...] [4/10877] CXX obj/base/base.file_util_posix.o FAILED: /usr/local/bin/clang++ -MMD -MF obj/base/base.file_util_posix.o.d -DANGLE_DX11

Re: 29.0.1547.57 build fails on 9.2-RC2 i386

On 27-08-2013 12:35, John Marshall wrote: On 26/08/2013 22:01, René Ladan wrote: On 26-08-2013 13:49, John Marshall wrote: Chromium 29.0.1547.57 doesn't want to build for me on 9.2-RC2 i386 [11637/11992] CXX obj/net/dns/net.dns_session.o FAILED: clang++ obj/net/dns/net.dns_session.o

Re: 29.0.1547.57 build fails on 9.2-RC2 i386

On 26-08-2013 13:49, John Marshall wrote: Chromium 29.0.1547.57 doesn't want to build for me on 9.2-RC2 i386 FreeBSD 9.2-RC2 r254395: Fri Aug 16 17:28:53 AEST 2013 ... i386 ports tree: r325368 This is an old Pentium 4 - no HTT available, so no scope for MAKE_JOBS. Earlier releases of

Re: chromium (unclickable links) still not fixed

On 31-07-2013 13:57, George Liaskos wrote: https://github.com/gliaskos/freebsd-chromium/blob/master/www/chromium/Makefile#L137 This is wrong, even if clang port is installed CC points /usr/bin/clang. It's obviously working only for releases that don't have clang. My bad, can you try

Re: chromium (unclickable links) still not fixed

On 31-07-2013 15:14, Jan Henrik Sylvester wrote: On 07/31/2013 15:07, René Ladan wrote: On 31-07-2013 13:57, George Liaskos wrote: https://github.com/gliaskos/freebsd-chromium/blob/master/www/chromium/Makefile#L137 This is wrong, even if clang port is installed CC points /usr/bin/clang. It's

Re: compiling Chromium 28 with clang33 fixes unclickable links

On 28-07-2013 02:20, Adam McDougall wrote: On Sat, Jul 27, 2013 at 01:04:01PM +0100, Brad Karp wrote: Given hope by Tony's experience, I tried building Chromium 28 on my 9.1-RELEASE amd64 box with clang33 instead of the default 9.1R clang (3.1). Success here, too: building with

Re: www/chromium

On 01-07-2013 17:28, Sergey A. Osokin wrote: Hi, I had installed new shiny FreeBSD 9.1, upgraded to 9.1-STABLE. I installed latest version of www/chromium from ports tree. When I started chrome and tried to view typical and simple page at http://www.ru/, it shows nothing, just empty page.

using API keys in the FreeBSD Chromium port

Hi, the patch at [1] enables the use of FreeBSD API keys which allows things like Google Sync to work. However [3] states that these keys are not for distribution purposes and must not be shared with other users. There has been some discussion about this on how to deal with this for source-based

Re: Upstreaming the patches in files/?

On 19-05-2013 17:19, Raphael Kubo da Costa wrote: René Ladan r...@freebsd.org writes: On 19-05-2013 16:25, Raphael Kubo da Costa wrote: Raphael Kubo da Costa rak...@freebsd.org writes: Hi there, I've noticed that www/chromium/files/ contains a fairy large amount of files these days. Many

Re: [CFT] chromium 27 (updated)

On 16-05-2013 10:27, Volodymyr Kostyrko wrote: 14.05.2013 19:52, René Ladan: Hi, I have uploaded a new version of the patch at ftp://rene-ladan.nl/pub/freebsd/chromium-27.diff SHA256 = acc3416b7a3271143b4b6c1fa9d094cd6a24774f9c225ab7003bd289799e1722 This updates chromium

[CFT] chromium 27 (updated)

Hi, I have uploaded a new version of the patch at ftp://rene-ladan.nl/pub/freebsd/chromium-27.diff SHA256 = acc3416b7a3271143b4b6c1fa9d094cd6a24774f9c225ab7003bd289799e1722 This updates chromium to 27.0.1453.81 and incorporates the npapi (flash) and some other fixes. I tested it to compile

geolocation (was: Re: chromium v25.0.1364.97 problems)

On 02-03-2013 14:42, J.R. Oldroyd wrote: On Tue, 26 Feb 2013 18:11:00 -0500 (EST) Lawrence K. Chen, P.Eng. lkc...@ksu.edu wrote: Also Currently seems to no longer be able to figure out my location anymore. Anybody else seeing this? Yes. I took a look at the wifi geolocation code, and

Fwd: chromium-20.0.1132.57 patch failure

Oops, I did wrong and committed something that appearently doesn't work. But I'll be unavailable for a while, can someone take a look? -- Forwarded message -- From: Jan Henrik Sylvester m...@janh.de Date: 2012/7/12 Subject: chromium-20.0.1132.57 patch failure To: René Ladan r

Re: Chromium build fails on Current (r233121)

2012/4/2 Xin Li delp...@delphij.net: On 03/18/12 13:11, Lars Engels wrote: Build of Chromium 17.0.963.79 fails to build on r233121, amd64: CXX(target) out/Release/obj.target/webkit_gpu/webkit/gpu/webgraphicscontext3d_in_process_impl.o LINK(host) out/Release/protoc AR(host)