Click on background master password window and enter twice. Enter master password in this new window. * 3rd TB restart (same as 2nd TB restart, but don't enter master password, just wait) -> 10 minutes later, a new master password prompt appears in front of main TB window (for IMAP refresh).
#Thunderbird master password reset windows
* 2nd TB restart (1 imap + 2 network calendars): 1 master password prompt immediately hidden by main TB window, 2 TB windows in task bar -> inbox is not refreshed and calendars are empty -> need to click on task bar to bring master password prompt on top, then type it, then ok. * 1st TB restart (1 imap + 0 calendar): main TB window displayed + 1 master password prompt on top of screen, only one TB windows in task bar -> OK * 6th TB restart + long wait (2min 30sec) * set email check for new message to 1 minute * 5th TB restart + long wait (2min 30sec) * if modified set email check for new message back to 10 minutes * switch each calendars on + refresh every minute * switch Calendars Off (right click on calendar + properties + uncheck "switch this calendar on", for each calendar) and 4th TB restart * 3rd TB restart + long wait (> 10 minutes, default IMAP refresh, but can be set to 1 minute to speed up tests: Edit - Account Settings - Server Settings - Check for new message every 1 minutes)
* 2 network CalDAV calendar creation, with authentication + remember (in my case, the 2 calendars are on the same DAViCal LAN Server, and can be accessed with the same authentication, but this bug have been reported with different configurations)
#Thunderbird master password reset install
* Addon Lightning 1.0b5 install + 1st TB restart
* one e-mail imap account creation (or pop) with authentication + remember bzip under Linux Ubuntu 11.04 x86 32 bits) Steps to reproduce several aspects of the bug: Multi-password prompt have been partially fixed in normal usage condition, but password prompt is still hidden by main window, and multiple password prompts still occurs if master password haven't been entered quickly. This bug had different forms from Thunderbird 3.1.10 / Lightning 1.0b2 Linux and WinXP to Thunderbird 6.0 / Lightning 1.0b5 Linux and Win7.
0 kommentar(er)
