Daily Build Thread Please use the next Daily Build Thread Here [If you would like to volunteer to post this weekly thread on a rotational basis Please go here: http://wiki.mozilla.org/Thunderbird:Nig ... ld_Threads for further instructions.]
Danger, Will Robinson, danger! Current situations to be aware of
Running TB 12 with local mail folders and pop3 mail filters may produce summary files that aren't correctly read by previous versions of Thunderbird See: TB 12 Known Issues
Checkins This Week
Now posted in each channel's status section
Recent Bugs/Links of interest
# 567240 [MailNews Core] - No blinking cursor when replying [Win] # 647036 [Thunderbird] - Allow attachment pane of a message to open non-collapsed by default [All] # 737347 [Thunderbird] - [meta] Postbox-Parity - equal or better Postbox's UX [Win]
Latest Tested Builds
The current nightly build, unless otherwise noted
Lanikai (Thunderbird 3.1 / Gecko 1.9.2) Status Green
Checkins This Week #739639 [Thunderbird:Message Compose Window]-forwarding message puts cursor at end instead of beginning [All] #749690 [Thunderbird:Instant Messaging]-Add a findbar and support the zoom feature in the chat tab [All] #751679 [Thunderbird:Build Config]-Update AUS server for Thunderbird [All]
Checkins This Week [May 02 02:06:18 2012 PST]#748388 [Thunderbird:Instant Messaging]-Protocol icon not displayed/updated in the right pane when selecting a contact [All] [May 02 02:06:18 2012 PST]#749552 [Thunderbird:Instant Messaging]-The Command+K keyboard shortcut should select for chat search box when the chat tab is selected [All] [May 02 02:06:18 2012 PST]#740765 [Thunderbird:Instant Messaging]-Starting or selecting a conversation with the mouse should focus the input box immediately [All] [May 02 02:06:18 2012 PST]#749690 [Thunderbird:Instant Messaging]-Add a findbar and support the zoom feature in the chat tab [All] [May 02 08:08:33 2012 PST]#739639 [Thunderbird:Message Compose Window]-forwarding message puts cursor at end instead of beginning [All] [May 02 14:51:10 2012 PST]#741998 [Thunderbird:Theme]-Implement Australis toolbar button design [Win] [May 03 06:25:05 2012 PST]#750080 [Thunderbird:Account Manager]-Segmentation fault (crash) when writing email with no account created nsMsgDBService::GetOpenDBs [Lin] [May 03 12:39:24 2012 PST]#751679 [Thunderbird:Build Config]-Update AUS server for Thunderbird [All] [May 03 13:40:47 2012 PST]#750794 [Thunderbird:Preferences]-Add pref UI to enable do-not-track (DNT) in Thunderbird [All] [May 04 10:03:19 2012 PST]#751871 [Thunderbird:General]-After upgrade refuses to start - crashes with "Terminate called without an active exception" in terminal. [Lin] [May 08 15:38:26 2012 PDT]#747415 [Thunderbird:Mail Window Front End]-Make our css more efficient. [Mac] [May 08 15:38:26 2012 PDT]#557928 [MailNews Core:LDAP Integration]-crash [@ nsLDAPOperation::SimpleBind(nsACString_internal const&)] and [@ @0x0 | nsLDAPOperation::SimpleBind(nsACString_internal const&)] [All]
Last edited by JoeS on May 9th, 2012, 3:36 pm, edited 6 times in total.
Did anybody on Windows recently install 12.0 or 12.0.1 from scratch? Just wondering, given that bug 481815 introduced a Windows service to update applications without asking Administrator password (i.e., it installs a "service" running with administrative privileges and is taking care of any updates, which you should see in the Services tab and say something like "Mozilla Maintenance"). Firefox seems to have a UI for it, I don't see any equivalent for Thunderbird or SeaMonkey (that's the app.update.service.enabled preference).
I don't think I've ever heard of a problem of asking for an Administrator password for TB updates. But then, all my personal systems are running as administrator
Never mind, though that service is strictly speaking Toolkit code it appears to be only packaged with Firefox. That's kind of a similar approach that Adobe went with their update service, annoyingly doing everything in the background without the user noticing (other than clogging your connection and hiking your CPU) and suddenly the new version shows up on restart. Personally, I still prefer to be in control when to clog my line, and I always like to see what's going wrong rather than something getting stuck in a background process...
As part of the automation switch, we've just landed a change to update the url for the update server for Daily (trunk) builds.
Whilst there should be no visible change for most users, there may be an additional delay of about 30 minutes after builds complete before updates are available. This will only occur for the next few days until we swap the trunk builders to the new automation.
Once the swap of builders occurs, there will be another few days where users of the old url will need to update to the latest version before picking up the url for the new server. At some stage soon after we'll be pointing the old url to the new server, and hence users will get the latest version regardless of what build they are on.
This should all be transparent, but if you do see issues with Daily builds over the next few days, please file a bug in mozilla.org / Release Engineering and mark it as blocking bug 750649.
Tree is closed on trunk after landing of # 650353 [Core/JavaScript] have one global object per compartment, tracked for comm-central by # 751873 (blocker).
The stack trace isn't really useful, it doesn't get far beyond the first steps and the link points to nsAutoVoidArray (but the include file rather than any actual code). Anyway, you are not alone, seeing 12 crash reports (all Linux, but various causes) over the last week matching that signature so far.
Did you get something like "Terminate called without an active exception" in your console window? That's what # 751871 reports, also after an update, but apparently he didn't file a crash report so that we could compare it.
This was caused by # 736564 [Core] mozglue library should be included into xulrunner SDK, Standard8 has checked in a bustage fix, thus the next tinderbox or nightly builds should be working again. Also, a comment was added that this would break again once a second merge from that bug into mozilla-central comes. Thus, it probably depends on whether or not that can be caught in time on the comm-central side.
Edit:
Standard8 wrote:We've fixed the crash issue for Linux, there will be new nightlies out in an hour or two once the builds complete.
mozillaZine is an independent Mozilla community and advocacy site. We're not affiliated or endorsed by the Mozilla Corporation but we love them just the same.