841687 - folders not visible

Status: RESOLVED WORKSFORME

(Thunderbird :: Folder and Message Lists, defect)

Description

[helkav]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/20100101 Firefox/18.0
Build ID: 20130201065344

Steps to reproduce:

start TB latest release 17.0.2 : Note I normally use Daily and I'm on the nightly update channel, may not be related but they're sharing the same profile, so perhaps there's a backward compatability issue? I checked the mail accounts and they were all set up correctly as per profile


Actual results:

I am using the classic view layout with the accounts and folders on the LHS. It's completely blank, not even local folders is there


Expected results:

account and local folders should have been displayed on RHS

Comment 1

[WADA:World Anti-bad-Duping Agency]

Does you problem occur even with -safe-mode of Tb?
(Help/"Restart with Add-ons Disabled" is available) 

Similar external phenomenon to bug 720958, bug 721842 etc.? (dups of bug 707329)
If so, folderTree.json may be state of "not syntactically broken" but state of "semantically incorrect and no valid folder data is contained".
Is folder pane shown by following?
  Terinate Tb, rename folderTree.json to folderTree.json-Backup, and restart Tb

Comment 2

[helkav]

(In reply to WADA from comment #1)
> Does you problem occur even with -safe-mode of Tb?
> (Help/"Restart with Add-ons Disabled" is available) 
> 

I tried to do this just now, unfortunately suddenly I can see the folders again. If it happens again I will try also in safe mode as you suggest

Comment 3

[:aceman]

This may also be fallout from bug 807848. See what is the value of the preference toolkit.telemetry.prompted in prefs.js. It should be set to true. If this is your problem, you should see an error in the Error console.
Some versions of TB Daily became incompatible with previous versions (like TB17.0.2 you mention). We have hopefully sorted it out now. TB17.0.3 should fix your profile even if you do not fix it manually as I wrote. Of course, only if this is the cause of your problem.

Comment 4

[helkav]

This has not happened for quite a while now...perhaps it has been fixed by the latest daily updates. I don't know what the protocol is for a bug that's not reproducible anymore but hasn't been fixed by any specific code? do I mark it as closed and/or not reproducible ?

Comment 5

[Wayne Mery (:wsmwk)]

(In reply to hckpost from comment #4)
> I don't know what the protocol is for a bug that's
> not reproducible anymore but hasn't been fixed by any specific code? do I
> mark it as closed and/or not reproducible ?

RESOLVED + WORKSFORME :)

Comment 6

[helkav]

ah...d'oh!