Regardless of the post count (and yes, we all began with one), there's no need to be rude to anyone.

I understand the challenge of supporting features directly versus add-ons, but multiple identity support and synchronizing seems so common today that related add-ons should be mainstream features.

Long ago after adopting Slackware, for a few years I was stuck with Eudora in Windows. I converted my NT4 setup to a VM and ran Eudora from there with Slackware as my host OS. Eventually I inhaled deeply and migrated to KMail during the KDE 3 days. Along with the move I changed from mbox to maildir.

Some years later, when akonadi became a pillar of KDE 4, I migrated to Thunderbird. Fortunately for me, maildir format was robust enough I had no mail corruption migrating from kmail.

For many years I resisted any kind of full-scale calendar app. My reminder needs are simple. I started with KAlarm in the KDE 3 days, moved to ReminderFox when I moved away from KDE 4, then when ReminderFox lost support with the Web Extension changes, moved to Lightning.

I am satisfied with Lightning and an interesting journey.

1 members found this post helpful.

I took 68.2.0 for a spin.

Same issues:

* Help->About dialog defaults to automatically checking for updates rather than presenting a button.
* Thunderbird segfaults when gfx.downloadable_fonts.enabled=true.

In my user.js I have all preferences related to updates disabled. Perhaps something has changed with global preferences that enables the automatic update check. Anybody know where?

Comparing the 60.9.0 and 68.2.0 sources I found some candidates that might be causing the segfault.

browser/extensions/pdfjs/content/PdfStreamConverter.jsm:
60.9:
return (!!prefBrowser && prefGfx);
68.2:
return !!prefBrowser && prefGfx;

layout/reftests/reftest-sanity/reftest.list:
60.9:
pref(gfx.downloadable_fonts.enabled,true) skip-if(styloVsGecko) != font-download.html font-default.html
pref(gfx.downloadable_fonts.enabled,false) skip-if(styloVsGecko) == font-download.html font-default.html
68.2:
pref(gfx.downloadable_fonts.enabled,true) != font-download.html font-default.html
pref(gfx.downloadable_fonts.enabled,false) == font-download.html font-default.html

As of Thunderbird 68, automatic updates can now only be disabled using the policy framework. Under Linux this is specified in a JSON file called policies.json in the distribution/ subdirectory of the main program tree. For a Slackware Thunderbird package this is probably /usr/lib64/thunderbird/. If the distribution/ directory doesn't exist just create it. Place the following content in policies.json:

This approach works for Firefox and Thunderbird from either Slackware packages or binary tarballs from Mozilla.

The use of policies.json for Firefox was first mentioned in an LQ post from "ljb643" in July 2019 (see the "Latest Firefox stable in Slackware" thread). The same advice applies to Thunderbird 68.

4 members found this post helpful.

Thank you for the information! The original post is here. Some additional comments here.

Some people on IRC has ditched TB for SM. I personally use Claws Mail with PGP/GPG plugins. I always remove Thunderbird on every install, only tried it once and didn't like it.

The Help->About dialog issue is now resolved.

Interesting, Thunderbird 68.2.1 still sefaults on "gfx.downloadable_fonts.enabled=false"

I never noticed before since I had never changed that setting. A few forum posts, but I don't see anything (so far) in bugzilla.

Also, for what its worth, I like TB since transitioning from Mozilla/Seamonkey. 4 email accounts (imap, pop3), filters to sort mail into local folders, calendar, enigmal, RSS/Atom feeds, very configurable and has served me well since its birth. Of course, YMMV.

Yes, in post 33 I noted some possible spots to start debugging. The bug could be elsewhere in the code though.

I started a new thread about the segfault. Please help if you understand code debugging.

Pat is aware of the segfault.

Indeed, and tried all of the usual tricks like changing the compiler, changing the linker, adding -fno-delete-null-pointer-checks, etc. No luck. It's not going to be me who digs into this with a debugger.

Meanwhile, the advice would be similar to the old joke where the fellow goes to the doctor and says "Doc, it hurts when I do this..."

Okdeydokey. I tested 68.2.2. Same segfault.

@upnort

Wouldn't be appropriate to ask for help from the specialists? Register a bug @
https://bugzilla.mozilla.org/home
Wasn't lucky in finding anything related to this segfault in their buglist:
https://bugzilla.mozilla.org/describ...ct=Thunderbird


Besides, they fixed the profile import/migration from Thunderbird version 60 to version 68 (64 bit) in 68.2.2. It messed up my profile too, had to manually move it
https://www.thunderbird.net/en-US/th.../releasenotes/
I guess "Then" is a typo, should be "When".

Sure, but can bug reports be filed anonymously or is Yet Another Online Account required?

Besides, I lean toward the bug being Slackware specific. I am not pointing fingers, just sharing observations. I have not tried 68.x in different distros, but I tested the Mozilla package and could not trigger the bug. Possibly the bug is related to the build chain. Pat gave that question a good shake and came up empty. If he found nothing then I'm out of my league to continue his efforts.

If the bug is Slackware specific then I doubt the developers will help.

I'll try to remember to test 68.x in some distros.