Thunderbird 3.0 installation issues: Difference between revisions

From MozillaZine Knowledge Base
Jump to navigationJump to search
(→‎Major: gloda info)
m (→‎Major: nit 2.0.0.23 > 2.0.0.24)
Line 9: Line 9:
* If you are using Kaspersky antivirus and have blank windows after you upgrade see [http://getsatisfaction.com/mozilla_messaging/topics/kaspersky_anti_spam_extension_causing_blank_window_problems_with_thunderbird_3_upgrade Kaspersky causing blank window problems with Thunderbird 3 upgrade]
* If you are using Kaspersky antivirus and have blank windows after you upgrade see [http://getsatisfaction.com/mozilla_messaging/topics/kaspersky_anti_spam_extension_causing_blank_window_problems_with_thunderbird_3_upgrade Kaspersky causing blank window problems with Thunderbird 3 upgrade]


* '''It is strongly recommended that you [[Profile_backup | backup your profile]] before upgrading to 3.0'''. If you go back to 2.0.0.23:  
* '''It is strongly recommended that you [[Profile_backup | backup your profile]] before upgrading to 3.0'''. If you go back to 2.0.0.24:  
:* It may create a smart folder account (due to having used smart folders in 3.0) that gradually corrupts folder listings. You can't delete it except by editing prefs.js.  
:* It may create a smart folder account (due to having used smart folders in 3.0) that gradually corrupts folder listings. You can't delete it except by editing prefs.js.  
:* Your passwords are stored in a different file in 3.0. However, the old passwords file is not deleted so if your passwords haven't changed you don't need to re-enter them again.  
:* Your passwords are stored in a different file in 3.0. However, the old passwords file is not deleted so if your passwords haven't changed you don't need to re-enter them again.  

Revision as of 19:52, 8 October 2010

Major

  • If you enable Global Search/Indexing information, then information about every message in every account (except News) is stored in an SQLite database. This feature has some unfixed bugs, and the the index for global search requires substantial disk space. In v3.0 one person's testing shows an average of 3.5 KB needed per message [1]. Note however, space requirements will vary greatly depending on what size and types of messages one receives, for example how many "message parts" are received in messages. (And space requirements are lower in v3.1 compared to v3.0 due to fixing of bug 543737 avoid indexing ridiculously large message bodies ... max 20k per message part.) If you encounter a problem you can either disable Global Search by unchecking Tools -> Options -> Advanced -> General -> Advanced Configuration -> Enable Global Search and Indexer, or use a debugging document. Known issues:
    • poor performance - constant high cpu and/or high memory (over 200 MB)
    • size of the profile / database keeps growing even after it had enough time to initially index all of the messages
  • If you can't update an add-on it will frequently work if you disable version checking per Updating add-ons. If it doesn't work correctly you can either disable or uninstall it (from Safe Mode if necessary).
  • It is strongly recommended that you backup your profile before upgrading to 3.0. If you go back to 2.0.0.24:
  • It may create a smart folder account (due to having used smart folders in 3.0) that gradually corrupts folder listings. You can't delete it except by editing prefs.js.
  • Your passwords are stored in a different file in 3.0. However, the old passwords file is not deleted so if your passwords haven't changed you don't need to re-enter them again.
  • If you switched to the new toolbar using the migration assistant you may have to customize the toolbar again.
  • Your add-ons may have been upgraded to versions that are not backwards compatible if you enabled automatically checking for updates for add-ons.
  • If you enabled Global searching/Indexing the global-messages-db.sqlite file in your profile is useless, and may waste a lot of space.
  • The new Account Wizard is easier to use but can make some unusual choices such as using an IMAP server in the Gmail domain while using a SMTP server in the Googlemail domain. It might also pick an existing SMTP server from another account that uses a different username rather than creating a new SMTP server entry. You can fix this by editing the account, the main thing is to be aware that these types of mistakes are being made. [2]
  • Thunderbird 3.0 might request a master password even though you never created one. There are several bugs in the upgrade code that cause this, with slightly different symptoms. One is fixed in 3.0.1. [3]. The bug(s) modifies your profile to say you have a master password, and does it in a way that prevents you from resetting the master password normally.

    If you backed up your profile beforehand try replacing the cert8.db and Key3.db files in your profile with the ones from your backup. Otherwise use one of the workarounds mentioned in either this thread or this one to reset your master password. Unfortunately, that deletes any saved passwords. [4]

  • Poor performance moving or deleting messages if you store your profile on a file share. It appears to be because they replaced some XPCOM calls with ones that don't do buffered writes. [5] [6] .
  • Password prompting is no longer sequential. Thunderbird may prompt for a password and while you are typing it display a prompt for another accounts password. The best workaround is to have the password manager remember them. [7]