Download Thunderbird 32 Bits
Shanae Maerz
Now that from thunderbird V 68.0 the 64-bit version is generally available how do we import all the 32-bit accounts to a 64-bit installation?I have installed the 64-bit version 68.0 and since upgraded to v 68.1.0 but both versions totally ignore the existing 32-bit thunderbird accounts. The 32-bit continues to function, so must be able to still find the existing profiles.How do I get the 64-bit installation to recognise and use these existing accounts?The Import everything simply reports "No application to import data from found.", so it appears to ignore the existing thunderbird accounts.The 32-bit version is installed to "C:\Program Files (x86)\Mozilla-org\Thunderbird" whilst the 64-bit version is in "C:\Program Files\Mozilla-org\Thunderbird".
I downgraded thunderbird to the 32-bit version, and that fixed thunderbird as well. I wonder why the 64-bit versions were prone to crashing? I noticed about a 20% slowdown in thunderbird and not much in firefox.
I downgraded thunderbird to the 32-bit version, and that fixed thunderbird as well. I wonder why the 64-bit versions were prone to crashing? I noticed about a 20% slowdown in thunderbird and not much in firefox.
I offer two reasons, no swap file and not enough memory to use 64 bit software. Now the only loss may be some speed and so dropping to 32 is a very good solution. Also, gropiuskalle already picked up on the memory thing before you dropped to 32 bit. It would seem that short of buying more memory, dropping to 32 bit was the answer. I might add though, it is not too late to add a swap partition. Drop some space on an existing partition and create a swap. If you use the YaST Partitioner, it will even add the partition to your fstab file for you.
Some browsers only display the root certificates that the user has actually used, and dynamically download new ones on demand. However, Mozilla believes it is important for users to know the root certificates that could be used, so the full set of certificates is always shown. This also allows you to edit the trust bits for any root certificates that you do not want to use.
If you change the trust bits of a root certificate or add or delete roots, that change will be will not be affected by upgrading to newer versions of the software. It can only be changed again by you.
Deleting a root certificate that is in the default root store is equivalent to turning off all of the trust bits for that root. Therefore, even though the root certificate will re-appear in the Certificate Manager, it will be treated as though you changed the trust bits of that root certificate to turn them all off.
If you delete a cert in your database that is also in the built-in list, it may appear to be completely gone, until you restart your program, at which point it will reappear, because it never left the built-in root list. However, the trust bits will be turned off for the root.
If you have edited the trust bits of a built-in root certificate, causing it to be copied to your personal database, you may wish to delete the copy from your database so that the default trust bits are again used. (Simply editing the trust bits to match the defaults would not give you the benefit of any updates Mozilla may later make to the defaults.) There is currently no UI to do this (bug 558222), but you can use the NSS certutil command-line tool. certutil does not ship with Mozilla products, and NSS itself does not have official binary releases at this time, but you can build certutil from source, or your OS distribution may include it (Fedora: nss-tools, Debian/Ubuntu: libnss3-tools).
760c119bf3