Launchpad has imported 10 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=754780.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2012-05-14T07:30:04+00:00 M-wada wrote: This is spin off of bug 752749 comment #8 for gloda error in bug 752749 comment #0. If a profile was used by Tb 9 or former, and if Tb 10 use and Tb 11 use is skipped, Gloda Scheme change is not correctly detected and gloda error is reported to Error Console by Tb 12 or newer, then Global Search doesn't work. So, one of next is needed. (a) Delete global-messages-db.sqlite, restart Tb 12 or newer. (b) Use the Tb's profile by Tb 10 or Tb 11 once, and use Tb 12 or newer. (1-1) With Gloda disabled, start Tb 9.0.1, terminate Tb. Followng message is shown. Schema change is detected. > gloda.datastore WARN Global database has been purged due to schema change. (1-2) With Gloda disabled, start Tb 12.0.1 or Tb 15.0a1 Following error occurs. Global Search doesn't work. > gloda.datastore ERROR Unexpected error when trying to open the database: > ReferenceError: aDBFile is not defined > gloda.everybody ERROR !!! error loading resource:///modules/gloda/fundattr.js > gloda.everybody ERROR (resource:///modules/gloda/datastore.js:1423) > TypeError: this.asyncConnection is null > gloda.explattr ERROR Error in init: TypeError: this.asyncConnection is null > gloda.everybody ERROR (resource:///modules/gloda/datastore.js:1555) > TypeError: this.asyncConnection is null > gloda.everybody ERROR !!! error loading > resource:///modules/gloda/noun_mimetype.js > gloda.everybody ERROR (resource:///modules/gloda/datastore.js:1423) > TypeError: this.asyncConnection is null > gloda.abattrs ERROR Error in init: TypeError: this.asyncConnection is null > gloda.everybody ERROR !!! error initializing > resource:///modules/gloda/index_ab.js > gloda.abattrs ERROR Error in init: TypeError: this.asyncConnection is null (2-1) With Gloda disabled, start Tb 9.0.1, terminate Tb. Followng message is shown. Schema change is detected. > gloda.datastore WARN Global database has been purged due to schema change. (2-2) With Gloda disabled, start Tb 10.0.1 or Tb 11.0.1 Followng message is shown. Schema change is detected. > gloda.datastore WARN Global database has been purged due to schema change. (2-3) With Gloda disabled, start Tb 12.0.1 or Tb 15.0a1 No gloda related error message is shown. Global Search continues to work. Reply at: https://bugs.launchpad.net/thunderbird/+bug/990331/comments/14 ------------------------------------------------------------------------ On 2012-05-15T04:06:24+00:00 Bugmail-asutherland wrote: Thanks very much for the excellent detective work! It appears I rushed the last migration logic fix too much; I apparently did not complete refactoring out the nuke migration logic and did not create a unit test for that code path. I have a fix and am writing the unit test now. To summarize, the situation is: - TB 12+ have broken nuke migration logic. - TB 10,11 have working nuke migration logic. - The last schema nuke happened with the release of TB 10, so anyone upgrading from TB 9 or earlier will make gloda want to nuke. So users who are upgrading from Thunderbird 3.1 will lose gloda. Although they probably weren't using gloda... Reply at: https://bugs.launchpad.net/thunderbird/+bug/990331/comments/15 ------------------------------------------------------------------------ On 2012-05-15T04:58:19+00:00 Bugmail-asutherland wrote: Created attachment 623939 add 2 tests that fail without the fix, pass with it Unfortunately, the tests need to be their own tests for realism. Reply at: https://bugs.launchpad.net/thunderbird/+bug/990331/comments/16 ------------------------------------------------------------------------ On 2012-05-15T04:59:59+00:00 Bugmail-asutherland wrote: Created attachment 623940 the fix that fixes the tests, and also thunderbird This fixes things. No complicated behaviour is required to correct affected Thunderbird profiles. What happens right now is that at every startup, gloda goes: "oh no, an out of date database, let me smite it!". Unfortunately, the smiting backfires and gloda dies instead. But with this fix, gloda will have the power to smite the database and work again. Reply at: https://bugs.launchpad.net/thunderbird/+bug/990331/comments/17 ------------------------------------------------------------------------ On 2012-05-17T19:28:24+00:00 Vseerror wrote: *** Bug 754631 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/thunderbird/+bug/990331/comments/19 ------------------------------------------------------------------------ On 2012-05-24T21:48:07+00:00 Mbanner wrote: Comment on attachment 623940 the fix that fixes the tests, and also thunderbird Thanks for the patches. r=me. Reply at: https://bugs.launchpad.net/thunderbird/+bug/990331/comments/20 ------------------------------------------------------------------------ On 2012-05-25T18:27:15+00:00 Bugmail-asutherland wrote: pushed to comm-central trunk: https://hg.mozilla.org/comm-central/rev/f2729b390e7b https://hg.mozilla.org/comm-central/rev/97f864cca479 Leaving branch landings to Standard8 or someone who understands what the tracking flag means. Reply at: https://bugs.launchpad.net/thunderbird/+bug/990331/comments/21 ------------------------------------------------------------------------ On 2012-05-25T18:27:35+00:00 Bugmail-asutherland wrote: crap, the tree was closed Reply at: https://bugs.launchpad.net/thunderbird/+bug/990331/comments/22 ------------------------------------------------------------------------ On 2012-05-28T20:46:01+00:00 Mbanner wrote: Comment on attachment 623939 add 2 tests that fail without the fix, pass with it [Triage Comment] We'll want this for 13 as well. So a=me. Reply at: https://bugs.launchpad.net/thunderbird/+bug/990331/comments/23 ------------------------------------------------------------------------ On 2012-05-29T08:06:50+00:00 Mbanner wrote: Checked in: https://hg.mozilla.org/releases/comm-aurora/rev/5038f76b1431 https://hg.mozilla.org/releases/comm-aurora/rev/4831bab6b12d https://hg.mozilla.org/releases/comm-beta/rev/166d519fc95e https://hg.mozilla.org/releases/comm-beta/rev/01303a6f3d9b Reply at: https://bugs.launchpad.net/thunderbird/+bug/990331/comments/24 ** Changed in: thunderbird Status: Unknown => Fix Released ** Changed in: thunderbird Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/990331 Title: Big Thunderbird problems after Ubuntu bugfix update To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/990331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
