update to 115 Supernova is empty page with menu and taskbar. Could not see folders, nor address book, nor inbox messages for 5 accounts
I was running TB 102.15 and I did an update which was to 115 supernova. When I opened the supernova application on my windows 10 desktop, I could not see folders, nor address book, nor inbox messages for any of my 5 emails that TB manages. It was an empty page with menu and taskbar only.
I actually was able to pull my old profile while under 102.15 from a cloud backup of idrive. I uninstalled supernova, saved and then deleted my thunder profile from "app data" (that supernova created), reinstalled 102.15, let it populate a new profile, copied the items IN my old profile (102.15) that was from idrive and pasted them in the new .default-release folder. Its running again. BUT..... I am now afraid what will happen when I HAVE TO update to supernova....what wouldn't my 102.15 profile just transfer over to 115 supernova?????
Edeziri
All Replies (4)
correction-----I deleted my profile created under supernova since I had my old profile from 102.15 on my i drive backup account.
Sounds like when you installed supernova that you didn't install it over top of version 102, into version 102's program directory.
Is that possible?
Yes 102.15 was installed and running. Then it updated to supernova and that is when everything dissapeared. But you are correct in that I later uninstalled 102 and installed supernova and that also failed. so I went back to installing 102.15 and then updated thru "Help--->about thunderbird" but again it failed. The program did install correctly but it did not show any folders, no address book and no emails. It was just a blank /empty program.
I am totally petrified to update to supernova again. I did upgrade my mother's thunderbird to supernova and no problems. I also updated my husbands and again no problems with importing the profile on both of there desktops. But mine is not importing my 102.15 profile....
I've been suffering from the same experience you had angellea but I haven't yet reverted to the older 102.15 yet. Instead, I found a work-around that while messy, works temporarily. I'm hoping there's a bug fix release for those of us upgrading from 102.15 here in the near future??
But in case anyone is interested in the details, see my posts here: https://support.mozilla.org/en-US/questions/1423621#answer-1603330