From owner-freebsd-chromium@FreeBSD.ORG Mon Jul 1 11:06:23 2013 Return-Path: Delivered-To: chromium@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C339D500 for ; Mon, 1 Jul 2013 11:06:23 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id B4FF310A0 for ; Mon, 1 Jul 2013 11:06:23 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r61B6No4085290 for ; Mon, 1 Jul 2013 11:06:23 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r61B6NiM085288 for chromium@FreeBSD.org; Mon, 1 Jul 2013 11:06:23 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 1 Jul 2013 11:06:23 GMT Message-Id: <201307011106.r61B6NiM085288@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 Subject: Current problem reports assigned to chromium@FreeBSD.org X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Jul 2013 11:06:23 -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 -------------------------------------------------------------------------------- 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. From owner-freebsd-chromium@FreeBSD.ORG Mon Jul 1 15:28:07 2013 Return-Path: Delivered-To: chromium@FreeBSD.org Received: by hub.freebsd.org (Postfix, from userid 975) id ADD2A1EC; Mon, 1 Jul 2013 15:28:07 +0000 (UTC) Date: Mon, 1 Jul 2013 15:28:07 +0000 From: "Sergey A. Osokin" To: chromium@FreeBSD.org Subject: www/chromium Message-ID: <20130701152807.GJ91122@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Jul 2013 15:28:07 -0000 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. Please note - I built www/chromium from port. I've also tried www/opera and works good. Any idea? -- Sergey A. Osokin osa@FreeBSD.org From owner-freebsd-chromium@FreeBSD.ORG Mon Jul 1 18:50:49 2013 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 6654588D; Mon, 1 Jul 2013 18:50:49 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from mail-ee0-x235.google.com (mail-ee0-x235.google.com [IPv6:2a00:1450:4013:c00::235]) by mx1.freebsd.org (Postfix) with ESMTP id C8BBE1B92; Mon, 1 Jul 2013 18:50:48 +0000 (UTC) Received: by mail-ee0-f53.google.com with SMTP id c41so2274321eek.12 for ; Mon, 01 Jul 2013 11:50:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=eaJMnZxk8aoB4vfsxW4d+yQXJOOCNY02f6y7cwf9fDM=; b=UFQGwDFemrv3evgC0OmuiqzwxT2jSGELZf87vnglnkEtEaKDAavQvkpD8lA2TPYByV Pao82B2SKwQGeoXjRa/qMcUu46w6zX+jOnYp79yX4dglvRfSOE8rE9V3tw8kD42d+RCO TaD47/kXsTmd37xwwWTyPByAzth7lVRaMRAa6pM3PZ9xB7v0S/vtzeIJHhogo1PpnuQ/ 5eTJoBlrLeKpTl8A8DmGC4jsUwjIAR4SwsYpH8VZWzuzmhTBI+Ls6kK/te7fMoWt9CWs Kkn1Yl3M7Dpq1robIrwVkRzxS14vDqWJflOCykUAw7pT4ASASH4ctcXjO5EDHdLtsZQG fVyw== X-Received: by 10.14.106.195 with SMTP id m43mr22670043eeg.60.1372704647931; Mon, 01 Jul 2013 11:50:47 -0700 (PDT) Received: from ?IPv6:2001:980:d7ed:1:8cfa:c24d:11b1:6584? ([2001:980:d7ed:1:8cfa:c24d:11b1:6584]) by mx.google.com with ESMTPSA id cg12sm31488038eeb.7.2013.07.01.11.50.46 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 01 Jul 2013 11:50:47 -0700 (PDT) Sender: =?UTF-8?Q?Ren=C3=A9_Ladan?= Message-ID: <51D1CF84.1080609@freebsd.org> Date: Mon, 01 Jul 2013 20:50:44 +0200 From: =?ISO-8859-1?Q?Ren=E9_Ladan?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130701 Thunderbird/17.0.7 MIME-Version: 1.0 To: freebsd-chromium@freebsd.org, "Sergey A. Osokin" Subject: Re: www/chromium References: <20130701152807.GJ91122@FreeBSD.org> In-Reply-To: <20130701152807.GJ91122@FreeBSD.org> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Jul 2013 18:50:49 -0000 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. > Please note - I built www/chromium from port. > > I've also tried www/opera and works good. > > Any idea? > Not really, the page shows fine here on FreeBSD 9.1-RELEASE-amd64. My chromium 27.0.1453.116 is built with the default options (so compiled with clang from base). I use poudriere to build packages in a clean environment, maybe something in your environments breaks rendering (e.g. outdated ports or something in 9.1-STABLE)? Regards, René From owner-freebsd-chromium@FreeBSD.ORG Mon Jul 1 19:08:32 2013 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 21CD5E65; Mon, 1 Jul 2013 19:08:32 +0000 (UTC) (envelope-from geo.liaskos@gmail.com) Received: from mail-ea0-x230.google.com (mail-ea0-x230.google.com [IPv6:2a00:1450:4013:c01::230]) by mx1.freebsd.org (Postfix) with ESMTP id 8A4C61C7C; Mon, 1 Jul 2013 19:08:31 +0000 (UTC) Received: by mail-ea0-f176.google.com with SMTP id z15so2247215ead.21 for ; Mon, 01 Jul 2013 12:08:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=GbViMH68IbrTCt8SGuVetXejGgD2D06cbt8umXYG3sg=; b=k+t4XBC0niwVbgFISnRpBOAsWzN2Y2jXVm1HU/t0Ma3IC0tHflEHVLgFDSEQlwtgWz oeJLBuLNXxx1LBD3vvhjkhwwHSNK5mQzwZaDIjJ1MnxJgvMfkBGXy5v+FQnnWoRsuEJK iIx8i6H+tNrySJnLjfPBV2Di5osQ7DZxHqDi8dcqNpSRx6H4/kigS+fPr8fPSbe/wFEN Mq6aiSOZI+fgmZscpJrXNwP2GXDuMgj1Y6yT7oUXcrHrc/thJY8QMSS32dV9Bn2AefdH WV7DMTrh5rjrKHx8qiN7TbLefT3EKGeMliqaORqqU7m+xYQSDmiPqBCnahwNW0/ljD4S r4jw== MIME-Version: 1.0 X-Received: by 10.14.104.4 with SMTP id h4mr22666841eeg.61.1372705710706; Mon, 01 Jul 2013 12:08:30 -0700 (PDT) Received: by 10.223.127.133 with HTTP; Mon, 1 Jul 2013 12:08:30 -0700 (PDT) In-Reply-To: <20130701152807.GJ91122@FreeBSD.org> References: <20130701152807.GJ91122@FreeBSD.org> Date: Mon, 1 Jul 2013 22:08:30 +0300 Message-ID: Subject: Re: www/chromium From: George Liaskos To: "Sergey A. Osokin" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: chromium@freebsd.org X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Jul 2013 19:08:32 -0000 > > Any idea? > > Maybe you missed the pkg-message? From owner-freebsd-chromium@FreeBSD.ORG Tue Jul 2 03:40:56 2013 Return-Path: Delivered-To: chromium@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 975) id BDE87129; Tue, 2 Jul 2013 03:40:56 +0000 (UTC) Date: Tue, 2 Jul 2013 03:40:56 +0000 From: "Sergey A. Osokin" To: George Liaskos Subject: Re: www/chromium Message-ID: <20130702034056.GA63640@FreeBSD.org> References: <20130701152807.GJ91122@FreeBSD.org> 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 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jul 2013 03:40:56 -0000 On Mon, Jul 01, 2013 at 10:08:30PM +0300, George Liaskos wrote: > > > > Any idea? > > > Maybe you missed the pkg-message? Good catch. I rebuilt kernel without SYSV* extensions. I've kldloaded sysv* kernel modules, sysctled kern.ipc.shm_allow_removed and everything works fine. Thanks. Probably, we need to update pkg-message, i.e. Please check SYSVSHM/whatever settings before report the bug. -- Sergey A. Osokin osa@FreeBSD.org From owner-freebsd-chromium@FreeBSD.ORG Tue Jul 2 13:31:25 2013 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D8EC3D9 for ; Tue, 2 Jul 2013 13:31:25 +0000 (UTC) (envelope-from lkchen@k-state.edu) Received: from ksu-out.merit.edu (ksu-out.merit.edu [207.75.117.133]) by mx1.freebsd.org (Postfix) with ESMTP id 9FF0B1DD5 for ; Tue, 2 Jul 2013 13:31:25 +0000 (UTC) X-Merit-ExtLoop1: 1 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AiMFAJfT0lHPS3TT/2dsb2JhbABXAxaCczJJgwe9RxZ0giMBAQEEAQEBICsgFwINGAICDRIHAh0MAQkYAQ0OBwQBHASHbgybRo58iTGIBwSBIoEwi0IQBYFFgkCBGgOVBINukByBWIFVUnwHFyA X-IronPort-AV: E=Sophos;i="4.87,980,1363147200"; d="scan'208";a="230094133" X-MERIT-SOURCE: KSU Received: from ksu-sfpop-mailstore02.merit.edu ([207.75.116.211]) by sfpop-ironport07.merit.edu with ESMTP; 02 Jul 2013 09:30:18 -0400 Date: Tue, 2 Jul 2013 09:30:17 -0400 (EDT) From: "Lawrence K. Chen, P.Eng." To: freebsd-chromium@freebsd.org Message-ID: <1803565128.29315497.1372771817328.JavaMail.root@k-state.edu> In-Reply-To: <210591621.26903432.1371845380989.JavaMail.root@k-state.edu> Subject: Re: Sync Error: Sign in Again - Looping (was Re: using API keys in the FreeBSD Chromium port) FreeBSD Chromium port) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [70.179.144.108] X-Mailer: Zimbra 7.2.2_GA_2852 (ZimbraWebClient - GC27 ([unknown])/7.2.2_GA_2852) X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jul 2013 13:31:25 -0000 So this is problem is weird.... Decided the Favicon db was terminal...so I deleted it from my Chromium profiles on all my FreeBSD systems (no mention of it in chrome://sync in chrome....guessing its some experimental sync only in chromium) Didn't solve the reappearance of the sign in again - looping problem. So, I was comparing the URL of the sign in page in chromium vs chrome (on Windows 7)....and sign in worked on chrome of course....but then I pasted an URL into a new tab and the sign in worked! Was it a fluke? I intentionally signed out, and tried to sign back in....results in sign in looping. But, copy URL from sign in looping tab to a new tab....the sign in works. So, there's something about the tab it spawns is different than a normal new tab? During my testing, I had tried clearing cache, clearing cookies, but it would still loop. ----- Original Message ----- > > I later recalled the 'echo .dump | sqlite3 old.db | sqlite3 new.db' > trick....still wonder how it get's messed up again, or perhaps the > sqliteman thing did ... didn't really fix, but rather the restart > made it look like it was. Though when I had looked at my system at > home last night, it was showing this error...but it wasn't asking me > to sign in again yet. > > chrome://sync > > Type Info > > Favicon Images |Error: > ProcessSyncChanges@chrome/browser/sync/glue/generic_change_processor.cc:326, > Failed to create Favicon Images node: > UpdateSyncState@chrome/browser/sync/glue/favicon_cache.cc:701, entry > already exists |0 |0 > Favicon Tracking |Error: > ProcessSyncChanges@chrome/browser/sync/glue/favicon_cache.cc:326, > One or both favicon types disabled. |0 |0 > > I should fire up chrome on some other computer and see what it thinks > of Favicon....though the sign in again problem has only been on > FreeBSD for me. > > ----- Original Message ----- > > Here's something interesting....I happened to look at chrome://sync > > and saw that it was complaining about "Favicons Images" and > > "Favicons Tracking" > > > > Didn't think to capture the screen...but it was something with > > "LogLookupFailure@chrome/browser/sync/glue/generic_change_process", > > which is what I had copied for a search.... > > > > Saw something about the Favicons sqlite3 database....so after > > finding > > something in ports to look at sqlite3 databases > > (databases/sqliteman), I tried opening it. Though I had no idea > > how > > to use sqliteman to see details (my only experience has been from > > Windows, back when I was contributing to WiRNS and the Poopli > > Updater...)...but I tried the analyze and vacuum options....got no > > output, but it changed the file. > > > > Restarted chromium and it was green for the two Favicon items and > > syncs were happening again. > > > > That was Tuesday....today the problem came back, and again its > > complaining about the same thing....doing the sqliteman thing again > > seemed to have fixed it again. But, what is causing this problem? > > > > I do have a background tab (feedly), so chromium stays running all > > the time though I had noticed frequently that when I come into work > > in the morning that chromium has disappeared, and no message about > > why in dmesg, etc. Haven't seen the chromium disappearing problem > > at home, though have seen the sync problem there and also did the > > same fix on Tuesday...didn't run into signin problem when I was > > using chromium this morning.... > > > > Lawrence > > > > ----- Original Message ----- > > > 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@mega-net.ru > > > > > > On 18.06.2013 01:48, Lawrence K. Chen, P.Eng. wrote: > > > > > > > > ----- Original Message ----- > > > >> Thanks for doing this! I was a bit mystified as to why sync > > > >> had > > > >> broken, and stumbled here, eventually. > > > >> > > > > 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 > > _______________________________________________ > > freebsd-chromium@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-chromium > > To unsubscribe, send any mail to > > "freebsd-chromium-unsubscribe@freebsd.org" > > > > -- > Who: Lawrence K. Chen, P.Eng. - W0LKC - Senior Unix Systems > Administrator > For: Enterprise Server Technologies (EST) -- & SafeZone Ally > Snail: Computing and Telecommunications Services (CTS) > Kansas State University, 109 East Stadium, Manhattan, KS 66506-3102 > Phone: (785) 532-4916 - Fax: (785) 532-3515 - Email: lkchen@ksu.edu > Web: http://www-personal.ksu.edu/~lkchen - Where: 11 Hale Library > _______________________________________________ > freebsd-chromium@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-chromium > To unsubscribe, send any mail to > "freebsd-chromium-unsubscribe@freebsd.org" > -- Who: Lawrence K. Chen, P.Eng. - W0LKC - Senior Unix Systems Administrator For: Enterprise Server Technologies (EST) -- & SafeZone Ally Snail: Computing and Telecommunications Services (CTS) Kansas State University, 109 East Stadium, Manhattan, KS 66506-3102 Phone: (785) 532-4916 - Fax: (785) 532-3515 - Email: lkchen@ksu.edu Web: http://www-personal.ksu.edu/~lkchen - Where: 11 Hale Library From owner-freebsd-chromium@FreeBSD.ORG Tue Jul 2 15:56:47 2013 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id CE4AAD23 for ; Tue, 2 Jul 2013 15:56:47 +0000 (UTC) (envelope-from evanm@google.com) Received: from mail-qa0-x22e.google.com (mail-qa0-x22e.google.com [IPv6:2607:f8b0:400d:c00::22e]) by mx1.freebsd.org (Postfix) with ESMTP id 830D11701 for ; Tue, 2 Jul 2013 15:56:47 +0000 (UTC) Received: by mail-qa0-f46.google.com with SMTP id ih17so2966263qab.12 for ; Tue, 02 Jul 2013 08:56:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=rgwoCSsGU372dk2afjpvhKsY+qIsNIPgxIM3Ah+ClpA=; b=Cj9J+kidivBHG6xLUDB/fXnCecuOjAXScL2UPSaMiLkFMZAnarrTfbqmY76H3LF1xI ff9bK8OEVTXQpGPq6IOuQFnLq6bKw1bKJ+UmCFR8b0BL2gpLrqFHPqxXHu8APbJ5WhfA jxdFe9IJxl99lM4hu3NzFQ2UNnQTJby5r+QdUHoC5ne0xuRcEMqZdCEGL1VcXn8LzmU8 Hl0+KwMG4jtsjHigJH5KlNSkx4lsosQtTdKefGKntSrFcC6GY9EUD0MZBzeauwi117C2 jF2lUoR8eBGsoPBFtUgartJodOmLBI9bgn8QVdo7/LUMkUfKp1NfNRZsVJr0A8jRJMOa W9ow== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=rgwoCSsGU372dk2afjpvhKsY+qIsNIPgxIM3Ah+ClpA=; b=L9wNYvgYR2XULN3IEhzAw/CvuiTarrkI8vJ+5Ghg4UTnDXFjEa0rD4IIBXZmOeajxz RXywarOYJPNjCB6F3xzO4vgqF3eaS6Nv+VZPkJQbI1UEJ7JoaHel5od8PcZFJnFV69k9 1wOUW3ZbHgbgUtcZ1mIymv0qfF0XWjzxcyl3U= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :x-gm-message-state; bh=rgwoCSsGU372dk2afjpvhKsY+qIsNIPgxIM3Ah+ClpA=; b=bm0kwTTQSM7HctmqgGd0vG67qGfiIX/qO1mxypxD3GE9gAXsAfXkEC8QT2rlWVfhqs oalwXBOjAHd9OoY803dEr/yG+gBfzp1kwSKqHvuz7xMks7EF/k+R4jd5Wo9/3UIAdMKu 8aIfcsC++dY0Tw6AVCCx6YojGGpXT2VT7+Hx4BugVvHc2l/kj5PS9BsFy24i5ifFbHYX CNaz6NQUjnmrFQxSOUG8VGLXt07YpRA6Dbt+gfhHeHH/Rx587jgsC0ZdYZ1GIddVL6lx i25g/xiCWpH+0JdQ7PFdX7CwHDbP1ytzadSosMQaRfy1SzNhe9cMwydOvqV9QQKdw4Ds bBiQ== MIME-Version: 1.0 X-Received: by 10.224.127.73 with SMTP id f9mr39450488qas.4.1372780606986; Tue, 02 Jul 2013 08:56:46 -0700 (PDT) Sender: evanm@google.com Received: by 10.229.106.4 with HTTP; Tue, 2 Jul 2013 08:56:46 -0700 (PDT) In-Reply-To: <1803565128.29315497.1372771817328.JavaMail.root@k-state.edu> References: <210591621.26903432.1371845380989.JavaMail.root@k-state.edu> <1803565128.29315497.1372771817328.JavaMail.root@k-state.edu> Date: Tue, 2 Jul 2013 08:56:46 -0700 X-Google-Sender-Auth: nXktKGCvRc6IDjoFJtMFhV_HLQM Message-ID: Subject: Re: Sync Error: Sign in Again - Looping (was Re: using API keys in the FreeBSD Chromium port) FreeBSD Chromium port) From: Evan Martin To: "Lawrence K. Chen, P.Eng." X-Gm-Message-State: ALoCoQlakzc0UEu02Yfru1j3QnBa6geomUoaWPTycD6STiK/zIy3aaZ7tKBh41+N+VJjEX75K7HAtj8mDnsOQgSumsB1sVu71FoQsNdVKGIe8l5NGnzwH7YsGs7nKMjPUzYvoEMvkIB8vO7cKhcSXig8BkLcvODjDFRuX0UlUmsREdvILQLK3v3YZbpIsqHDrNYsOI+CKmIFymk9u89/4CWsVJsj0/tUqw== Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-chromium@freebsd.org X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jul 2013 15:56:47 -0000 Sign in looping is often a symptom of something going wrong with cookies. Two ideas: - clear all your cookies - check that you haven't set up any cookie-related settings that break sites (in particular, the "block third-party cookies" setting might be more aptly named "randomly break sites in an unpredictable manner") On Tue, Jul 2, 2013 at 6:30 AM, Lawrence K. Chen, P.Eng. wrote: > So this is problem is weird.... > > Decided the Favicon db was terminal...so I deleted it from my Chromium > profiles on all my FreeBSD systems (no mention of it in chrome://sync in > chrome....guessing its some experimental sync only in chromium) > > Didn't solve the reappearance of the sign in again - looping problem. > > So, I was comparing the URL of the sign in page in chromium vs chrome (on > Windows 7)....and sign in worked on chrome of course....but then I pasted > an URL into a new tab and the sign in worked! > > Was it a fluke? > > I intentionally signed out, and tried to sign back in....results in sign > in looping. But, copy URL from sign in looping tab to a new tab....the > sign in works. So, there's something about the tab it spawns is different > than a normal new tab? > > During my testing, I had tried clearing cache, clearing cookies, but it > would still loop. > > ----- Original Message ----- > > > > I later recalled the 'echo .dump | sqlite3 old.db | sqlite3 new.db' > > trick....still wonder how it get's messed up again, or perhaps the > > sqliteman thing did ... didn't really fix, but rather the restart > > made it look like it was. Though when I had looked at my system at > > home last night, it was showing this error...but it wasn't asking me > > to sign in again yet. > > > > chrome://sync > > > > Type Info > > > > Favicon Images |Error: > > ProcessSyncChanges@chrome > /browser/sync/glue/generic_change_processor.cc:326, > > Failed to create Favicon Images node: > > UpdateSyncState@chrome/browser/sync/glue/favicon_cache.cc:701, entry > > already exists |0 |0 > > Favicon Tracking |Error: > > ProcessSyncChanges@chrome/browser/sync/glue/favicon_cache.cc:326, > > One or both favicon types disabled. |0 |0 > > > > I should fire up chrome on some other computer and see what it thinks > > of Favicon....though the sign in again problem has only been on > > FreeBSD for me. > > > > ----- Original Message ----- > > > Here's something interesting....I happened to look at chrome://sync > > > and saw that it was complaining about "Favicons Images" and > > > "Favicons Tracking" > > > > > > Didn't think to capture the screen...but it was something with > > > "LogLookupFailure@chrome/browser/sync/glue/generic_change_process", > > > which is what I had copied for a search.... > > > > > > Saw something about the Favicons sqlite3 database....so after > > > finding > > > something in ports to look at sqlite3 databases > > > (databases/sqliteman), I tried opening it. Though I had no idea > > > how > > > to use sqliteman to see details (my only experience has been from > > > Windows, back when I was contributing to WiRNS and the Poopli > > > Updater...)...but I tried the analyze and vacuum options....got no > > > output, but it changed the file. > > > > > > Restarted chromium and it was green for the two Favicon items and > > > syncs were happening again. > > > > > > That was Tuesday....today the problem came back, and again its > > > complaining about the same thing....doing the sqliteman thing again > > > seemed to have fixed it again. But, what is causing this problem? > > > > > > I do have a background tab (feedly), so chromium stays running all > > > the time though I had noticed frequently that when I come into work > > > in the morning that chromium has disappeared, and no message about > > > why in dmesg, etc. Haven't seen the chromium disappearing problem > > > at home, though have seen the sync problem there and also did the > > > same fix on Tuesday...didn't run into signin problem when I was > > > using chromium this morning.... > > > > > > Lawrence > > > > > > ----- Original Message ----- > > > > 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@mega-net.ru > > > > > > > > On 18.06.2013 01:48, Lawrence K. Chen, P.Eng. wrote: > > > > > > > > > > ----- Original Message ----- > > > > >> Thanks for doing this! I was a bit mystified as to why sync > > > > >> had > > > > >> broken, and stumbled here, eventually. > > > > >> > > > > > 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 > > > _______________________________________________ > > > freebsd-chromium@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-chromium > > > To unsubscribe, send any mail to > > > "freebsd-chromium-unsubscribe@freebsd.org" > > > > > > > -- > > Who: Lawrence K. Chen, P.Eng. - W0LKC - Senior Unix Systems > > Administrator > > For: Enterprise Server Technologies (EST) -- & SafeZone Ally > > Snail: Computing and Telecommunications Services (CTS) > > Kansas State University, 109 East Stadium, Manhattan, KS 66506-3102 > > Phone: (785) 532-4916 - Fax: (785) 532-3515 - Email: lkchen@ksu.edu > > Web: http://www-personal.ksu.edu/~lkchen - Where: 11 Hale Library > > _______________________________________________ > > freebsd-chromium@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-chromium > > To unsubscribe, send any mail to > > "freebsd-chromium-unsubscribe@freebsd.org" > > > > -- > Who: Lawrence K. Chen, P.Eng. - W0LKC - Senior Unix Systems Administrator > For: Enterprise Server Technologies (EST) -- & SafeZone Ally > Snail: Computing and Telecommunications Services (CTS) > Kansas State University, 109 East Stadium, Manhattan, KS 66506-3102 > Phone: (785) 532-4916 - Fax: (785) 532-3515 - Email: lkchen@ksu.edu > Web: http://www-personal.ksu.edu/~lkchen - Where: 11 Hale Library > _______________________________________________ > freebsd-chromium@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-chromium > To unsubscribe, send any mail to "freebsd-chromium-unsubscribe@freebsd.org > " > From owner-freebsd-chromium@FreeBSD.ORG Tue Jul 2 15:57:51 2013 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4FCB5DD5 for ; Tue, 2 Jul 2013 15:57:51 +0000 (UTC) (envelope-from evanm@google.com) Received: from mail-qc0-x232.google.com (mail-qc0-x232.google.com [IPv6:2607:f8b0:400d:c01::232]) by mx1.freebsd.org (Postfix) with ESMTP id 07B551715 for ; Tue, 2 Jul 2013 15:57:50 +0000 (UTC) Received: by mail-qc0-f178.google.com with SMTP id c11so3715124qcv.23 for ; Tue, 02 Jul 2013 08:57:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=F1DxJ02L7Na+UwrW9YmTe4eNCLPsOzRg2kw3p+yZ71M=; b=QaO3xluxVSbmO1sliOO8khF+96kUOHbuuWLCIpMmGXABB1RKwjivRhzgcxfnf3Z0q0 Pkj0xUTgZ3U4Bv9mXP34YEOrW27mpX3j17OgFXXRq8cIqGr/kl3p8yrr2aGD2AI5TVp8 epruExJu1S+sGmNt+7bWqIp17gWqZYUfUYt2EpQ/ACnTJwyB1177kOSBrZ4nLsAngpRH bAjrMcDWKO8HSyZWmIGHfxLTKQ4vYk1wC1G/4OI/Pht2LA8zPpPIeBsbnkMTEwIluPi2 8fbaMXb5IaI2NcnRFT7C5tc6LLlJNR+03+LDc8lXPlTsyA/YLXIQvj2bzR3iym0L+Khq Vqtw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=F1DxJ02L7Na+UwrW9YmTe4eNCLPsOzRg2kw3p+yZ71M=; b=U9iFzMALs4vuPotJQMFcXaIFY/lMZKhkguFo4g9urwK381/nURcVDZMn4sZTHA7fCu DwShP3u4dcrUrwka6Q05XgRXMIcp/EMK40BR+xFtuhY2j6rTlVXEgeL182GsxyTk/K/s fTW0ls3UccYYbkg7Q2WHoE52IE3/GUA8y5Wco= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :x-gm-message-state; bh=F1DxJ02L7Na+UwrW9YmTe4eNCLPsOzRg2kw3p+yZ71M=; b=i2bUDR02Lw7/Cdy4MZWvwbhPfy/O0YB9Y5Tr2jQJhAZIFufy7PvltbnzREwIoTK6C5 lr64MGrDhR4FzkVax0Zkis6jN0V9Btn4kdn1oYsz1a4nvjNhpsKGix6ZnPnp6BnfnmQj fkYoBh1PHJ4I9WJxUe5647QfM+fsv61c8zuWsjFV6viF11ApCynIPO7Moxy03FlYIfkF vF5OV1b55gX/39o83Ug+1R9MPu6eGaC+A6nxsNJ6tfKpHqbm8mqWA6gNtMeetSxvQ114 pHG2iG4w+KuTnNmJ2NUXB+CggUFcNmSEvej2JN5dSevyvlq+hsifxgUJ7BInUgd3r3U4 Te1g== MIME-Version: 1.0 X-Received: by 10.224.38.133 with SMTP id b5mr39812681qae.78.1372780670446; Tue, 02 Jul 2013 08:57:50 -0700 (PDT) Sender: evanm@google.com Received: by 10.229.106.4 with HTTP; Tue, 2 Jul 2013 08:57:50 -0700 (PDT) In-Reply-To: References: <210591621.26903432.1371845380989.JavaMail.root@k-state.edu> <1803565128.29315497.1372771817328.JavaMail.root@k-state.edu> Date: Tue, 2 Jul 2013 08:57:50 -0700 X-Google-Sender-Auth: YQnvQEUy6pApo0oKtnTgFEDUlO0 Message-ID: Subject: Re: Sync Error: Sign in Again - Looping (was Re: using API keys in the FreeBSD Chromium port) FreeBSD Chromium port) From: Evan Martin To: "Lawrence K. Chen, P.Eng." Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQkQdvBR1BaPA/P824zQ4S2K7BqVqq7JQkpvIDt45iRYyj/MIk+vHbm+2K0WcfMeH4n271HUfl0P6eQlEDowDmtwGUl6xt15mofsh/vUUUqThRYaD2e8BnyDeSCySSnJYgeQZwckjiJ4aH5VXOMN0w2aa52wyoTji4k/mXCxq7WiSV6EyVgbWws/kenN7xlr2qqhzXk1+d1cVAD3YYLBdpDrpPNovQ== Cc: freebsd-chromium@freebsd.org X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jul 2013 15:57:51 -0000 Ah, I misread the beginning of the thread, please disregard. On Tue, Jul 2, 2013 at 8:56 AM, Evan Martin wrote: > Sign in looping is often a symptom of something going wrong with cookies. > Two ideas: > - clear all your cookies > - check that you haven't set up any cookie-related settings that break sites > (in particular, the "block third-party cookies" setting might be more aptly > named "randomly break sites in an unpredictable manner") > > > On Tue, Jul 2, 2013 at 6:30 AM, Lawrence K. Chen, P.Eng. > wrote: >> >> So this is problem is weird.... >> >> Decided the Favicon db was terminal...so I deleted it from my Chromium >> profiles on all my FreeBSD systems (no mention of it in chrome://sync in >> chrome....guessing its some experimental sync only in chromium) >> >> Didn't solve the reappearance of the sign in again - looping problem. >> >> So, I was comparing the URL of the sign in page in chromium vs chrome (on >> Windows 7)....and sign in worked on chrome of course....but then I pasted an >> URL into a new tab and the sign in worked! >> >> Was it a fluke? >> >> I intentionally signed out, and tried to sign back in....results in sign >> in looping. But, copy URL from sign in looping tab to a new tab....the sign >> in works. So, there's something about the tab it spawns is different than a >> normal new tab? >> >> During my testing, I had tried clearing cache, clearing cookies, but it >> would still loop. >> >> ----- Original Message ----- >> > >> > I later recalled the 'echo .dump | sqlite3 old.db | sqlite3 new.db' >> > trick....still wonder how it get's messed up again, or perhaps the >> > sqliteman thing did ... didn't really fix, but rather the restart >> > made it look like it was. Though when I had looked at my system at >> > home last night, it was showing this error...but it wasn't asking me >> > to sign in again yet. >> > >> > chrome://sync >> > >> > Type Info >> > >> > Favicon Images |Error: >> > >> > ProcessSyncChanges@chrome/browser/sync/glue/generic_change_processor.cc:326, >> > Failed to create Favicon Images node: >> > UpdateSyncState@chrome/browser/sync/glue/favicon_cache.cc:701, entry >> > already exists |0 |0 >> > Favicon Tracking |Error: >> > ProcessSyncChanges@chrome/browser/sync/glue/favicon_cache.cc:326, >> > One or both favicon types disabled. |0 |0 >> > >> > I should fire up chrome on some other computer and see what it thinks >> > of Favicon....though the sign in again problem has only been on >> > FreeBSD for me. >> > >> > ----- Original Message ----- >> > > Here's something interesting....I happened to look at chrome://sync >> > > and saw that it was complaining about "Favicons Images" and >> > > "Favicons Tracking" >> > > >> > > Didn't think to capture the screen...but it was something with >> > > "LogLookupFailure@chrome/browser/sync/glue/generic_change_process", >> > > which is what I had copied for a search.... >> > > >> > > Saw something about the Favicons sqlite3 database....so after >> > > finding >> > > something in ports to look at sqlite3 databases >> > > (databases/sqliteman), I tried opening it. Though I had no idea >> > > how >> > > to use sqliteman to see details (my only experience has been from >> > > Windows, back when I was contributing to WiRNS and the Poopli >> > > Updater...)...but I tried the analyze and vacuum options....got no >> > > output, but it changed the file. >> > > >> > > Restarted chromium and it was green for the two Favicon items and >> > > syncs were happening again. >> > > >> > > That was Tuesday....today the problem came back, and again its >> > > complaining about the same thing....doing the sqliteman thing again >> > > seemed to have fixed it again. But, what is causing this problem? >> > > >> > > I do have a background tab (feedly), so chromium stays running all >> > > the time though I had noticed frequently that when I come into work >> > > in the morning that chromium has disappeared, and no message about >> > > why in dmesg, etc. Haven't seen the chromium disappearing problem >> > > at home, though have seen the sync problem there and also did the >> > > same fix on Tuesday...didn't run into signin problem when I was >> > > using chromium this morning.... >> > > >> > > Lawrence >> > > >> > > ----- Original Message ----- >> > > > 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@mega-net.ru >> > > > >> > > > On 18.06.2013 01:48, Lawrence K. Chen, P.Eng. wrote: >> > > > > >> > > > > ----- Original Message ----- >> > > > >> Thanks for doing this! I was a bit mystified as to why sync >> > > > >> had >> > > > >> broken, and stumbled here, eventually. >> > > > >> >> > > > > 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 >> > > _______________________________________________ >> > > freebsd-chromium@freebsd.org mailing list >> > > http://lists.freebsd.org/mailman/listinfo/freebsd-chromium >> > > To unsubscribe, send any mail to >> > > "freebsd-chromium-unsubscribe@freebsd.org" >> > > >> > >> > -- >> > Who: Lawrence K. Chen, P.Eng. - W0LKC - Senior Unix Systems >> > Administrator >> > For: Enterprise Server Technologies (EST) -- & SafeZone Ally >> > Snail: Computing and Telecommunications Services (CTS) >> > Kansas State University, 109 East Stadium, Manhattan, KS 66506-3102 >> > Phone: (785) 532-4916 - Fax: (785) 532-3515 - Email: lkchen@ksu.edu >> > Web: http://www-personal.ksu.edu/~lkchen - Where: 11 Hale Library >> > _______________________________________________ >> > freebsd-chromium@freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-chromium >> > To unsubscribe, send any mail to >> > "freebsd-chromium-unsubscribe@freebsd.org" >> > >> >> -- >> Who: Lawrence K. Chen, P.Eng. - W0LKC - Senior Unix Systems Administrator >> For: Enterprise Server Technologies (EST) -- & SafeZone Ally >> Snail: Computing and Telecommunications Services (CTS) >> Kansas State University, 109 East Stadium, Manhattan, KS 66506-3102 >> Phone: (785) 532-4916 - Fax: (785) 532-3515 - Email: lkchen@ksu.edu >> Web: http://www-personal.ksu.edu/~lkchen - Where: 11 Hale Library >> _______________________________________________ >> freebsd-chromium@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-chromium >> To unsubscribe, send any mail to >> "freebsd-chromium-unsubscribe@freebsd.org" > >