From owner-freebsd-chromium@FreeBSD.ORG Thu Jun 20 17:02:15 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 6BFBD3EA for ; Thu, 20 Jun 2013 17:02:15 +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 380191714 for ; Thu, 20 Jun 2013 17:02:14 +0000 (UTC) X-Merit-ExtLoop1: 1 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgUFAP8zw1HPS3TT/2dsb2JhbABYA4MJMUmDA70vFnSCIwEBBSNiAg0YAgINEgcCHTwZiA6bZY58iT6IBwSBIoEvi0IFgUUFgjeBFAOpB4FYgVOBTgcXIA X-IronPort-AV: E=Sophos;i="4.87,906,1363147200"; d="scan'208";a="118425523" X-MERIT-SOURCE: KSU Received: from ksu-sfpop-mailstore02.merit.edu ([207.75.116.211]) by sfpop-ironport01.merit.edu with ESMTP; 20 Jun 2013 13:01:00 -0400 Date: Thu, 20 Jun 2013 13:00:59 -0400 (EDT) From: "Lawrence K. Chen, P.Eng." To: freebsd-chromium@freebsd.org Message-ID: <931241605.26500798.1371747659991.JavaMail.root@k-state.edu> In-Reply-To: <51BFD820.6090501@mega-net.ru> 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: [129.130.0.181] 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: Thu, 20 Jun 2013 17:02:15 -0000 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