Closed
Bug 134289
Opened 23 years ago
Closed 23 years ago
Turbo, Address Book entries from first profile appear in second
Categories
(SeaMonkey :: MailNews: Address Book & Contacts, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 124208
mozilla1.0
People
(Reporter: nbaca, Assigned: sspitzer)
References
Details
(Whiteboard: [ADT2])
Trunk build 2002-03-28: WinMe
Overview: I get into a state where my address book entries from the first
profile appear in the second profile.
Steps to reproduce:
1. Migrate 1 profile
2. turn turbo on
3. Start 1st profile and add some cards, lists, address books
4. Exit
5. Run "netscape.exe -installer" to see the list of other profiles and select a
second profile (in this case it was another IMAP profile)
6. Open the Address Book window
Actual Results: Cards and lists from the first address book are appearing in the
second. It also appears that the entries are mixed up. In one list I should have
had just 3 entries but it included many more.
Expected Results: I should only see the cards/lists/address books that are
pertinent to the profile that is currently loaded.
Reporter | ||
Comment 1•23 years ago
|
||
Marking nsbeta1 since this makes it difficult to trust what is seen in the
address book.
Severity: normal → major
Keywords: nsbeta1
Reporter | ||
Updated•23 years ago
|
Summary: Address Book entries from first profile appear in second → Turbo, Address Book entries from first profile appear in second
Reporter | ||
Comment 2•23 years ago
|
||
Note to QA: Use nbaca's qatest32/qatest22 profiles to verify this bug when there
is a fix.
Comment 3•23 years ago
|
||
Discussed in Mail News bug meeting. Decided to ADT2 and plus this bug.
See also bug 124208 which this one might be a duplicate of.
Assignee | ||
Comment 7•23 years ago
|
||
yes, it's a dup of #124208
my fix for #124208 fixes this.
*** This bug has been marked as a duplicate of 124208 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•