Hi,

I got a couple of information on this.

a) The Thunderbird is officially not compatible with Mac OSX 10.9 Mavericks :(

b) To use the Thunderbird 31.0 on Mac 10.9, you have to launch it in 32-bit Mode. DO AT YOUR OWN RISK!!

I sure hope that Mozilla will address this issue and make it comfortable to use with Mavericks ASAP!!

BTW, the problematic screen appears like this. Please note that I retouched the image by erasing my own e-mail address that is shown on the right of "Thunderbird Mail -".

I got another information on this.

There is a user here in Japan who runs Thunderbird 31.0 on Mac 10.6 and he also experiences the same symptom as I.

So the OS compatibility is not the cause.

Hope they'll fix this issue ASAP!!

I still got another couple of Thunderbird 31 user reports on Mac OSX 10.7.5, and 10.8.5 that are supposed to be compatible with TB31 but are unable to use because of the same symptom as I experienced: No folders shown in the Fonder Pane.

So again, it's not the OS compatibility issue, it's a bug in the TB31. I sure hope they'll fix this issue ASAP!!

Do you have folderpane tools addon installed? Does your problem reproduce in THunderbird safe mode?

Thanks for your reply.

a) Folder Pane Addon

People say it's not compatible with TB31.0: https://addons.mozilla.org/en-US/thunderbird/addon/folderpane-tools/

b) TB Safe Mode

There are reports here in Japan that TB Safe Mode didn't solve the issue.

>>W: Do you have folderpane tools addon installed? >N: a) Folder Pane Addon >N: People say it's not compatible with TB31.0: https://addons.mozilla.org/en-US/thunderbird/addon/folderpane-tools/

yes. But this doesn't answer my question. Do YOU have the addon installed?

>>W: Does your problem reproduce in THunderbird safe mode? >N: b) TB Safe Mode >N: There are reports here in Japan that TB Safe Mode didn't solve the issue.

OK. But this doesn't answer my question. Does your problem reproduce when YOU start THunderbird safe mode?

>N: I got a couple of information on this. >N: a) The Thunderbird is officially not compatible with Mac OSX 10.9 Mavericks :( >N: b) To use the Thunderbird 31.0 on Mac 10.9, you have to launch it in 32-bit Mode. DO AT YOUR OWN RISK!!

According to https://www.mozilla.org/en-US/thunderbird/31.0/system-requirements/ Mac OSX 10.9 is supported, and there is no requirement to run 32bit mode.

Please cite your references / URLs.

> Please cite your references / URLs.

Here:

http://www.mozilla.jp/thunderbird/31.0/system-requirements/

I'll try add-on and safe mode later.

>> Please cite your references / URLs. > http://www.mozilla.jp/thunderbird/31.0/system-requirements/

I suspect they simply missed mentioning OS X 10.9 I would not take the omission as, it doesn't work.

Ok, so I tried both the addon and the safe mode. They seemed to solve the issue for the first few launches but after that, they all ended in vain.

Also.....

> I suspect they simply missed mentioning OS X 10.9 > I would not take the omission as, it doesn't work.

That's because you knew below webpage but most of us Japanese including myself don't even know it exists!! https://www.mozilla.org/en-US/thunderbird/31.0/system-requirements/

So it seems like I have to keep using the TB31 in 32bit Mode.

Thanks a lot for the info anyway.

Hey,

You wrote.....

> According to https://www.mozilla.org/en-US/thunderbird/31.0/system-requirements/ > Mac OSX 10.9 is supported, and there is no requirement to run 32bit mode.

Although above URL itself says "31.0" the actual webpage linked from above says "Thunderbird 26.0 System Requirements".

Which one should I believe!?

> "Thunderbird 26.0 System Requirements" is an edit error

It's now reported on here also: https://bugzilla.mozilla.org/show_bug.cgi?id=1045958 The Japanese user forum which I often refer to is also referred here.

>> "Thunderbird 26.0 System Requirements" > is an edit error

>> http://www.mozilla.jp/thunderbird/31.0/system-requirements/ > I suspect they simply missed mentioning OS X 10.9

With all sorts of edit errors here and there, and if the problem won't be solved soon, I have to consider stop using Thunderbird and moving to other mailer software.

so you read in the forum

1. "When folderTree.json session.json or is damaged, the symptoms of the problem it is to occur. " And if you remove folderTree.json session.json then the problem goes away

2. only one user reported using Thunderbird in safe mode

> 1. "When folderTree.json session.json or is damaged, the symptoms of the problem it is to occur. " And if you remove folderTree.json session.json then the problem goes away

I tried and the problem went away only for the first launch. From the second launch it came back and everything is in vain again.

> 2. only one user reported using Thunderbird in safe mode

But I also experienced the same in the safe mode so at least its two, including myself. Now what shall I do??

> Now what shall I do??

I have neither the environment nor the Japanese build, so there's nothing I can do expect encourage everyone to submit information and diagnose the problem.

I cc some Mozilla Japan developers on https://bugzilla.mozilla.org/show_bug.cgi?id=1045958 and they are looking. I suggest you offer your help there.

Thanks for helping push this issue forward.

My wife also experienced this issue using the Japanese build of version 31 on a Mavericks machine, and so has been using an old version of Thunderbird.

The link in Wayne's final post does not lead to Bugzilla content I can access. All I get is a message saying "you are not authorized to access bug #1045958".

Has there been any progress on this very irritating issue?

A fix is available, but we are still in the process of trying to get the fix in for the next release, Thunderbird 31.3.0

Thank you! We'll hold off upgrading for the time being, then.

Wayne Mery said

A fix is available, but we are still in the process of trying to get the fix in for the next release, Thunderbird 31.3.0

TB 31.3 din't help us at all, but finally a couple of days ago, after several months of waiting, 31.4 came out and this bug seems to be eliminated at last. Thanks.