http://permalink.gmane.org/gmane.os.freebsd.chromium hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.os.freebsd.chromium/687 <pre>Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/chromium&lt; at &gt;freebsd.org.html Port | Current version | New version ------------------------------------------------+-----------------+------------ www/chromium | 27.0.1453.110 | 27.0.1453.116 ------------------------------------------------+-----------------+------------ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://por</pre> portscout< at >portscout.freebsd.org 2013-06-19T13:04:22 http://permalink.gmane.org/gmane.os.freebsd.chromium/686 <pre>Hi all. I have the same problem, but it was in earlier versions also. Now I have FreeBSD 8.4-PRERELEASE and Chromium 27.0.1453.110 (202711). The same problem is on WinXP and Chromium 27.0.1453.110 m Gooogle help doesn`t help.... With best regards, Dmitry S. Nikolaev phone: +7 (499) 678 8007 [ext. 6003] fax: +7 (499) 678 8007 [ext. 7777] www: http://www.mega-net.ru mail: dnikolaev&lt; at &gt;mega-net.ru On 18.06.2013 01:48, Lawrence K. Chen, P.Eng. wrote: </pre> Dmitry S. Nikolaev 2013-06-18T03:46:40 http://permalink.gmane.org/gmane.os.freebsd.chromium/685 <pre> ----- Original Message ----- So, lastest chromium....had been working okay on the most part, but now sync is broken...and I don't know why? How do you fix this problem? I sign in...it and just takes me back to the sign in page, clear cookies, cache, everything....keeps looping. Can sign into other parts of google fine.... Lawrence </pre> Lawrence K. Chen, P.Eng. 2013-06-17T21:48:47 http://permalink.gmane.org/gmane.os.freebsd.chromium/684 <pre>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 -------------------------------------------------------------------------------- f ports/175369 chromium www/chromium: Chromimum Desktop Integration doesn't op o ports/165635 chromium www/chromium: 17.0.963.56: proxy isn't read by chrome f ports/165634 chromium www/chromium : 17.0.963.56 doesn't show physical print 3 problems total. </pre> FreeBSD bugmaster 2013-06-17T11:06:22 http://permalink.gmane.org/gmane.os.freebsd.chromium/683 <pre>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 -------------------------------------------------------------------------------- f ports/175369 chromium www/chromium: Chromimum Desktop Integration doesn't op o ports/165635 chromium www/chromium: 17.0.963.56: proxy isn't read by chrome f ports/165634 chromium www/chromium : 17.0.963.56 doesn't show physical print 3 problems total. </pre> FreeBSD bugmaster 2013-06-10T11:06:23 http://permalink.gmane.org/gmane.os.freebsd.chromium/682 <pre> I looked at the chromium.desktop(.in) file again and noticed a superfluous '/' before 'x-scheme-handler/https', I think this is the culprit. René http://www.rene-ladan.nl/ GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) 2013/6/9 Baptiste Daroussin &lt;bapt&lt; at &gt;freebsd.org&gt;: </pre> René Ladan 2013-06-09T12:04:23 http://permalink.gmane.org/gmane.os.freebsd.chromium/681 <pre>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 invalid character in the subtype) done regards, Bapt </pre> Baptiste Daroussin 2013-06-09T11:48:45 http://permalink.gmane.org/gmane.os.freebsd.chromium/680 <pre>Some last fall, flash started asking weird in Chromium - seemed to also start with 24...suspect its how chromium uses shared memory now? Basically flash would render and then whiteout...scrolling the page would force it to redraw correctly, but could whiteout immediately. I think I've mentioned it in passing before, but hadn't seen anything else on the list about it. So, I decided that maybe its a problem specific to my setup....first I played around to see if there were flash settings to play with....had turned off hardware acceleration long ago to solve the blue skin tone problem. Didn't look like there was anything else that would do anything. Then I decided to look at my xorg.conf....after a long process of trial and error, I found that removing the option "AllowSHMPixmaps" "True" fixed the whiteout. Though now when flash first renders on the screen its garbage that looks like it might be a mash of the unexposed output from various terminals on my desktop. Kind of distracting, but it ev</pre> The BSD Dreamer 2013-06-07T15:05:16 http://permalink.gmane.org/gmane.os.freebsd.chromium/679 <pre> Oh look...after updating to the latest chromium, the chrome apps "currently" and "full screen weather" now know where I am. Lawrence </pre> The BSD Dreamer 2013-06-07T13:36:36 http://permalink.gmane.org/gmane.os.freebsd.chromium/678 <pre>René&lt; at &gt; got an official response [0] concerning they key, nothing to worry about. Just Enjoy [0] http://svnweb.freebsd.org/ports?view=revision&amp;revision=319796 _______________________________________________ freebsd-chromium&lt; at &gt;freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-chromium To unsubscribe, send any mail to "freebsd-chromium-unsubscribe&lt; at &gt;freebsd.org"</pre> George Liaskos 2013-06-06T20:21:55 http://permalink.gmane.org/gmane.os.freebsd.chromium/677 <pre>Thanks for doing this! I was a bit mystified as to why sync had broken, and stumbled here, eventually. I've used some of the other Google APIs and, at least for those, I'm pretty sure these are intended to be per-application (not per-user) keys, so I think including them in the build is consistent with what they are "normally" for. See https://code.google.com/apis/console/ where you "create a project" and get an API key that your application uses when issuing requests. See also https://developers.google.com/api-client-library/python/guide/aaa_apikeys I agree the language "don't share with other users" is confusing, so I'm not 100% sure. </pre> David P. Caldwell 2013-06-06T19:45:29 http://permalink.gmane.org/gmane.os.freebsd.chromium/676 <pre>Email not displaying correctly? View it ( http://sendgrid.org/wf/webmail?rp=ZTI1bGQzTnNaWFIwWlhKZmFXUTZNVEl6TkN4MWMyVnlYMmxrT2pJMU5qVTBmUWV5SnVaWGR6YkdWMGRHVnlYMmxrSWpvaU1UWTJOVEF4TmlJc0ltNWxkM05zWlhSMFpYSmZkWE5sY2w5cFpDSTZNall4T1RReU5EZzJOalI5 ) in your browser Increase Sales, Get More Leads &amp; Reach To New Customers ( http://sendgrid.com/newsletter/editNewsletter/id/1494080 ) ==================================================================================================================== DealsTrain.com is determined to promote best deals, products &amp; promotions in Singapore.   We will be promoting your Deals (on our website) through advertisement in top daily newspapers, social networking sites and through our dedicated 8 page brochure (contains best deals with full description,click here to see the brochure ( http://www.dealstrain.com/images/brochure2.pdf )). We are also advertising on TV and in various newspapers, which will benefit your brand as well.    We will always try our best to make your d</pre> Deals Train 2013-06-06T02:15:06 http://permalink.gmane.org/gmane.os.freebsd.chromium/675 <pre> ----- Original Message ----- Well, I'm not among the chromium-porters, but I have contributed ... ;) Lawrence </pre> Lawrence K. Chen, P.Eng. 2013-06-05T17:13:47 http://permalink.gmane.org/gmane.os.freebsd.chromium/674 <pre> Well, this wasn't exactly my question. But if this means that there are currently no plans among the chromium-porters to implement capsicum-support, then you're right: this would be the next question ... ;) Sadly, I'm not able to help with it, but nonetheless I would appreciate to use it ... Regards, kaltheat </pre> kaltheat< at >googlemail.com 2013-06-05T12:27:55 http://permalink.gmane.org/gmane.os.freebsd.chromium/673 <pre> ----- Original Message ----- Hmmm, suppose I need to read up on capsicum... Google is matching the funding from The FreeBSD Foundation on capsicum, with Google working on the Linux version. Sounds like they want it for Chrome OS, so ... Well, there's a wiki entry on ChromiumCapsicum -- https://wiki.freebsd.org/ChromiumCapsicum Suppose the question is who wants to do it, and will it be part of the current port or as a slave port? Lawrence </pre> Lawrence K. Chen, P.Eng. 2013-06-04T17:30:30 http://permalink.gmane.org/gmane.os.freebsd.chromium/672 <pre> Hi, are there any plans to provide chromium for FreeBSD with capsicum support? If I am right Mr. Watson already did it for a previous chromium-version and it was "little" effort to do so. It seems that since August, 2012 Mr. Dawidek is improving capsicum. His work seems to be funded by Google. Does this mean that they want to use it in base-chromium so that there is no need for FreeBSD-chromium-port to support capsicum on its own? Regards, kaltheat </pre> kaltheat< at >googlemail.com 2013-06-04T09:20:54 http://permalink.gmane.org/gmane.os.freebsd.chromium/671 <pre>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 -------------------------------------------------------------------------------- f ports/175369 chromium www/chromium: Chromimum Desktop Integration doesn't op o ports/165635 chromium www/chromium: 17.0.963.56: proxy isn't read by chrome f ports/165634 chromium www/chromium : 17.0.963.56 doesn't show physical print 3 problems total. </pre> FreeBSD bugmaster 2013-06-03T11:06:22 http://permalink.gmane.org/gmane.os.freebsd.chromium/670 <pre> ----- Original Message ----- And, presumably https://github.com/gliaskos/freebsd-chromium/commit/8701e94cc54126d6907d7665b5181e5d53705d90 is the official FreeBSD one. But the question is whether how Debian/Gentoo/Arch, and now FreeBSD, are distributing the keys in violation of http://www.chromium.org/developers/how-tos/api-keys "Note that the keys you have now acquired are not for distribution purposes and must not be shared with other users." I see geolocation is part api keys..is that why it hasn't been working since 23? Wonder if everybody who runs FreeBSD could just join the FreeBSD team and see the key? </pre> Lawrence K. Chen, P.Eng. 2013-05-30T22:28:00 http://permalink.gmane.org/gmane.os.freebsd.chromium/669 <pre>René should now have an official response from an &lt; at &gt;google.com e-mail. Please let me know if after that there are still some issues - and consider https://groups.google.com/a/chromium.org/forum/#!forum/chromium-packagersfor further questions. :) Paweł On Thu, May 30, 2013 at 12:22 PM, Xin Li &lt;delphij&lt; at &gt;delphij.net&gt; wrote: _______________________________________________ freebsd-chromium&lt; at &gt;freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-chromium To unsubscribe, send any mail to "freebsd-chromium-unsubscribe&lt; at &gt;freebsd.org"</pre> Paweł Hajdan, Jr. 2013-05-30T20:23:30 http://permalink.gmane.org/gmane.os.freebsd.chromium/668 <pre> I may be wrong but i don't think that this is feasible, you can not expect every enduser to generate keys so he can use the browser. We just need a key that will be "blessed" as official for FreeBSD, just like Debian [0], Gentoo [1], Arch [2] and others have done. [0] http://anonscm.debian.org/gitweb/?p=pkg-chromium/pkg-chromium.git;a=blob;f=debian/rules;hb=HEAD [1] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/www-client/chromium/chromium-9999-r1.ebuild?view=markup [2] https://projects.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/chromium </pre> George Liaskos 2013-05-30T19:45:22 http://permalink.gmane.org/gmane.os.freebsd.chromium/667 <pre>-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 05/30/13 11:46, George Liaskos wrote: Ah, ok so this is for identifying the client. I personally don't think this would work though. In order to do this, I think the only way would be: - Don't ship the port with a key. Instead, require the builder (currently everyone who runs FreeBSD) to acquire one for themselves. When the key is not present, don't build the features that requires an API key. - On FreeBSD package building cluster (as well as PC-BSD ones), deploy the "official" key and make binaries there. I don't see how this would even work as expected, though: the key is embedded in the binary and thus anyone who can run the binary and have debugging tools would be able to extract it. This situation is totally different from normal OAuth scenario, where API key is deployed on servers and protected from being accessed by average users, and the API provider can easily block misbehaving client when the key is "stolen". Cheers, - -- Xin LI &lt;delphi</pre> Xin Li 2013-05-30T19:22:09 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.os.freebsd.chromium