Following the link to the gnome bugzilla -- I ran across a tolerable workaround for the moment: If G_SLICE=always-malloc is in the environment, then it will start. It still complains, but it starts and appears to work (so far).
This makes it consume more CPU (and Lord knows it already consumes enough CPU), but it does allow Thunderbird to start - which is a good thing.
Following the link to the gnome bugzilla -- I ran across a tolerable workaround for the moment: If G_SLICE= always- malloc is in the environment, then it will start. It still complains, but it starts and appears to work (so far).
This makes it consume more CPU (and Lord knows it already consumes enough CPU), but it does allow Thunderbird to start - which is a good thing.